234
Pages Scanned
50
Pages Flagged
234
Changed Pages
21.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:10
Scan Information
Started At: 2026-02-19 00:00:10
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 234
Files Completed: 234
Problematic Pages
52 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 heavily features PowerShell scripts (.ps1) and instructs users to use Windows-specific tools (winget) for installing prerequisites. All example commands are given in PowerShell syntax, and there are no equivalent Bash or Linux/macOS instructions. The documentation assumes a Windows environment throughout, creating friction for Linux/macOS users.
Recommendations
- Provide Bash shell script equivalents for the onboarding scripts (e.g., infra_onboarding.sh, cm_onboarding.sh) and document their usage.
- Include instructions for installing Azure CLI and kubectl on Linux/macOS (e.g., using apt, yum, brew) instead of only winget.
- Add example commands for Linux/macOS terminals alongside PowerShell examples.
- Clarify OS compatibility of the scripts and, if Windows-only, explicitly state this in the prerequisites.
- Consider providing cross-platform scripts or containerized solutions for onboarding.
Create Pull Request
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
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a notable Windows bias in several areas: PowerShell scripts and Windows-specific tools (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, often with step-by-step instructions and example scripts, while equivalent Linux automation (e.g., Bash scripts for cleanup, package manager automation, systemd integration) is not provided. Windows methods and tools are sometimes presented first or with more depth. The cleanup script for stale resources is PowerShell-only, with no Linux CLI or Bash equivalent. Proxy configuration for Windows includes detailed environment variable handling and service restart instructions, while Linux relies on a bundled script but lacks deeper automation examples.
Recommendations
- Provide equivalent Bash or shell scripts for Linux users, especially for tasks like cleanup of stale Arc resources.
- Include automation examples for Linux (e.g., using cron, systemd, or Ansible) where Windows automation is described (e.g., Group Policy, WSUS).
- Balance the depth of instructions: offer step-by-step guidance for Linux package manager automation and system configuration, similar to Windows.
- When presenting methods, alternate the order or group by OS rather than consistently leading with Windows.
- Expand Linux proxy configuration guidance to include manual environment variable setup and service restart instructions, matching Windows detail.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (.ps1) for bulk deployment and workflow deletion. There are no Bash or Linux/macOS shell examples, and the only provided automation scripts are Windows PowerShell (.ps1) files. This creates friction for Linux/macOS users, as they must adapt the examples and cannot use the provided scripts directly.
Recommendations
- Provide Azure CLI command examples in Bash syntax, as Azure CLI is cross-platform.
- Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or note how Linux/macOS users can achieve the same workflow.
- Explicitly state that the PowerShell scripts are Windows-only and provide guidance for Linux/macOS users.
- Add a section clarifying cross-platform support and any limitations for Linux/macOS users.
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 (.ps1) script for clean-up operations, with all usage examples and instructions tailored to PowerShell. There are no Bash, shell, or cross-platform alternatives, nor any mention of how Linux/macOS users can perform the same tasks. This creates friction for non-Windows users.
Recommendations
- Provide a Bash or shell script equivalent for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core (pwsh) on non-Windows platforms.
- Include explicit instructions and examples for running the script on Linux/macOS, such as using PowerShell Core or adapting the script for Bash.
- Clarify any Windows-specific dependencies or limitations of the script, and suggest alternatives if possible.
Azure Arc
Migrate Existing Target Resources to General Availability
...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux shell alternatives, or cross-platform scripting. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
- Provide a Bash or shell script equivalent for Linux/macOS users.
- Document how to run the PowerShell script using PowerShell Core on Linux/macOS, including installation instructions if necessary.
- Clarify whether the migration script is cross-platform or Windows-only, and update prerequisites accordingly.
- If only PowerShell is supported, explicitly state this and offer guidance for Linux/macOS users to install PowerShell Core.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax and references Windows-style command lines (e.g., PowerShell blocks for kubectl exec/sqlcmd), without offering equivalent Linux/macOS shell examples. The use of PowerShell is unnecessary for cross-platform tools like kubectl and sqlcmd, and may confuse Linux/macOS users. Additionally, Windows-style command blocks are shown first and exclusively.
Recommendations
- Replace PowerShell code blocks with generic shell (bash/sh) examples, or provide both PowerShell and bash versions.
- Clarify that kubectl and sqlcmd commands are cross-platform and can be run from any OS terminal.
- Add explicit Linux/macOS shell examples for connecting to the SQL Server pod and running sqlcmd.
- Use 'console' or 'shell' code block syntax instead of 'powershell' for cross-platform commands.
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 Windows/PowerShell-specific tools (Invoke-AksEdgeNodeCommand) for Linux node configuration without providing native Linux command alternatives. This creates friction for Linux users who may not have access to PowerShell or Windows tools, and omits direct Linux shell examples for sysctl configuration.
Recommendations
- Provide native Linux shell commands for sysctl configuration, e.g., 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
- Clarify whether Invoke-AksEdgeNodeCommand is required, and if so, provide Linux-native alternatives or explain how Linux users can achieve the same result without PowerShell.
- Ensure all steps for Linux node preparation can be completed using standard Linux tools and commands, not Windows/PowerShell-centric utilities.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly lists PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools like Azure CLI and Visual Studio Code. There are no explicit Linux/macOS examples or mentions of Linux-native tools, and Windows tools are listed without Linux alternatives or parity discussion.
Recommendations
- Add examples or references for Linux/macOS management tools (e.g., sqlcmd, Azure Data Studio, Bash scripting).
- Clarify which tools are cross-platform and which are Windows-only.
- Provide parity guidance for PowerShell scripting, such as Bash or Python alternatives for Linux/macOS users.
- Explicitly mention Azure CLI usage for common management tasks, with example commands.
- Consider listing cross-platform tools before Windows-only tools in the Tools section.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., C:\Backupfiles\test.bak) and referencing tools like SQL Server Management Studio (SSMS) without mentioning cross-platform alternatives. Linux/macOS equivalents for file paths and backup procedures are not provided, which may hinder non-Windows users.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/user/backup/test.bak) alongside Windows paths in backup and restore commands.
- Mention and provide examples using cross-platform tools such as Azure Data Studio for database connections and queries, in addition to SSMS.
- Clarify that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links or notes for Linux/macOS users.
- Where commands reference local file paths (e.g., for kubectl cp), show both Windows and Linux/macOS variants.
- Explicitly state that all steps can be performed from Linux/macOS unless a step is Windows-only, and provide alternatives where necessary.
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 instructions are more detailed and appear after the Linux example. The Windows section introduces certutil and findstr, but does not mention Linux equivalents for removing headers. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and generally favors Linux-first examples, but the Windows-specific encoding instructions are more prominent and lack parity in header removal for Linux.
Recommendations
- Provide explicit Linux/macOS commands for removing certificate headers (e.g., using grep or sed) to match the Windows findstr example.
- Clarify that base64 encoding and header removal steps are needed on both platforms, and show both sets of commands side-by-side.
- Consider mentioning macOS as well, since it is similar to Linux for these operations.
- Ensure that Windows and Linux instructions are equally detailed and easy to follow.
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 where Windows-specific tools, patterns, and examples are mentioned before or instead of Linux equivalents. For example, PowerShell is referenced for troubleshooting HTTP2 issues, and Windows paths are shown in error messages. Linux-specific troubleshooting steps (such as using curl, wget, or Linux shell commands) are largely absent, and Linux CLI usage is only briefly mentioned (e.g., glibc error). The guidance for network/proxy/DNS troubleshooting often assumes Windows environments (e.g., Resolve-DnsName, nslookup, ping), and PowerShell is used for HTTP2 validation, with no Linux alternative provided.
Recommendations
- Add Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl for HTTP2 troubleshooting, dig for DNS resolution).
- Ensure troubleshooting steps reference both Windows and Linux tools where applicable (e.g., show how to check proxy settings/environment variables on Linux).
- Include Linux-specific error messages and their resolutions, especially for Azure CLI and network troubleshooting.
- Where Windows paths or tools are referenced, clarify if the guidance applies to Linux/macOS and provide alternate instructions if needed.
- Review all command examples and ensure Linux/macOS users are equally supported, especially in sections about CLI usage, network diagnostics, and proxy configuration.
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 the azcmagent CLI. While most examples and instructions are platform-neutral, there is a notable Windows bias in several areas: the interactive browser login is described as 'Windows only' and is discussed first; certificate authentication includes detailed instructions for Windows certificate stores but omits Linux/macOS equivalents; access token acquisition references PowerShell's Get-AzAccessToken without mentioning Linux/macOS alternatives. These biases may create friction for Linux/macOS users, though most features are available cross-platform.
Recommendations
- Present authentication options in a platform-neutral order, or explicitly note Linux/macOS alternatives alongside Windows-specific instructions.
- For certificate authentication, add guidance for Linux/macOS users (e.g., storing certificates in files, using PEM/PFX formats, relevant file permissions).
- When referencing access token acquisition, include Azure CLI (az account get-access-token) and other cross-platform methods, not just PowerShell.
- Where Windows-specific tools or stores are mentioned, provide equivalent Linux/macOS instructions or clarify if no equivalent exists.
- Consider adding explicit Linux/macOS examples in the 'Examples' section, such as using shell commands for hostname or certificate paths.
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 deployment instructions exclusively using Azure PowerShell commands, with no Azure CLI or Bash examples. All deployment steps and code blocks use PowerShell syntax, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, PowerShell is presented as the primary (and only) method for deploying ARM templates, even though Azure CLI is cross-platform and commonly used on Linux/macOS. The documentation does provide parity in ARM template examples for both Linux and Windows extensions, but the deployment tooling is Windows-centric.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell for all deployment steps, e.g., using 'az deployment group create'.
- Mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider showing Bash script examples for template deployment where appropriate.
- Clarify that PowerShell is not required and that users can use their preferred tooling.
Azure Arc
Recover from accidental deletion of resource bridge VM
...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation exclusively provides recovery instructions for the Azure Arc resource bridge VM using a Windows-based PowerShell script. There are no examples or guidance for Linux/macOS users, nor are cross-platform tools or alternatives mentioned. The script provided is Windows-specific, and the section is titled 'Recover Arc resource bridge from a Windows machine,' with no equivalent Linux/macOS section.
Recommendations
- Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
- If the recovery process is fundamentally Windows-only, clarify this limitation explicitly in the prerequisites.
- Mention any cross-platform alternatives or explain why only Windows is supported.
- Add a note about the lack of Linux/macOS support and suggest workarounds if possible (e.g., running the script in a Windows VM or container).
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
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs, but the primary automation script is PowerShell-based and references Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents, and Linux-specific automation guidance is minimal. While out-of-band methods mention Ansible playbooks (Linux-friendly), the main scripted method and examples are Windows-centric.
Recommendations
- Provide a Bash or Python version of the automation script for Linux/macOS users, or clarify if the script is cross-platform.
- Include instructions for running the automation script as a cron job on Linux (using 'crontab') alongside the Windows Task Scheduler example.
- Offer explicit Linux/macOS terminal usage examples for script execution, not just PowerShell.
- Ensure parity in prerequisites and troubleshooting for both Windows and Linux environments.
- Highlight Ansible playbook usage with a sample for Linux users, and link to relevant Linux onboarding documentation.
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 script with a .ps1 extension, which is Windows/PowerShell-specific. There are no Bash or Linux/macOS shell examples, nor any mention of how to run the onboarding script on Linux or macOS. The instructions assume the use of Windows tools and editors, creating friction for Linux/macOS users who may need to adapt the process.
Recommendations
- Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
- Explicitly state platform requirements for the onboarding script and offer guidance for Linux/macOS environments (e.g., using PowerShell Core, prerequisites, or alternative steps).
- If the onboarding script is PowerShell-only, recommend using PowerShell Core (pwsh) and provide instructions for installing and running it on Linux/macOS.
- Add notes about editing scripts on Linux/macOS, including compatible editors and file path conventions.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions and examples for Windows users, particularly when running the deboarding script, with explicit PowerShell commands and notes for Windows environments. There is no equivalent Linux/macOS example or guidance for running the script, and Windows instructions are presented first and in greater detail. This creates friction for Linux/macOS users who may need to adapt the process themselves.
Recommendations
- Add explicit instructions and examples for running the deboarding script on Linux/macOS, including shell commands and prerequisites.
- Clarify whether the deboarding script is cross-platform (e.g., if it can be run with PowerShell Core on Linux/macOS or if a Bash version exists).
- Present Windows and Linux/macOS instructions in parallel sections, or clarify platform limitations early in the document.
- Include troubleshooting tips for Linux/macOS users, such as handling execution policies or script permissions.
Azure Arc
Diagnostics of Edge-Related Logs and Errors in Workload Orchestration
.../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page provides nearly all CLI/script examples in PowerShell syntax, uses Windows-style file paths in JSON templates, and references PowerShell scripts for orchestration. There are no Bash or Linux/macOS shell equivalents, and Windows-specific conventions (e.g., backslashes, drive letters) are used throughout. This creates friction for Linux/macOS users, who must adapt commands and paths manually.
Recommendations
- Provide Bash/zsh/Linux/macOS shell equivalents for all PowerShell script examples, especially for az CLI commands.
- Use platform-neutral file path examples in JSON templates (e.g., /home/user/config.yaml instead of C:\Users\... or E:\...).
- Clearly indicate when a script is Windows-only or provide cross-platform alternatives.
- Add notes or links to Linux/macOS onboarding guides for Azure Arc and workload orchestration.
- Where possible, use az CLI syntax that works identically on all platforms, and avoid PowerShell-specific line continuations (`) in examples.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses 'winget', a Windows-only tool, with no Linux/macOS alternative. In the section on extracting ZIP files, the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a standard Bash/Linux tool. Throughout, Windows-centric tools and patterns are presented first or exclusively, and Linux/macOS equivalents are missing or unclear. The PowerShell and Bash tabs often use Windows paths (e.g., 'C:\path\to\archive.zip') and commands that are not portable to Linux/macOS.
Recommendations
- Provide Linux/macOS-specific instructions for installing kubectl (e.g., using 'curl', 'apt', 'brew', or direct download).
- For extracting ZIP files, use standard Bash/Linux commands like 'unzip' or 'tar', and provide examples with Linux-style paths.
- Ensure Bash examples use cross-platform commands and paths, and clarify when a command is Windows-only.
- Add explicit notes or tabs for macOS where relevant, especially for installation steps.
- Review all Bash sections to ensure they are valid for Linux/macOS users, not just Windows users running Bash or PowerShell.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command 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 for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, which offers both Bash and PowerShell tabs. This creates friction for Linux/macOS users, who must translate PowerShell commands themselves.
Recommendations
- Provide Bash/Linux equivalents for all Azure CLI, Docker, and kubectl commands.
- Use cross-platform syntax (e.g., az CLI, kubectl, docker) in examples, and avoid PowerShell-specific constructs unless required.
- Clearly indicate when a command is Windows-only or provide alternative instructions for Linux/macOS.
- For scripting tasks (e.g., Base64 encoding, JSON file creation), offer both PowerShell and Bash methods.
- Review and update troubleshooting steps to ensure Linux/macOS users can follow along without needing to translate PowerShell code.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is a Windows-centric tool, though it is now cross-platform. The documentation does not mention Linux-native tools or workflows (such as Bash scripts or Docker commands for import), and the Azure PowerShell example may create friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
- Add explicit Bash shell examples for image import using Azure CLI, highlighting Linux/macOS compatibility.
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider mentioning Docker CLI commands for image manipulation as an alternative for Linux/macOS users.
- If PowerShell is included, note its cross-platform support and provide guidance for Linux/macOS installation.
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 both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal prominence throughout, despite being primarily a Windows tool. In several sections, PowerShell commands are presented as a main option rather than as an alternative for Windows users. There are no explicit Linux/macOS-specific command-line examples (e.g., bash scripting, environment variable usage in Linux shells), and the documentation does not clarify platform differences or provide Linux/macOS-specific guidance. While the CLI examples are cross-platform, the prominence of PowerShell and lack of explicit Linux/macOS context may create friction for non-Windows users.
Recommendations
- Clearly indicate that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is cross-platform.
- Add explicit bash/zsh/Linux shell examples for scripting scenarios (e.g., using export instead of set for environment variables, using Linux shell syntax for piping tokens).
- In sections where PowerShell is shown, provide a corresponding Linux/macOS shell example or clarify that PowerShell is optional.
- When referencing environment variables, show both Windows (set/PowerShell) and Linux (export/bash) syntax.
- Consider reordering examples to show Azure CLI (cross-platform) first, and PowerShell as an alternative for Windows users.
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 Linux and Windows information for the Azure Connected Machine agent, but Windows-related resources and tools (such as Windows Admin Center and Windows installation package URLs) are often mentioned first or in more detail. Windows-specific service tags and tools are listed before Linux equivalents, and Windows Admin Center scenarios are highlighted, while Linux management tools are not mentioned. However, Linux installation URLs and OpenSSL guidance are present, and most instructions are cross-platform.
Recommendations
- Ensure Linux examples and tools are given equal prominence alongside Windows tools (e.g., mention Linux management tools if relevant).
- When listing URLs or service tags, alternate the order or group by platform to avoid always listing Windows first.
- Add explicit references to Linux equivalents for Windows Admin Center scenarios, or clarify if no equivalent exists.
- Include troubleshooting links for Linux networking/TLS issues, similar to the Windows-specific troubleshooting link provided.
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, which is a minor form of bias ('windows_first') as it favors Linux/macOS users by showing their examples first. There are no missing Linux examples, no exclusive mention of Windows tools, and no PowerShell-heavy content.
Recommendations
- No significant changes needed. The documentation already provides full parity for Linux and Windows users.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to avoid perceived bias.
- Explicitly state that both Bash and PowerShell are supported and that users should select the tab appropriate for their environment.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are sometimes shown immediately after Bash, and some minor details (such as base64 encoding commands) are slightly more Windows-centric. The documentation does not exclusively mention Windows tools or patterns, and Linux-specific commands are present throughout. There is no critical bias preventing Linux/macOS users from completing the tasks.
Recommendations
- Ensure Bash and PowerShell examples are equally prominent, possibly by alternating which is shown first or by clarifying that Bash is for Linux/macOS and PowerShell for Windows.
- Where minor differences exist (such as file encoding or base64 commands), add explicit notes for both platforms.
- Consider adding a brief section at the top clarifying which shell to use for which OS, and that all steps are cross-platform unless otherwise noted.
- Review PowerShell snippets for unnecessary Windows-specific syntax and ensure Bash equivalents are accurate and complete.
Azure Arc
Multiple Solutions with a Single Shared Dependency at Different Levels
...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-specific tools or patterns used, and Linux examples are present throughout. The Azure CLI and Helm are cross-platform tools, and no steps are exclusive to Windows or PowerShell. However, the ordering of examples (Bash first, PowerShell second) is the only minor evidence of bias.
Recommendations
- Consider explicitly stating that both Bash and PowerShell examples are equivalent and supported on all platforms.
- Ensure that Bash and PowerShell tabs are equally visible and accessible.
- If possible, clarify that PowerShell examples can be run on Linux/macOS as well (using PowerShell Core).
- Add a note about cross-platform compatibility of Azure CLI and Helm.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and linked more prominently. There are no explicit Linux/macOS examples or screenshots, and the text refers to copying values into 'a text document' without platform-specific guidance. However, Azure CLI is included, which is cross-platform.
Recommendations
- Alternate the order of PowerShell and Azure CLI references to avoid Windows-first bias.
- Explicitly mention that Azure CLI works on Linux and macOS, and provide example commands for those platforms.
- Include screenshots or instructions that reflect Linux/macOS environments where relevant.
- Clarify that copying to clipboard and pasting works similarly across all platforms, or provide platform-specific tips if there are differences.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned as cross-platform, SSMS is listed before sqlcmd, and no Linux-native graphical client alternatives (such as Azure Data Studio or DBeaver) are suggested. The examples and instructions are generally applicable to both Windows and Linux, but the documentation subtly prioritizes Windows tools and patterns.
Recommendations
- Mention cross-platform graphical SQL clients such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting using sqlcmd on Linux (e.g., specifying the shell environment or package installation instructions).
- List sqlcmd before SSMS to emphasize cross-platform parity.
- Add a note clarifying that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides installation instructions for client tools used with Azure Arc-enabled data services. While it includes links for Windows, Linux, and macOS for most tools, there are signs of Windows bias: Windows installation links are listed first, PowerShell/cmd.exe is referenced specifically for Windows users, and Linux installation instructions for curl are vague ('install curl package') compared to explicit Windows links. There is also a note about PowerShell's curl alias, but no equivalent Linux/macOS shell guidance.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first ordering.
- Provide explicit Linux/macOS installation commands for tools like curl (e.g., 'sudo apt install curl', 'brew install curl').
- Add shell-specific notes for Linux/macOS users where PowerShell-specific guidance is given (e.g., explain curl usage in bash/zsh).
- Ensure parity in detail and clarity for Linux/macOS instructions compared to Windows.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides cross-platform instructions and examples, with explicit Linux/Ubuntu guidance for kubelogin installation and generic shell commands for cluster configuration. However, in the section on installing Azure kubelogin, Windows and Mac are mentioned first, with Linux/Ubuntu instructions following. The overall guidance is platform-neutral, but minor ordering bias is present.
Recommendations
- Present Linux/macOS installation instructions alongside Windows, or in a neutral order (e.g., alphabetical).
- Where possible, clarify that all CLI commands are cross-platform unless otherwise noted.
- Explicitly mention macOS in shell command examples if relevant.
- Ensure that screenshots and portal instructions are equally applicable to all 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 lists Azure PowerShell examples after Azure CLI. There are no Linux-specific command-line examples (e.g., Bash scripts), but the CLI examples are cross-platform. The PowerShell examples, while useful for Windows users, may create friction for Linux/macOS users who are less likely to use PowerShell. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained, but the documentation could better highlight Linux/macOS workflows.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and preferred for Linux/macOS environments.
- Add brief notes or examples for Bash scripting or shell environments where relevant (e.g., setting environment variables).
- Consider mentioning that Azure PowerShell is available on Linux/macOS, but CLI is typically more native.
- Ensure that Linux/macOS users are guided to use Azure CLI for all tasks, and clarify any differences in environment variable syntax (e.g., export vs. $Env).
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, the overall guidance is generic and does not appear to exclude Linux/macOS management machines or tools.
Recommendations
- Add explicit statements clarifying that Linux and macOS management machines are supported for Azure CLI and Arc resource bridge deployment.
- Provide installation links for Azure CLI on Linux and macOS alongside Windows, or use the main Azure CLI install page that covers all platforms.
- Mention any OS-specific requirements or limitations for the management machine, if applicable.
- If possible, include example commands or screenshots for Linux/macOS environments.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent. While most features and fixes are presented in parallel for both platforms, Windows download links and version numbers are consistently listed first, and Windows-specific tools (such as PowerShell, msiexec, and GUI installer instructions) are mentioned without Linux equivalents. Some instructions and known issues are Windows-only, but Linux parity is generally maintained for core agent functionality.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
- When referencing Windows installation methods (e.g., msiexec, PowerShell), provide equivalent Linux installation instructions (e.g., using rpm, deb, or shell scripts) in the same section.
- Include troubleshooting tips for Linux installer issues alongside Windows installer known issues.
- Ensure that improvements or bug fixes referencing Windows tools (such as PowerShell scripts) also mention Linux alternatives if applicable.
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 throughout, but PowerShell examples are often shown alongside CLI, and occasionally Windows-specific notes are included (e.g., log file paths, PowerShell command syntax). Windows tools and patterns are referenced (such as PowerShell and Windows log locations), but Linux equivalents are also provided. In some sections, Windows is mentioned first (e.g., log viewing), and download.microsoft.com is referenced as the Windows installation package source, while packages.microsoft.com is referenced for Linux. Overall, Linux parity is good, but minor Windows-first ordering and PowerShell emphasis are present.
Recommendations
- Ensure CLI examples are presented before PowerShell, as CLI is cross-platform.
- Explicitly state that all CLI commands work on both Windows and Linux/macOS.
- Where file paths or log locations are mentioned, always provide both Windows and Linux equivalents side-by-side.
- Avoid phrasing that implies Windows is the default (e.g., 'On Windows...' before 'On Linux...').
- Consider adding Bash shell examples for Linux users where relevant.
- Clarify that onboarding and management can be performed equally from Linux/macOS systems.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page lists connectivity requirements for the Arc resource bridge, including both Windows and Linux-related endpoints. However, Windows-specific services (such as 'time.windows.com' for NTP and 'sts.windows.net' for authentication) are mentioned, and Windows terminology (e.g., 'Management machine', 'Windows NTP') appears before Linux equivalents. There is a slight bias toward Windows tools and endpoints, but Linux endpoints (such as 'packages.microsoft.com' and 'linuxgeneva-microsoft.azurecr.io') are also included. No OS-specific command examples are given, and the requirements are generally platform-neutral.
Recommendations
- Clarify when Windows-specific endpoints (e.g., 'time.windows.com', 'sts.windows.net') are only required for Windows deployments, and provide Linux equivalents (such as 'pool.ntp.org' for NTP) where appropriate.
- Add notes or examples for Linux management machines, including any differences in required endpoints or ports.
- Ensure that Linux-related endpoints and requirements are given equal prominence and are not listed after Windows-specific ones.
- Where possible, use OS-neutral language (e.g., 'management machine' instead of 'Windows management machine') unless the requirement is truly OS-specific.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All management methods (CLI, PowerShell, portal, templates) are mentioned together, and partner extensions are shown for both OSes. No examples or instructions are Windows-only, and Linux extensions are well-represented.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side, to avoid implicit prioritization.
- Explicitly state that all management methods (CLI, PowerShell, portal, templates) support both Windows and Linux, and provide links to Linux-specific usage guides where relevant.
- If possible, add a brief section or example showing deployment of an extension to a Linux VM using Azure CLI or templates, to reinforce parity.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation presents Windows/PowerShell examples before Linux/Bash equivalents and uses PowerShell as the primary scripting language for Windows. Linux instructions are present and reasonably complete, but Windows examples and terminology are given first, which may create minor friction for Linux users.
Recommendations
- Alternate the order of Windows and Linux examples, or present both in parallel to avoid implicit prioritization.
- Explicitly state that both Windows and Linux are equally supported at the start of technical sections.
- Where possible, provide cross-platform examples (e.g., Azure CLI) in addition to OS-specific scripts.
- Ensure that screenshots and sample outputs are provided for both Windows and Linux, not just one platform.
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
powershell_heavy
windows_first
Summary
The documentation page references Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI in metadata and in the 'Next steps' section, potentially implying a Windows-first or PowerShell-heavy bias. However, the page does state that both Windows and Linux are supported, and notes a Linux-specific limitation. No explicit Linux command examples or Linux-specific tooling are provided on this overview page.
Recommendations
- Ensure Linux-specific examples and limitations are equally highlighted, especially in introductory and 'Next steps' sections.
- Consider mentioning Bash or shell scripting as a supported experience for Linux users, if applicable.
- Add explicit links or references to Linux-focused documentation or examples, not just PowerShell.
- Clarify parity between Windows and Linux in terms of supported scripting languages and tools.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation 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-specific tools and features (e.g., PowerShell, Windows Server management, Windows registry, Windows tabs in links) are often mentioned first or exclusively, and some links default to Windows-focused tabs. While Linux is supported and referenced, Linux examples or tools are less prominent or are mentioned after Windows equivalents.
Recommendations
- Ensure that all feature and tool mentions (e.g., Azure Automation, Update Manager, VM extensions) explicitly reference both Windows and Linux where supported, and provide parity in examples.
- When linking to docs with OS-specific tabs, use neutral or Linux-first tabs where possible, or clarify support for both OSes in the surrounding text.
- In lists of supported tools (CLI, PowerShell, SDKs), avoid placing PowerShell or Windows tools first by default; alternate or group by platform.
- Add explicit Linux examples or references (e.g., Bash, Linux daemons, Linux configuration) alongside Windows/PowerShell examples.
- Highlight Linux-specific capabilities or considerations where relevant, to reassure Linux users of full support.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and PowerShell notes are presented first and in greater detail. Windows-specific guidance (e.g., Set-ExecutionPolicy, PowerShell ISE warning) is more prominent, while Linux instructions are concise and lack equivalent troubleshooting or environment-specific notes. The retry command section also lists Windows before Linux.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid 'Windows first' bias.
- Add Linux-specific troubleshooting notes (e.g., common Bash issues, permissions, shell environment advice) similar to the PowerShell ISE warning for Windows.
- Ensure parity in detail and guidance for both platforms, including any script prerequisites or environment setup steps.
- Consider a tabbed interface or clear separation for Windows and Linux instructions to improve clarity and accessibility.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for the Azure Arc agent, but Windows tools (.NET Framework, PowerShell) are listed first and in more detail, with download links. Linux requirements are mentioned briefly and lack equivalent guidance or links. There are no Linux-specific examples or instructions, and Windows tools are referenced before Linux equivalents.
Recommendations
- Provide download links or installation instructions for Linux prerequisites (e.g., systemd, wget).
- Include Linux-specific examples or scripts where Windows scripts are referenced.
- Present Linux and Windows requirements in parallel, rather than listing Windows first.
- Clarify any differences in onboarding or agent installation between Windows and Linux VMs.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. While it covers both Windows and Linux enhancements, Windows-specific features (such as guest OS customization and Windows Server Management) are often mentioned before Linux equivalents. Windows tools like Azure PowerShell and System Center Configuration Manager are listed alongside cross-platform tools, but Windows-centric methods are sometimes presented first or more prominently. There is a slight tendency to highlight Windows-related capabilities and tools before Linux ones, though Linux support is also referenced (e.g., SSH-based agent installation, Ansible playbook).
Recommendations
- Ensure Linux examples and tools (such as Bash, Ansible, and SSH) are given equal prominence and are listed before or alongside Windows tools.
- Where possible, provide explicit Linux/macOS usage examples for features that currently only mention Windows tools or patterns.
- Review the ordering of bullet points and sections to avoid consistently placing Windows-specific features or tools first.
- Clarify when features are cross-platform versus Windows-only to help Linux/macOS users quickly identify relevant information.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are mentioned, and Linux examples are present throughout.
Recommendations
- Maintain the current approach of providing both Bash and PowerShell examples.
- Consider alternating the order of examples (e.g., sometimes showing PowerShell first, or grouping by OS) to further reduce perceived bias.
- Explicitly state that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users, to clarify applicability.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for setting up workload orchestration, but consistently presents Bash instructions first and PowerShell instructions second. There is no evidence of exclusive Windows tools or missing Linux examples, as all commands use the cross-platform Azure CLI. However, the PowerShell section is nearly as prominent as Bash, which may create a slight perception of Windows bias.
Recommendations
- Continue to provide both Bash and PowerShell examples, but clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider adding a brief note at the top of the examples section stating that Bash is suitable for Linux/macOS and PowerShell for Windows, and that Azure CLI is fully cross-platform.
- If possible, add a third tab for 'macOS/Linux' or 'Command Prompt' to further reinforce parity.
- Ensure that any references to file paths, environment variables, or shell-specific syntax are accurate for both platforms.
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, rather than in parallel or with equal prominence. There are no Windows-only tools or patterns, and all instructions are based on the Azure CLI, which is cross-platform. No Linux examples are missing, and no Windows-specific tools are mentioned.
Recommendations
- Consider presenting Bash and PowerShell examples side-by-side (e.g., using tabs or columns) to reinforce equal parity.
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Ensure that Bash and PowerShell examples are equally prominent in headings and formatting.
- Add a brief note for macOS users if there are any OS-specific considerations (none detected here, but could be helpful in general).
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, 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. There are no Windows-specific tools, patterns, or terminology used exclusively or preferentially. All instructions are cross-platform and rely on the Azure CLI, which is available on both Windows and Linux/macOS.
Recommendations
- No changes needed for Linux parity. The documentation already provides Bash examples first, which is preferable for Linux/macOS users.
- If desired, clarify that Azure CLI commands work on both Linux/macOS and Windows, and that PowerShell syntax is provided for Windows users.
- Consider adding a brief note at the top indicating that all CLI commands are cross-platform and that both Bash and PowerShell examples are available.
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 page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash/Linux shell examples for those commands. Throughout the rest of the document, CLI instructions are generally shown in Bash syntax, but the presence of PowerShell-only examples and occasional use of Windows-style command formatting suggests a mild Windows bias.
Recommendations
- For every PowerShell CLI example, provide a Bash/Linux shell equivalent, especially for commands using Azure CLI.
- Ensure that CLI instructions use cross-platform syntax (e.g., avoid PowerShell backticks for line continuation; use Bash line continuation with '\' where appropriate).
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and clarify any OS-specific nuances.
- Review all command snippets to ensure they are not inadvertently formatted in a Windows-centric way.
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, but PowerShell is given equal prominence and detail throughout. In some sections, PowerShell examples are shown immediately after Bash, and the PowerShell syntax is explained in depth. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the presence of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is primarily used on Windows, though it is available cross-platform.
Recommendations
- Consider clarifying that PowerShell examples are also valid for PowerShell Core on Linux/macOS, to avoid implying Windows exclusivity.
- Add a brief note at the start of the tutorial explaining that both Bash and PowerShell examples are cross-platform, and that users can choose either based on their environment.
- If possible, provide a third example for native macOS/Linux shell users (e.g., Zsh), or clarify that Bash examples are suitable for all Unix-like systems.
- Ensure that Bash examples are shown first in each section, as is currently done, to reinforce Linux parity.
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. Azure PowerShell is presented as a distinct method, and PowerShell examples are included. However, the CLI examples are generic and cross-platform, and there are no Windows-specific tools or patterns used. The PowerShell section is not presented first, but its inclusion may signal a slight Windows bias. The JSON dashboard examples reference both Linux and Windows VM creation links, showing parity in resource types.
Recommendations
- Clarify that Azure PowerShell is available on Linux and macOS, not just Windows.
- Consider mentioning Bash or shell scripting for Azure CLI usage, especially for Linux/macOS users.
- Add a note that all CLI commands work equally on Linux, macOS, and Windows.
- If possible, provide a Bash script example for deploying dashboards using Azure CLI.
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 is generally cross-platform, focusing on Helm and Azure CLI commands, which work on Windows, Linux, and macOS. However, there are subtle Windows-first biases: the environment variable setup uses the Windows 'set' command without showing the equivalent Linux/macOS 'export' command, and the prerequisites mention Azure PowerShell before Azure CLI and portal for AKS creation. No explicit Linux/macOS examples are provided for environment variable setup, which could cause friction for non-Windows users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- When listing prerequisites or creation methods, mention Azure CLI and portal before Azure PowerShell, or clarify that all options are available cross-platform.
- Add a note clarifying that all shown CLI commands work on Linux/macOS unless otherwise stated.
- Review other command snippets to ensure they are not Windows-centric and add Linux/macOS equivalents where needed.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently lists Azure PowerShell examples immediately after Azure CLI, and references PowerShell in prerequisites and installation instructions. However, Azure CLI is cross-platform and all examples are equally applicable to Linux/macOS users. No Windows-specific tools, commands, or patterns are used, and there are no missing Linux/macOS examples. The only minor bias is the ordering of PowerShell examples after CLI, which may give a slight impression of Windows-first documentation.
Recommendations
- Clarify early that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider explicitly mentioning that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- If possible, add a brief note in the prerequisites section indicating that all commands shown (CLI and PowerShell) work on Linux, macOS, and Windows, except where noted.
- Optionally, provide a table or section comparing CLI and PowerShell usage across platforms.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as showing usage and changing SKU), but consistently lists PowerShell after CLI and does not provide explicit Linux/macOS shell examples or mention cross-platform parity. There are no examples for Bash scripting, and PowerShell is referenced without clarifying that Azure CLI is the recommended cross-platform tool. This may cause friction for Linux/macOS users, especially those unfamiliar with PowerShell.
Recommendations
- Clearly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Provide explicit Bash shell examples where relevant, or clarify that Azure CLI commands work on all platforms.
- When listing both CLI and PowerShell, consider listing CLI first and labeling PowerShell as 'for Windows users' or similar.
- Add a brief section or note about tool parity for different OSes, reassuring Linux/macOS users that all features are available via CLI and REST API.
- Where PowerShell is shown, consider also showing the equivalent Bash/CLI invocation for parity.