234
Pages Scanned
49
Pages Flagged
234
Changed Pages
20.9%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-02-22 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 234
Files Completed: 234
Problematic Pages
51 issues found
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows/PowerShell environments. All onboarding scripts and example commands are provided only as PowerShell scripts (.ps1), and users are instructed to use PowerShell terminals. Installation instructions use Windows-specific tools like winget, with no mention of Linux/macOS equivalents. There are no Bash/shell script examples or guidance for non-Windows users, making it difficult for Linux/macOS administrators to follow the onboarding process.
Recommendations
- Provide equivalent Bash/shell scripts for Linux/macOS users, or document how to run the onboarding process on those platforms.
- Include installation instructions for Azure CLI and kubectl using platform-agnostic methods (e.g., apt, yum, Homebrew, or official install scripts) instead of only winget.
- Clarify whether the onboarding scripts are supported on Linux/macOS (e.g., via PowerShell Core or alternative scripts), and provide troubleshooting notes for cross-platform use.
- If the onboarding process is truly Windows-only, explicitly state this in the prerequisites section.
Create Pull Request
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 backup and restore examples using Windows file paths (e.g., 'C:\Backupfiles\test.bak') and references Windows tools (SQL Server Management Studio, Visual Studio Code) without offering equivalent Linux/macOS examples or guidance. The 'kubectl cp' example also uses a Windows path, and there is no mention of Linux file paths or tools for creating backups, which may create friction for Linux/macOS users.
Recommendations
- Add Linux/macOS file path examples alongside Windows examples (e.g., '/home/user/Backupfiles/test.bak').
- Mention and provide guidance for Linux-compatible tools for connecting to SQL Server (e.g., Azure Data Studio, sqlcmd).
- Clarify that the backup file can be created on any OS and provide instructions for Linux/macOS users.
- Include notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting HTTP2 errors, Windows paths are shown in error messages, and Windows-specific tools (like Remote PowerShell and RDP) are discussed. Linux-specific troubleshooting steps and examples are minimal or missing, and Windows tools or patterns are often mentioned first or exclusively. For example, the PowerShell example for HTTP2 troubleshooting is given, but no Linux equivalent (such as curl with --http2) is provided. The GLIBC error is explained, but no guidance is given for checking or upgrading glibc on Linux. In DNS troubleshooting, Windows tools (Resolve-DnsName, ping) are shown, but Linux equivalents (dig, nslookup) are not. The documentation does not provide parity in examples or troubleshooting steps for Linux/macOS users.
Recommendations
- Add Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl --http2 for HTTP2 troubleshooting, dig/nslookup for DNS troubleshooting).
- Mention Linux/macOS tools alongside Windows tools when discussing troubleshooting steps (e.g., SSH folder permissions, network diagnostics).
- Provide guidance for resolving GLIBC errors on Linux, including commands to check and upgrade glibc.
- Ensure that troubleshooting steps and error messages reference both Windows and Linux paths and environments.
- Where possible, use cross-platform CLI commands (such as Azure CLI) and clarify any OS-specific requirements.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides authentication options and examples for connecting servers to Azure Arc using azcmagent. While most examples and instructions are generic and applicable to both Windows and Linux, there is a notable Windows bias in several areas: the interactive browser login is described as Windows-only and presented first; certificate-based authentication includes detailed instructions for Windows certificate stores but lacks equivalent Linux guidance; and access token acquisition references only the Windows PowerShell Get-AzAccessToken cmdlet, omitting Linux alternatives.
Recommendations
- Present authentication options in a neutral order or explicitly note Linux defaults where relevant.
- Add Linux/macOS-specific guidance for certificate-based authentication, such as how to use PEM/PFX files and recommended storage locations.
- Include Linux-compatible methods for obtaining access tokens, such as using Azure CLI (az account get-access-token) or Microsoft Entra clients for Linux.
- Where Windows tools are mentioned, provide equivalent Linux commands or links.
- Clarify which examples and flags are cross-platform, and highlight any OS-specific limitations.
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
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation provides only a Windows/PowerShell-based recovery script and instructions. There are no examples, scripts, or guidance for performing the recovery from a Linux or macOS machine. The script provided is a PowerShell script, which is not natively available on Linux/macOS, and there is no mention of cross-platform alternatives.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or cross-platform PowerShell Core if possible.
- Explicitly state if the recovery process is only supported from Windows, and explain why.
- If possible, offer a containerized or cross-platform CLI tool for the recovery process.
- Clarify any Windows-specific dependencies in the prerequisites section.
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 shows notable Windows bias. The auto-enablement script is PowerShell-based, with instructions and examples for Windows terminals and Windows Task Scheduler. Windows tools and automation patterns (PowerShell, Task Scheduler, Group Policy, Configuration Manager) are mentioned before Linux equivalents. Linux-specific guidance is minimal and not as prominent, with only a brief sudo configuration note and a mention of Ansible playbooks in the out-of-band section.
Recommendations
- Provide a Bash or cross-platform version of the auto-enablement script, or document how Linux/macOS users can run the PowerShell script (e.g., via PowerShell Core).
- Include Linux/macOS terminal instructions alongside Windows/PowerShell examples, such as how to run the script from Bash or zsh.
- Offer examples for scheduling automation on Linux (e.g., using cron) in addition to Windows Task Scheduler.
- Highlight Ansible and other cross-platform automation tools earlier and more prominently, not only in the out-of-band section.
- Ensure parity in prerequisites and troubleshooting steps for Linux/macOS 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 automation, without providing Bash or shell script equivalents. There are no Linux/macOS-specific examples or guidance, and the use of PowerShell is shown first and exclusively, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI command examples in Bash syntax (e.g., using single quotes, escaping, and variable conventions for Bash).
- Offer Bash or shell script equivalents for the referenced PowerShell automation scripts (e.g., bulk_deployment.ps1 and workflow-delete.ps1).
- Clarify that Azure CLI commands can be run in Bash or PowerShell, and highlight any OS-specific considerations.
- Add notes or sections for Linux/macOS users, including sample commands and scripts.
- Ensure file paths and variable conventions are compatible with Linux/macOS environments.
Azure Arc
Clean-Up Script for Workload Orchestration
...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for Linux/macOS users, such as using Bash, shell scripts, or cross-platform alternatives. The script and its usage are presented as Windows-first, with no mention of how to run or adapt the script on non-Windows platforms.
Recommendations
- Provide instructions for running the script on Linux/macOS, such as using PowerShell Core (pwsh) which is cross-platform.
- Include example commands for Linux/macOS terminals, e.g., using './RGCleanScript.ps1' with pwsh.
- Clarify whether the script is compatible with PowerShell Core or only Windows PowerShell; if not, offer a Bash or shell script alternative.
- Mention prerequisites for Linux/macOS users, such as installing PowerShell Core and ensuring script execution permissions.
- Consider providing a platform-agnostic cleanup tool (e.g., a Python or Bash script) or guidance for Linux users.
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 offering a Bash or Linux-compatible alternative. There is no mention of how Linux/macOS users can perform the migration, nor is there guidance for running the script cross-platform.
Recommendations
- Provide a Bash or cross-platform script for Linux/macOS users.
- Document how to run the PowerShell script using PowerShell Core on Linux/macOS, if applicable.
- Explicitly state platform requirements and offer alternatives or workarounds for non-Windows environments.
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 extensive PowerShell-based examples and scripts for diagnostics and onboarding, with no equivalent Bash, Linux shell, or cross-platform CLI examples. File paths in JSON templates and scripts are Windows-style (e.g., C:\, E:\), and all automation is shown via PowerShell scripts (.ps1), which are not natively supported on Linux/macOS. Azure CLI commands are embedded in PowerShell scripts, further reinforcing Windows-centric workflows. No Linux/macOS alternatives or guidance are offered, creating friction for non-Windows users.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell examples, especially for onboarding and diagnostics.
- Use cross-platform file path conventions in JSON templates (e.g., /home/user/path/file.yaml) or document how to adapt paths for Linux/macOS.
- Clearly indicate which scripts are Windows-only and offer alternatives for Linux/macOS users.
- Where Azure CLI is used, show direct CLI commands outside PowerShell context, and clarify that Azure CLI works on all platforms.
- Add notes or sections for Linux/macOS users, including troubleshooting tips and platform-specific instructions.
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 syntax. Most examples, including those for Azure CLI, kubectl, and Docker, are presented in PowerShell format, with no explicit Bash or Linux shell equivalents for critical steps. Only the 'service groups' section provides both Bash and PowerShell tabs, but the rest of the document assumes PowerShell usage, which creates friction for Linux/macOS users.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, kubectl, and Docker commands.
- Clearly indicate when commands are cross-platform and when they require Windows/PowerShell-specific syntax.
- Add notes or tabs for Bash and PowerShell throughout the troubleshooting steps, not just in the 'service groups' section.
- Review variable syntax and file manipulation steps to ensure they are compatible with Linux/macOS environments.
- Where PowerShell-specific features (e.g., ConvertTo-Json, Out-File) are used, offer alternatives for Bash users (e.g., jq, echo, cat).
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 instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell examples and references are prominent throughout. Windows/PowerShell tools are mentioned alongside Azure CLI, but Linux/macOS-specific guidance (such as shell scripting or environment setup) is largely absent. The CLI examples are generic and could apply to Linux/macOS, but PowerShell is featured equally or more, and there are no explicit Linux/macOS shell examples or notes about cross-platform differences. The 'Next steps' section links only to Azure CLI and PowerShell guides, omitting Linux/macOS-specific workflows.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., Bash) for authentication workflows, especially for scripting scenarios.
- Clarify that Azure CLI commands work on Linux/macOS and provide any OS-specific caveats (such as Docker daemon requirements or file locations).
- Include links to Linux/macOS getting started guides for Azure Container Registry.
- Balance PowerShell examples with Bash or other shell examples, or note PowerShell is Windows-centric.
- Mention cross-platform compatibility in sections referencing Docker and Azure CLI.
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. There is a specific note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance. The curl installation section gives a Windows link but only mentions 'install curl package' for Linux, lacking a direct link or command. There is also a PowerShell-specific note about curl aliasing, but no similar shell-specific notes for Linux/macOS. Overall, the page is usable for Linux/macOS users but could be improved for parity.
Recommendations
- List Linux/macOS installation links alongside Windows, not after or below them.
- Provide direct Linux/macOS installation commands or links for curl, not just 'install curl package'.
- Add shell-specific notes for Linux/macOS (e.g., bash/zsh) where PowerShell-specific notes are given.
- Ensure examples and guidance are equally detailed for all platforms.
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
Although the documentation is titled and scoped for Linux preparation with AKS Edge Essentials, it uses Windows-centric tools and patterns (Invoke-AksEdgeNodeCommand) for Linux node configuration. There are no native Linux shell or SSH examples for critical sysctl configuration steps, and the text editor suggestion (Notepad) is Windows-first. This creates friction for Linux/macOS users who may not have access to Windows tools or expect Linux-native workflows.
Recommendations
- Provide equivalent Linux-native commands (e.g., using SSH or local shell) for sysctl configuration, such as 'sudo sysctl fs.inotify.max_user_instances' and editing /etc/sysctl.conf directly.
- Suggest Linux text editors (e.g., nano, vim) instead of Notepad for editing aksedge-config.json.
- Clarify when Windows tools are required and offer alternative workflows for Linux-only environments.
- Add explicit notes or sections for macOS users if relevant.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for managing the Azure Connected Machine agent, including installation, upgrade, uninstall, and proxy configuration. However, Windows examples and tools (PowerShell, Control Panel, Group Policy, Microsoft Update, WSUS, Configuration Manager) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no Linux shell equivalent. Some sections (like Microsoft Update configuration) are inherently Windows-specific, but overall, Linux parity is good, though Windows-centric tools and scripting are emphasized.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for resource cleanup and stale server removal, not just PowerShell.
- Where possible, present Windows and Linux instructions side-by-side or in parallel, rather than Windows-first.
- Expand Linux uninstall instructions to include removal of residual folders/files, similar to Windows guidance.
- Clarify when a tool or method is Windows-only, and offer Linux alternatives where feasible.
- Consider including examples for macOS where relevant (e.g., Azure CLI usage).
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 both Linux and Windows ARM template examples for each extension, ensuring parity in template content. However, all deployment instructions and command-line examples exclusively use Azure PowerShell, with no Azure CLI or Bash equivalents shown. Additionally, PowerShell commands and Windows-style file paths are presented first and throughout, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. The documentation does mention Azure CLI in the 'Related content' section, but does not provide CLI examples inline.
Recommendations
- Add Azure CLI deployment command examples alongside PowerShell for each extension.
- Include Bash-style file paths and instructions for Linux/macOS users.
- Consider presenting CLI and PowerShell examples together, or alternate which is shown first.
- Clarify that PowerShell commands can be run cross-platform, but provide CLI alternatives for users who prefer them.
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 steps for Azure Arc resource bridge in VMware vSphere environments, but all script examples and instructions are exclusively in PowerShell (.ps1), with no mention of Bash, shell, or cross-platform alternatives. The onboarding script and its usage are presented only in Windows/PowerShell context, and there is no guidance for Linux/macOS users on how to perform equivalent operations.
Recommendations
- Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
- Explicitly state OS requirements for running the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS).
- Add instructions or examples for Linux/macOS users, including how to install prerequisites and run the script.
- Mention any limitations or workarounds for non-Windows environments.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy steps and script invocation, but does not offer equivalent Linux/macOS guidance. The script section is labeled 'Windows' and omits instructions for running the script on Linux or macOS, despite the Azure Arc agent supporting both platforms. This creates friction for non-Windows users, who must infer how to run the script or whether it is compatible. Additionally, Windows instructions are presented first and in greater detail.
Recommendations
- Add explicit instructions for running the deboarding script on Linux and macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any differences in behavior.
- Clarify script compatibility (e.g., if the script is PowerShell-only, note if PowerShell Core is required and how to install/run it on Linux/macOS).
- Present Windows and Linux/macOS instructions in parallel sections, or note any limitations for non-Windows platforms.
- Include troubleshooting or caveats for Linux/macOS users (e.g., file permissions, execution policy differences).
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 displays notable Windows bias in several areas. The example for installing kubectl uses Windows-specific tooling (winget) with no Linux/macOS alternative. The archive extraction example under the Bash tab uses Expand-Archive, which is a PowerShell/Windows command, not a native Bash/Linux command. 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 assumes Windows environments and tools, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS alternatives for installing kubectl (e.g., using curl or package managers like apt, yum, brew).
- Replace Expand-Archive in Bash examples with native Linux commands (e.g., unzip or tar).
- Use generic or platform-neutral file paths in examples, or provide both Windows and Linux/macOS path examples.
- Explicitly mention cross-platform support and clarify any Windows-specific steps.
- Add a Linux/macOS tab for critical steps where the Bash tab is actually Windows-specific.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as viewing registry usage and changing SKU), but consistently lists PowerShell examples alongside or immediately after CLI, and explicitly references PowerShell cmdlets. There are no Linux/macOS-specific examples or mentions of Bash or shell scripting, and the CLI examples are not explicitly shown as cross-platform. The documentation does not mention Linux tools or patterns, and PowerShell is referenced as a primary option, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Provide Bash shell scripting examples for common operations, or explicitly note that CLI commands work in Bash.
- Mention that PowerShell is primarily used on Windows, and suggest alternatives for Linux/macOS users.
- Consider listing CLI examples before PowerShell examples, or grouping them by platform.
- Add a note about installing Azure CLI on Linux/macOS, with a link to relevant documentation.
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 using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no explicit Linux-specific examples or mentions of Linux tools, and the Azure CLI is cross-platform, but the use of PowerShell syntax can create friction for Linux/macOS users.
Recommendations
- Provide both Bash and PowerShell examples for CLI commands, especially in sections where only PowerShell is shown.
- Clarify that Azure CLI commands work on all platforms and note any OS-specific syntax differences.
- Consider showing Bash examples first or side-by-side with PowerShell to improve Linux parity.
- Add explicit notes or links for Linux/macOS users regarding CLI usage and file path conventions.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd) and labels these examples as 'powershell', which may confuse Linux/macOS users. All command-line examples are shown in PowerShell blocks, even though the commands themselves are cross-platform. There are no explicit Linux/macOS shell examples or clarifications that these commands work equally well in Bash or other shells.
Recommendations
- Replace 'powershell' code block labels with 'console' or 'shell' where appropriate, since the commands are not PowerShell-specific.
- Add explicit Bash/Linux/macOS shell examples or clarify that the commands work on all platforms.
- Include notes indicating that tools like kubectl and sqlcmd are cross-platform and can be used in Bash, zsh, or other shells.
- Avoid labeling generic shell commands as 'powershell' unless they require PowerShell-specific syntax.
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 x64 and x86 requirements without clarifying Linux/macOS support. However, there are no explicit Windows-only tools or PowerShell examples, and the CLI commands shown are cross-platform. The overall guidance is generic, but Windows is implicitly prioritized in CLI installation links and terminology.
Recommendations
- Add explicit guidance for Linux and macOS management machines, including supported distributions and required Azure CLI versions.
- Provide links to Azure CLI installation instructions for Linux and macOS alongside Windows.
- Clarify that the Azure CLI and 'arcappliance' extension are cross-platform, and note any OS-specific limitations.
- If possible, include example commands or screenshots from Linux/macOS environments.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens with managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and output are presented first, and PowerShell is emphasized in related content. The Linux example is present and complete, but Windows tools and terminology are slightly prioritized.
Recommendations
- Alternate the order of Windows and Linux examples in each section, or present them side-by-side to avoid implicit prioritization.
- In related content, mention Azure CLI and Bash examples before or alongside PowerShell, especially for cross-platform tasks.
- Ensure that all screenshots and sample outputs are provided for both Windows and Linux, not just Windows.
- Clarify that both Windows and Linux are equally supported, and highlight any platform-specific differences.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, with dedicated tables for each OS and clear links to relevant extension documentation. However, Windows extensions are presented first, which may subtly signal prioritization. All deployment methods (CLI, PowerShell, portal, ARM templates) are mentioned equally for both OSes, and partner extensions are shown for both platforms. No critical Linux omissions or Windows-only patterns are present.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or explicitly state that both OSes are equally supported.
- Ensure that linked deployment guides (e.g., Azure CLI, PowerShell) include Linux-specific examples and instructions where relevant.
- Add a brief introductory statement clarifying that all features described are available for both Windows and Linux, unless otherwise noted.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation generally provides parity between Windows and Linux, with clear download links and change logs for both platforms. However, there is a consistent pattern of listing Windows download links and version numbers before Linux, and some references to Windows-specific tools (e.g., PowerShell, msiexec) in troubleshooting and bug fix notes. There are also a few improvements or bug fixes that are Windows-only, but these are clearly marked. No critical features are Windows-only, and Linux users are able to access all major updates and fixes.
Recommendations
- Alternate the order of Windows and Linux download links and version columns, or present them side-by-side to avoid implicit prioritization.
- Where Windows-specific tools or commands are mentioned (e.g., msiexec, PowerShell), provide equivalent Linux instructions or clarify that the step is not required for Linux.
- Continue clearly marking platform-specific changes, and ensure Linux-specific issues and improvements are equally highlighted.
- Consider a short section at the top summarizing Linux-specific changes or linking to Linux-focused installation/troubleshooting guides.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations. However, there are signs of Windows bias: Windows examples and PowerShell syntax are presented first in the verbose logging section, and Windows-specific file paths and tools (e.g., PowerShell, %TEMP%, %ProgramData%) are referenced before their Linux equivalents. Linux examples are present and reasonably complete, but Windows is often prioritized in ordering and detail.
Recommendations
- Alternate the order of Windows and Linux examples to avoid always presenting Windows first.
- Where referencing file paths or logs, always show both Windows and Linux locations side-by-side.
- Provide Bash or shell script equivalents for PowerShell commands where possible.
- Ensure troubleshooting steps and remediation advice reference both Windows and Linux tools (e.g., 'restart HIMDS service' should mention both 'Services.msc' and 'systemctl').
- Consider a summary table or section that clearly distinguishes Windows and Linux troubleshooting steps for each major error.
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 biases: Windows tools and examples (such as PowerShell, Windows Server management, and Windows-specific tabs) are mentioned first or more prominently in several places. PowerShell and Windows-centric automation are referenced before Linux equivalents, and some links default to Windows tabs. Linux is supported, but parity in examples and tool references could be improved.
Recommendations
- Ensure that all automation and scripting references (e.g., Azure Automation runbooks) mention both PowerShell and Bash/Python equally, and provide Linux-specific examples or links where appropriate.
- When linking to documentation with OS-specific tabs (e.g., 'tabs=windows'), either link to a neutral landing page or mention both Windows and Linux options.
- In lists of supported tools and SDKs, avoid putting PowerShell or Windows tools first by default; alternate or group by platform.
- Explicitly mention Linux support in all relevant scenarios, especially in sections discussing configuration, monitoring, and automation.
- Where Windows Server management is called out, ensure a parallel mention of Linux management capabilities if available.
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. The Windows-specific note about PowerShell ISE is also more prominent. However, Linux parity is generally maintained, and both platforms are supported throughout.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel tabs to avoid implicit prioritization.
- Add any Linux-specific troubleshooting notes if relevant, similar to the PowerShell ISE note for Windows.
- Ensure screenshots and UI references are not Windows-centric if possible.
- Explicitly state that both PowerShell and Bash scripts are functionally equivalent and supported.
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-related features (such as customizing Windows VM guest settings and Windows Server Management) are mentioned explicitly, but Linux features (like agent installation via SSH) are also included. In tool mentions, Azure PowerShell is listed after Azure CLI and REST APIs, and Windows-specific tools (System Center Configuration Manager, Group Policy) are mentioned alongside cross-platform tools (Ansible). Windows examples or tools are not exclusively presented, but Windows features are sometimes listed before Linux equivalents.
Recommendations
- Ensure Linux-related features and tools are given equal prominence and detail as Windows features.
- When listing management tools, consider grouping or ordering them by platform neutrality (e.g., CLI, REST, Ansible, then PowerShell, SCCM, Group Policy).
- Add explicit Linux/macOS examples or links where possible, especially for agent installation and VM management.
- Clarify when features are Windows-only to avoid confusion for Linux users.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, indicating a minor 'windows_first' bias. There are no Windows-only tools or patterns, and Linux/macOS users are not missing any critical information.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
- Explicitly state at the beginning that both Linux/macOS (Bash) and Windows (PowerShell) are fully supported and examples are provided for each.
- Ensure that any OS-specific nuances (e.g., file encoding, carriage return handling) are clearly explained for both platforms, as is already done in the documentation.
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 PowerShell examples are consistently shown after Bash. There are no Windows-specific tools or patterns, and Linux/macOS users are fully supported via Azure CLI Bash examples. No critical sections are Windows-only.
Recommendations
- Maintain parity by continuing to provide both Bash and PowerShell examples.
- Consider clarifying in the introduction that all commands work cross-platform via Azure CLI.
- If possible, add a note that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to further guide users.
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 could be considered a minor 'windows_first' bias in ordering. No Windows-only tools, patterns, or references are present, and all instructions are cross-platform via Azure CLI. No critical sections are Windows-only.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note at the start clarifying that all CLI commands are cross-platform and can be run on any OS with Azure CLI installed.
- If relevant, mention that Azure CLI can be used in Windows Command Prompt, macOS Terminal, or Linux shells.
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
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, but PowerShell examples are always shown directly after Bash, and the structure is strictly parallel. There are no Windows-specific tools or patterns mentioned, and all commands are cross-platform (az CLI). However, the presence of PowerShell examples may create a slight perception of Windows bias, especially since Bash is shown first but PowerShell is always present, which is not strictly necessary for Linux/macOS users.
Recommendations
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- If possible, provide a brief note at the start of the tutorial indicating that all az CLI commands are cross-platform and can be run in Bash (Linux/macOS) or PowerShell (Windows).
- Optionally, add a section for macOS users if there are any subtle differences (e.g., file paths, shell syntax).
- If Bash is the primary shell for most users, consider making Bash the default and PowerShell an optional tab.
- Ensure that any references to environment setup or prerequisites mention both Bash and PowerShell environments equally.
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 throughout, but PowerShell examples are consistently presented immediately after Bash examples, not before. There are no Windows-specific tools or patterns used; all commands are cross-platform (Azure CLI, kubectl). No critical steps are Windows-only, and Linux parity is maintained. The only minor bias is the inclusion of PowerShell examples alongside Bash, which may slightly favor Windows users by offering familiar syntax, but Bash is always shown first.
Recommendations
- Maintain Bash as the primary example for cross-platform parity.
- Consider clarifying in the introduction that Bash and PowerShell examples are provided for both Linux/macOS and Windows users.
- If possible, add a note that Azure CLI and kubectl commands are fully supported on Linux/macOS.
- Ensure that Bash examples remain first in each section to reinforce Linux parity.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell examples, which is a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used; all commands rely on the Azure CLI and Helm, which are cross-platform. There are no missing Linux examples or exclusive Windows tools.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to clarify intent.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance alongside Windows instructions.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details â
Detected Bias Types
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 (e.g., variable naming, file paths), Windows conventions (backslashes, PowerShell syntax) are used. Bash examples are always shown first, so there is no 'windows_first' ordering. No Windows-only tools or patterns are used; all commands rely on the Azure CLI and Helm, which are cross-platform.
Recommendations
- Ensure that PowerShell examples use only cross-platform syntax and avoid Windows-specific conventions (e.g., backslashes in file paths) where possible.
- Clarify that both Bash and PowerShell examples are equivalent and that users can choose either based on their OS.
- Consider adding a note about Helm and Azure CLI installation on Linux/macOS if not already covered in prerequisites.
- Review PowerShell snippets for any Windows-specific assumptions (e.g., file path formats) and provide alternatives for Linux/macOS if needed.
Azure Portal
Programmatically create Azure Dashboards
...tal/azure-portal-dashboards-create-programmatically.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment instructions for Azure dashboards using the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is included as a first-class method, which may be seen as Windows-centric since PowerShell is most commonly used on Windows (though available cross-platform). The CLI examples use standard syntax that works on all platforms. There are no examples or instructions that are Windows-only, and Linux/macOS users can follow the CLI or portal instructions without issue. The only minor bias is the inclusion of PowerShell as a primary method, which may not be as familiar or native to Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is available cross-platform and provide a link to installation instructions for Linux/macOS.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS.
- Optionally, add a short note for Linux/macOS users about using Bash or other shells with the Azure CLI.
- Ensure that no PowerShell-specific steps are required for the main workflow, or provide equivalent Bash scripting examples if scripting is discussed.
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, which is a minor 'windows_first' bias (in reverse). No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm). There are no missing Linux examples or Windows-exclusive instructions.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is excellent.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right tab.
- If desired, alternate the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in nearly all sections, Bash examples are shown first, followed by PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and all commands use cross-platform Azure CLI and Helm tools. There are no missing Linux examples or Windows-only instructions.
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows, to reinforce parity.
- Ensure that any future additions (e.g., troubleshooting, file manipulation) also include both Bash and PowerShell examples.
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 into Azure Container Registry. However, the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users. The CLI example is cross-platform, but the documentation does not explicitly mention Linux/macOS compatibility or provide shell-specific guidance. There is a minor 'windows_first' bias as PowerShell is featured alongside CLI without clarifying its platform limitations.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider providing bash or shell script examples for common workflows, or link to Linux/macOS-specific guidance.
- Ensure that all critical workflows are demonstrated with cross-platform tools first, and Windows-specific tools second.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides command-line examples for Helm and Azure CLI, which are cross-platform, but it shows a Windows-style environment variable assignment ('set ACR_NAME=<container-registry-name>') without a Linux/macOS equivalent. Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but also includes Azure PowerShell and Portal, which is reasonable. Most commands use Bash syntax, but the single use of 'set' is Windows-specific and may confuse Linux/macOS users.
Recommendations
- Replace or supplement the 'set ACR_NAME=<container-registry-name>' command with the Linux/macOS equivalent: 'export ACR_NAME=<container-registry-name>'.
- Add a note clarifying that environment variable assignment differs between Windows (cmd/PowerShell) and Linux/macOS (bash/zsh).
- Ensure all environment variable examples are shown for both Windows and Linux/macOS shells, or use cross-platform syntax where possible.
- Review for any other Windows-specific commands or patterns and provide Linux/macOS alternatives.
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 references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before cross-platform tools like sqlcmd. However, sqlcmd usage is shown with a Linux/Windows-neutral example. There is no explicit Linux GUI client mentioned, and SSMS is presented as the default option. Azure CLI commands are used throughout, which are cross-platform, but the overall tone and examples favor Windows tools and patterns.
Recommendations
- Mention cross-platform SQL GUI clients (e.g., Azure Data Studio, DBeaver) alongside SSMS.
- Provide explicit Linux/macOS connection examples, including any differences in authentication or environment setup.
- Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links.
- Avoid listing SSMS first unless the majority of users are expected to be Windows-based; otherwise, present cross-platform options equally.
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 Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. However, it also references cross-platform tools (Azure CLI, Visual Studio Code extension) and does not provide Windows-only examples or prioritize Windows tools over Linux equivalents in critical sections. No Linux/macOS-specific tools or scripting environments (e.g., Bash, sqlcmd) are mentioned, and PowerShell is highlighted as a scripting option without Linux alternatives.
Recommendations
- Add examples or mention of Linux/macOS-compatible tools such as sqlcmd, Azure Data Studio, or Bash scripting for manageability.
- Clarify that PowerShell scripting is available cross-platform, or provide Bash/CLI alternatives for scripting tasks.
- List cross-platform tools before Windows-only tools, or group them by platform for clarity.
- Include guidance for Linux/macOS users where applicable, especially in the 'Tools' and 'Manageability' sections.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) and Windows NTP as a default, but also covers Linux-related endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io). Windows tools and URLs are mentioned, sometimes before Linux equivalents. However, the requirements are generally platform-neutral, and Linux endpoints are present. No PowerShell-specific instructions or Windows-only commands are given.
Recommendations
- Clarify when Windows-specific endpoints (e.g., time.windows.com) are only required for Windows deployments, and provide Linux NTP alternatives (e.g., pool.ntp.org) if relevant.
- Ensure Linux-related endpoints and tools are mentioned with equal prominence and detail as Windows ones.
- Where possible, add notes or examples for Linux management machines (e.g., how to configure outbound connectivity, NTP, etc.).
- Review the order of endpoint listings to avoid Windows-first bias unless justified by usage statistics.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the PowerShell section is presented after Bash and is equally detailed. There is no evidence of Windows-only tools or patterns, and the Azure CLI is used throughout, which is cross-platform. However, the inclusion of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is primarily associated with Windows, though it is now available cross-platform. No Linux-specific tools or patterns are missing, and Bash is presented first.
Recommendations
- Clarify that PowerShell examples are valid for Linux/macOS users (since PowerShell Core is cross-platform).
- Consider adding a note that Bash examples are suitable for Linux/macOS and PowerShell for Windows, or for users who prefer PowerShell on any OS.
- If possible, provide explicit guidance for macOS users (e.g., mention terminal usage or prerequisites for PowerShell Core).
- Ensure that any referenced scripts or files (such as onboarding scripts) are compatible with both Bash and PowerShell environments.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but the Linux example is presented first and is more concise. The Windows section introduces certutil and findstr, which are Windows-specific tools, but does not provide PowerShell alternatives or parity for Linux users. All other examples (openssl, Azure CLI, kubectl) are cross-platform and do not show Windows bias.
Recommendations
- Clarify that certutil and findstr are Windows-specific and provide PowerShell alternatives for base64 encoding if possible.
- For Linux, mention that base64 is available on macOS as well, and provide explicit macOS instructions if any differences exist.
- Consider providing a table summarizing equivalent commands for Linux, macOS, and Windows for base64 encoding.
- Ensure parity in instructions for removing headers from base64 output for both platforms.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI. In several sections, PowerShell is given equal prominence, and in some cases, appears before or immediately after CLI examples. There are no Linux-specific command-line examples (such as Bash scripts or references to Linux-native tools), but Azure CLI is cross-platform and is shown first in most cases. No Windows-only tools or patterns are mentioned, and the documentation does not reference Windows-specific behaviors. However, the presence of PowerShell examples may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
- Clearly indicate that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Add explicit notes or callouts for Linux/macOS users, clarifying that Azure PowerShell is optional and Azure CLI is fully supported.
- Consider including Bash shell script examples or references to Linux-native workflows where relevant.
- Ensure Azure CLI examples are always shown first and are complete for all tasks.
- Optionally, provide links to PowerShell installation instructions for Linux/macOS users if PowerShell usage is necessary.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell throughout, with PowerShell examples included for all major operations. CLI examples use backtick (`) line continuations, which are PowerShell-specific and may confuse Linux/macOS users. The order of examples is consistently Portal, CLI, then PowerShell, putting Windows-centric tools last but CLI examples use Windows-style syntax. There is a minor bias in log file paths, but both Windows and Linux are covered. Endpoint tables clearly distinguish Linux and Windows requirements. Overall, Linux users can complete all tasks, but some friction exists due to Windows-centric syntax and PowerShell prominence.
Recommendations
- Use standard bash-style line continuations (\) in Azure CLI examples, or provide both Windows and Linux/macOS CLI syntax.
- Explicitly note that Azure CLI commands work on Linux/macOS and provide example commands for those platforms.
- Consider listing CLI examples before PowerShell, or clarify that PowerShell is Windows-only.
- Where file paths are mentioned, always show both Windows and Linux/macOS paths side-by-side.
- Add a brief note at the start clarifying cross-platform support and tool parity.
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, listing PowerShell (a Windows-centric tool) before REST API. However, it also clearly states support for both Windows and Linux operating systems and does not provide any Windows-only examples or tools in the main content. There is a minor bias in listing PowerShell before Linux-native tools, but no critical sections are Windows-only.
Recommendations
- When listing supported experiences, consider mentioning Azure CLI (cross-platform) first, followed by PowerShell and REST API, to emphasize Linux parity.
- Add explicit statements or examples highlighting Linux support, such as referencing Bash or shell scripting alongside PowerShell.
- Ensure linked pages (CLI, PowerShell, REST) provide balanced examples for both Windows and Linux environments.
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 without specifying Bash or Linux shell equivalents. PowerShell is mentioned before any Linux-specific scripting tools, and no explicit Linux/macOS examples or tools are referenced. However, the context is general and does not provide actual script examples, so the bias is minor.
Recommendations
- Clarify that Azure Copilot can generate Bash scripts or Linux shell commands in addition to PowerShell scripts.
- Explicitly mention support for Bash or other Linux/macOS scripting environments when listing script generation capabilities.
- Provide example prompts or outputs for both PowerShell and Bash/CLI to demonstrate parity.