231
Pages Scanned
51
Pages Flagged
231
Changed Pages
22.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-02-25 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 231
Files Completed: 231
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 is heavily biased towards Windows, with all onboarding scripts and examples provided only for PowerShell (.ps1) and instructions to use Windows-specific tools like winget. There are no Bash, Linux shell, or cross-platform script examples, and Linux/macOS users are not given equivalent onboarding instructions.
Recommendations
- Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the onboarding process on those platforms.
- Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
- Clearly state platform requirements at the top of the page if onboarding is only supported on Windows, or provide guidance for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, including any prerequisites or workarounds needed.
Create Pull Request
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 Profiler, SQL Server PowerShell) and highlights PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are mentioned, there are no explicit Linux/macOS-focused examples or tools, and Windows tools are listed without Linux alternatives or parity discussion.
Recommendations
- Add explicit mention of cross-platform tools (e.g., Azure Data Studio, sqlcmd) and their support for SQL Managed Instance enabled by Azure Arc.
- Provide examples or guidance for Linux/macOS users, such as using Azure CLI or VS Code extensions.
- Clarify which tools are Windows-only and which are cross-platform, ideally in a dedicated section.
- Include PowerShell alternatives for Linux/macOS (e.g., PowerShell Core, Bash scripting) if supported.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (removing headers) not explained for Linux. The Linux example is brief and lacks parity in guidance. Windows tools (certutil, findstr) are mentioned explicitly, while Linux alternatives for header removal are not provided. The rest of the guide uses cross-platform tools (openssl, Azure CLI, kubectl) and is generally platform-neutral.
Recommendations
- Expand the Linux example to include instructions for removing certificate headers (e.g., using grep or sed).
- Provide parity in explanation for Linux users, such as how to decode and clean base64 output.
- Mention macOS explicitly where applicable, as its base64 and openssl utilities are similar to Linux.
- Consider listing Linux/macOS instructions before Windows, or presenting them side-by-side for equal visibility.
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
Summary
The documentation is generally Linux-focused, but it uses Windows-specific PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, rather than native Linux shell commands. This creates friction for Linux users, as the recommended commands are not standard Linux tools and require a Windows environment or PowerShell Core.
Recommendations
- Provide native Linux shell (bash) equivalents for node configuration steps, especially for sysctl settings.
- Clarify whether Invoke-AksEdgeNodeCommand is available on Linux, or if it requires a Windows management host.
- If PowerShell is required, explicitly state this and offer guidance for Linux users (e.g., using PowerShell Core).
- Show both PowerShell and bash examples for cross-platform parity.
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 frequently presents Windows-centric examples and tools first (e.g., file paths like C:\Backupfiles\test.bak, Visual Studio Code, and SSMS), and does not provide equivalent Linux/macOS examples for key steps such as database backup and file copying. This can create friction for Linux/macOS users, especially in the backup and file transfer steps.
Recommendations
- Provide Linux/macOS equivalents for file paths in backup examples (e.g., /home/user/backup/test.bak).
- Include examples using cross-platform tools (e.g., Azure Data Studio instead of only Visual Studio Code and SSMS).
- Show how to perform the backup step using sqlcmd or Azure Data Studio on Linux/macOS.
- When demonstrating kubectl cp, show both Windows (C:\ paths) and Linux/macOS (/home/user/backup/test.bak) source file paths.
- Explicitly state that all steps can be performed from Linux/macOS, and clarify any Windows-only requirements.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting and HTTP/2 validation without equivalent Linux commands; Windows paths and error messages are referenced first; and some CLI instructions (e.g., Azure CLI installer/downgrade) are described in Windows-centric terms, with Linux alternatives mentioned only briefly or not at all. There are also missing Linux/macOS equivalents for some troubleshooting steps, such as SSH folder permissions and proxy configuration.
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP/2 troubleshooting, nslookup/dig for DNS validation).
- When referencing CLI installation/downgrade, include explicit instructions for Linux/macOS (e.g., package manager commands, pip alternatives).
- Ensure troubleshooting steps for SSH folder permissions and concurrent access include Linux/macOS guidance (e.g., file permissions, lsof/fuser for file locks).
- Mention Linux/macOS tools and patterns alongside Windows tools, not after or instead of them.
- Where error messages reference Windows paths, clarify Linux/macOS equivalents or note that errors may differ.
Azure Arc
Run command on Azure Arc-enabled servers (preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides extensive PowerShell examples and references to Windows-specific tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule), with Windows-focused REST API scenarios and script samples. Linux-specific examples are minimal or absent, and Windows terminology and tools are often mentioned first or exclusively, especially in REST API and PowerShell sections.
Recommendations
- Add Linux-focused examples for REST API usage, such as configuring firewall rules using Linux commands (e.g., ufw, iptables) and scripts (.sh).
- Provide parity in PowerShell and CLI examples by including both Windows (.ps1) and Linux (.sh) script samples and scenarios.
- When referencing tools for generating SAS tokens or managing blobs, mention cross-platform alternatives or CLI equivalents.
- Ensure that introductory and example sections explicitly show Linux use cases and commands, not just Windows.
- Balance the order of examples so Linux and Windows are equally represented, or clarify when an example is OS-specific.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first, especially in sections like agent upgrade and uninstall. Windows-specific tools (PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are described in detail, while Linux equivalents are referenced but not explained as thoroughly. The cleanup script for stale Arc resources is only provided in PowerShell, with no Linux/bash equivalent. Overall, Linux users can complete all tasks, but Windows-centric presentation and tooling may create friction.
Recommendations
- Alternate the order of Windows and Linux sections so Linux is not always after Windows.
- Provide bash or Azure CLI scripts for tasks like stale resource cleanup, not just PowerShell.
- Expand Linux-specific guidance for update automation (e.g., using cron, unattended-upgrades, or package manager hooks).
- Where Windows tools are described in detail (e.g., Group Policy, WSUS), offer equivalent Linux automation strategies or links.
- Ensure Linux examples are as detailed as Windows ones, especially for advanced scenarios.
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 use PowerShell syntax, which is native to Windows and less familiar to Linux/macOS users. While ARM template samples are provided for both Linux and Windows, the deployment workflow is Windows-centric. Additionally, PowerShell examples are presented before mentioning Azure CLI as an alternative in the 'Related content' section.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands for each extension.
- Explicitly state that Azure CLI can be used from Linux/macOS and provide sample CLI commands.
- Consider including Bash script examples for template deployment.
- Clarify that PowerShell Core is cross-platform, but provide CLI alternatives for Linux users.
- In the 'Deployment commands' section, show both PowerShell and CLI syntax for deploying ARM templates.
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
windows_first
missing_linux_example
Summary
The documentation provides recovery instructions and a script exclusively for Windows, using PowerShell. There are no Linux/macOS examples, nor is there mention of equivalent tools or scripts for non-Windows platforms. The section is titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered for Linux/macOS users.
Recommendations
- Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
- Mention if the recovery process is supported only on Windows, and clarify why (e.g., dependencies on Windows-only tools).
- If possible, offer a cross-platform script or containerized solution that can be run on any OS.
- Add a section explicitly addressing Linux/macOS users, even if only to state limitations or workarounds.
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 both Windows and Linux guidance, but exhibits Windows bias in several areas. The primary automation script is PowerShell-based, with instructions to run it in a PowerShell terminal and use Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents, and Linux automation (e.g., shell scripts, cron) is not covered. While Linux prerequisites are briefly mentioned, Linux/macOS users lack parity in automation examples and tooling.
Recommendations
- Provide a Bash/shell script version of the automation script for Linux/macOS users, or document how to run the PowerShell script cross-platform (e.g., with PowerShell Core).
- Include instructions for scheduling the automation script using cron on Linux, alongside Windows Task Scheduler examples.
- Offer Linux/macOS-specific guidance for running the script, including handling permissions and execution policies.
- Ensure that out-of-band methods (e.g., Ansible) are given equal prominence and detailed examples for Linux environments.
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 for disaster recovery operations of the Azure Arc resource bridge VM is heavily focused on PowerShell scripts and Windows tooling. All example scripts and commands are provided in PowerShell, with no mention of Bash, Linux shell equivalents, or cross-platform onboarding script usage. There is no guidance for Linux/macOS users on how to perform the same operations, and the onboarding script appears to be a PowerShell script (.ps1), which may not be natively usable on Linux/macOS without additional steps.
Recommendations
- Explicitly state whether the onboarding script is cross-platform or Windows-only. If it is cross-platform, provide Bash or shell examples for Linux/macOS users.
- If the onboarding script is Windows-only, provide guidance for Linux/macOS users, such as using PowerShell Core (pwsh) or alternative methods.
- Add notes or sections clarifying prerequisites for Linux/macOS users, including how to install PowerShell Core and run .ps1 scripts.
- Consider providing equivalent Bash scripts or instructions for Linux environments, or link to relevant cross-platform onboarding documentation.
- Ensure that any Azure CLI commands are shown with both Windows and Linux syntax where differences exist.
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 equivalents. All CLI examples are shown in PowerShell blocks, and the only provided automation scripts are PowerShell-based. There are no Linux/macOS-specific instructions or examples, and the documentation does not clarify cross-platform usage or provide Bash alternatives.
Recommendations
- Provide Azure CLI command examples in Bash syntax as well as PowerShell, using code blocks labeled for each platform.
- Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clarify if the PowerShell scripts are cross-platform (e.g., PowerShell Core/7).
- Explicitly state that Azure CLI commands can be run from Bash on Linux/macOS, and provide guidance for Linux/macOS users where relevant.
- Add notes or sections for Linux/macOS users, including any platform-specific considerations or requirements.
Azure Arc
Remove your VMware vCenter environment from Azure Arc
...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed instructions for running the deboarding script exclusively in Windows/PowerShell, with no equivalent Linux/macOS guidance. The script section is labeled 'Windows' and all examples are PowerShell-based, suggesting Windows as the primary platform. Linux agent removal instructions are present, but Linux/macOS users are left without guidance for running the deboarding script.
Recommendations
- Provide instructions for running the deboarding script on Linux/macOS, including any prerequisites (e.g., PowerShell Core, Azure CLI) and example commands.
- Clarify whether the script is Windows-only or cross-platform; if cross-platform, add Linux/macOS sections.
- If the script is Windows-only, offer alternative manual steps or a cross-platform script.
- Mention PowerShell Core compatibility if relevant, and provide installation links 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 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 or cross-platform scripting tools. The script appears to be Windows-centric, and Linux users are not given equivalent instructions or alternatives.
Recommendations
- Provide instructions for running the script on Linux/macOS, such as using PowerShell Core (pwsh) or converting the script to Bash if possible.
- Include example commands for Linux/macOS terminals, specifying how to execute the script with PowerShell Core.
- Clarify whether the script is compatible with PowerShell Core and, if not, consider providing a cross-platform version.
- Mention any prerequisites for Linux/macOS users, such as installing PowerShell Core or dependencies.
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_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, with no Bash or Linux shell equivalents. Paths in JSON templates use Windows-style (C:\, E:\) and PowerShell scripts (.ps1) are referenced throughout. There are no Linux/macOS-specific instructions or examples, and Windows conventions (file paths, script invocation) are used by default. This creates friction for Linux/macOS users, who must adapt the instructions and scripts themselves.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell examples, especially for az CLI commands.
- Use generic or cross-platform file paths in JSON templates (e.g., /home/user/schema.yaml) or note that paths should be adapted for the user's OS.
- Reference both .ps1 (PowerShell) and .sh (shell) scripts, or provide guidance for Linux/macOS users on adapting the scripts.
- Explicitly mention OS requirements or compatibility for scripts and tools.
- Add a section or callout for Linux/macOS users, highlighting any differences or required adaptations.
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, with no mention of Linux/macOS-compatible alternatives or instructions. The script is referenced as a .ps1 file, which is traditionally Windows-centric, and the example usage is in PowerShell. There are no Bash or cross-platform script examples, nor guidance for Linux/macOS users.
Recommendations
- Provide a Bash or cross-platform script for migration, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Add explicit instructions for running the migration script on Linux/macOS, including any prerequisites (such as installing PowerShell Core).
- Mention whether the migration process can be completed using Azure CLI or other tools available on Linux/macOS.
- If the script is Windows-only, state this clearly and provide alternative guidance for Linux/macOS users.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exhibits Windows bias primarily in the 'kubectl' installation instructions, where only the Windows 'winget' command is provided, with no Linux/macOS alternative. Additionally, the file extraction example under the Bash tab uses the Windows PowerShell 'Expand-Archive' command, which is not available on Linux/macOS Bash shells. Throughout, file paths and examples are Windows-centric (e.g., 'C:\path\to\archive.zip'), and Linux/macOS equivalents are missing. Bash and PowerShell tabs are provided for most Azure CLI commands, but the initial environment setup and tooling instructions favor Windows tools and patterns.
Recommendations
- Provide Linux/macOS installation instructions for 'kubectl' (e.g., 'curl' or 'apt/yum' commands).
- For file extraction, use cross-platform Bash commands such as 'unzip' or 'tar' for Linux/macOS, and clarify which commands are Windows-only.
- Include Linux/macOS file path examples alongside Windows paths.
- Ensure all critical steps have Linux/macOS equivalents, especially for initial setup and tooling.
- Where possible, reference platform-agnostic installation methods or link to official cross-platform guides.
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 towards PowerShell and Windows-style command syntax. Most examples, including Azure CLI, Docker, and Kubernetes commands, are provided in PowerShell format, with variable syntax and command structure specific to Windows/PowerShell. Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service group' section, which provides both Bash and PowerShell tabs. This creates friction for Linux/macOS users, who must translate PowerShell commands and variable usage to Bash manually.
Recommendations
- Provide Bash/Linux equivalents for all troubleshooting steps, especially for Azure CLI, Docker, and Kubernetes commands.
- Use cross-platform variable syntax (e.g., $VAR for PowerShell, $VAR or ${VAR} for Bash) and clarify differences.
- Clearly indicate when a command is Windows-specific and offer alternatives for Linux/macOS.
- Where possible, use platform-neutral Azure CLI syntax and avoid PowerShell-specific constructs.
- Add notes or tabs for Linux/macOS users, similar to the 'service group' section.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Windows and Linux examples for key tasks, but Windows/PowerShell examples are often presented first or with more detail. PowerShell commands are included alongside Azure CLI, and some instructions reference Windows-specific paths or tools (e.g., PowerShell, Windows Admin Center) before their Linux equivalents. However, Linux is supported throughout, and Linux-specific instructions (such as log file locations) are present. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Explicitly mention macOS support and provide macOS-specific instructions where relevant.
- Ensure parity in detail and clarity between Windows and Linux instructions (e.g., log file locations, script examples).
- Where possible, use cross-platform CLI examples as the default, and reference PowerShell only as an alternative.
- Clarify when a tool or path is Windows-only and provide the Linux/macOS equivalent immediately.
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 presents Windows and Linux VM extension tables separately, but the Windows extensions section appears first and is more extensive. The deployment methods (Azure portal, CLI, PowerShell, ARM templates) are listed without bias, and Linux-specific extensions and partner tools are well represented. There are no PowerShell-heavy examples or exclusive Windows tools mentioned. However, the ordering of Windows before Linux and the longer Windows extension table may subtly reinforce Windows as the primary platform.
Recommendations
- Consider presenting Windows and Linux extension tables side-by-side or in alphabetical order to avoid implicit prioritization.
- Ensure parity in extension descriptions and links for both platforms.
- If possible, balance the depth of information between Windows and Linux sections.
- Explicitly state that both Windows and Linux are equally supported at the start of the Extensions section.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed explanation and output imagery. The Linux/Bash example follows, but is slightly less detailed. References to Windows tools (PowerShell) appear before Linux equivalents (Bash, SSH), and related content links mention PowerShell before Azure CLI.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to emphasize parity.
- Provide equally detailed explanations and output imagery for both Windows and Linux examples.
- In related content, list Azure CLI and Bash examples before or alongside PowerShell.
- Ensure that prerequisite instructions for Linux are as clear and prominent as those for Windows.
- Explicitly state that both Windows and Linux are fully supported and provide links to Linux-specific tutorials where relevant.
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, ensuring parity for both platforms. However, Windows instructions and notes are presented before Linux instructions in the 'Run the script' and 'Retry command' sections, which is a minor form of bias ('windows_first'). No critical functionality is missing for Linux users, and all necessary steps are covered for both OSes.
Recommendations
- Present Windows and Linux instructions in parallel (side-by-side) or alternate the order in sections to avoid always showing Windows first.
- Add explicit mention that macOS users can follow the Linux (Bash) instructions if applicable.
- Ensure screenshots and UI references are OS-neutral or clarify if any steps differ for Linux/macOS 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 immediately after Bash, and in some sections, the PowerShell tab is labeled as a peer to Bash rather than as a Windows-specific alternative. There are no Windows-only tools or patterns, and all instructions are based on the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, but the ordering of PowerShell examples may subtly prioritize Windows users.
Recommendations
- Clarify that Bash examples are for Linux/macOS and PowerShell for Windows, possibly by labeling the tabs as 'Linux/macOS (Bash)' and 'Windows (PowerShell)'.
- Ensure Bash examples are shown first in all sections to reinforce Linux/macOS parity.
- Consider adding a brief note at the start indicating that all CLI commands are cross-platform and can be run on any OS with Azure CLI installed.
- If applicable, mention that PowerShell Core is available on Linux/macOS, but Bash is the default shell for those platforms.
Azure Arc
Service Groups for Workload Orchestration
...cles/azure-arc/workload-orchestration/service-group.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all command-line operations, ensuring parity for Linux/macOS and Windows users. However, in each section, PowerShell examples are consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools, patterns, or exclusive Windows instructions are present; all commands use the cross-platform Azure CLI. There are no missing Linux examples or Windows-only tools.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell examples are provided for cross-platform compatibility.
- Ensure that any troubleshooting or advanced sections also include Bash and PowerShell parity if command-line instructions are needed.
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 most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. No evidence of Windows-only tools, Windows-specific patterns, or missing Linux examples is found. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
- No changes needed for Linux parity. The documentation already provides full Bash examples and uses cross-platform tools.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to avoid perceived bias toward either platform.
- Explicitly mention that all examples are cross-platform and that Azure CLI and Helm are available on both Windows and Linux/macOS.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation generally uses cross-platform tools (Helm CLI, Azure CLI), but there are subtle Windows biases. The environment variable setup uses the Windows-style 'set' command without showing the Linux/macOS equivalent. In the prerequisites, Azure PowerShell is mentioned before the Azure CLI and portal for AKS creation. No explicit Linux/macOS shell example is given for environment variable setup, and the order of some examples and tool mentions slightly favors Windows.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands for setting environment variables.
- When listing ways to create AKS clusters, mention Azure CLI and portal before Azure PowerShell, or clarify all are supported.
- Add explicit notes or examples for Linux/macOS users where commands differ (e.g., environment variables, file operations).
- Review the order of tool mentions to ensure cross-platform parity.
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 marks these blocks as 'powershell', which may imply Windows-centric usage. There are no explicit Linux/macOS shell examples, and PowerShell is used as the default for command blocks, even though the commands themselves are cross-platform. The documentation does not mention Linux tools or shell patterns, nor does it clarify that the examples work equally well on Linux/macOS.
Recommendations
- Provide explicit Linux/macOS shell examples (e.g., bash) alongside PowerShell examples.
- Clarify that the kubectl and sqlcmd commands are cross-platform and can be run from any OS with the appropriate tools installed.
- Avoid labeling command blocks as 'powershell' when the commands are not PowerShell-specific.
- Mention prerequisites for Linux/macOS users, such as installing mssql-tools and kubectl.
- Consider showing bash syntax first or equally with PowerShell to avoid Windows-first bias.
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 and a Linux-compatible example is provided, SSMS is listed before sqlcmd, and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The overall guidance and examples are slightly Windows-centric, but Linux users can complete the task using sqlcmd.
Recommendations
- Mention cross-platform SQL client tools (e.g., Azure Data Studio, DBeaver, Squirrel SQL) alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using GUI tools, not just sqlcmd.
- Ensure that Linux/macOS instructions and examples are presented with equal prominence to Windows/SSMS examples.
- Clarify that sqlcmd works on both Windows and Linux, and provide installation links for both platforms.
Low 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 there are subtle Windows biases: Windows installation links are listed first for kubectl and curl, and there is a specific note about using cmd.exe instead of PowerShell for curl on Windows 10, without equivalent Linux/macOS guidance. The curl installation for Linux is less explicit (just 'install curl package'), lacking a direct link or command example. There is also a PowerShell-specific note about curl aliases, but no comparable Linux/macOS shell notes.
Recommendations
- List installation links for all platforms in parallel or alphabetical order to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl', 'brew install curl') with direct links.
- Include shell-specific notes for Linux/macOS where relevant (e.g., bash/zsh nuances for curl or kubectl).
- Balance platform-specific notes: if mentioning PowerShell quirks, also mention any relevant Linux/macOS shell quirks.
- Consider providing example commands for checking tool versions on all platforms, not just Windows.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but PowerShell examples are consistently presented alongside CLI and sometimes before Linux-native approaches. There are no Linux-specific command-line examples (e.g., Bash scripts), and the use of PowerShell is emphasized, which may create friction for Linux/macOS users who typically use Bash and Azure CLI. However, Azure CLI examples are present and fully functional for Linux/macOS users, and environment variable instructions use Bash syntax where appropriate.
Recommendations
- Ensure Azure CLI examples are always presented first, as CLI is cross-platform and native to Linux/macOS.
- Add explicit Bash script examples for common tasks, especially for onboarding and updating clusters.
- Clarify that Azure PowerShell is available cross-platform, but recommend Azure CLI for Linux/macOS users.
- Consider including a 'Linux/macOS' tab or section for any steps where environment setup differs.
- Review and minimize PowerShell-centric language unless the task is Windows-specific.
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 shows mild Windows bias. Windows-specific services (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are referenced, and Windows NTP is mentioned as the default for Hyper-V. Windows-related endpoints appear before Linux equivalents in some cases. However, Linux endpoints and requirements (e.g., packages.microsoft.com for Linux package downloads, SSH port 22, log collection for Linux components) are also included, and the documentation is generally cross-platform.
Recommendations
- Clarify when Windows-specific endpoints (e.g., time.windows.com) are only needed for Windows-based deployments, and provide Linux alternatives (e.g., ntp.ubuntu.com or pool.ntp.org) where relevant.
- Explicitly state whether management machines and appliance VMs can be Linux-based, and if so, highlight any Linux-specific requirements or differences.
- Where Windows and Linux endpoints/tools are both relevant, list them together or in parallel, rather than Windows-first.
- Add example configurations for both Windows and Linux environments, especially for network and firewall settings.
- Ensure notes specify when a requirement is OS-specific (e.g., 'Windows NTP' vs. 'Linux NTP').
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, with parity in most features and fixes. However, Windows download links are consistently listed before Linux, and Windows-specific tools (e.g., PowerShell, msiexec, GUI installer) are referenced in troubleshooting and known issues sections. Some improvements and bug fixes are described with Windows tools or patterns, while Linux equivalents are not always mentioned or explained in the same detail.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid implicit prioritization.
- When referencing Windows-specific tools (e.g., PowerShell, msiexec), provide Linux equivalents (e.g., shell commands, package managers) where relevant.
- Expand troubleshooting and known issues to include Linux-specific guidance, not just Windows installer scenarios.
- Ensure that improvements or bug fixes described for Windows (such as installer logic or GUI changes) are matched with Linux details if applicable, or explicitly state if not relevant.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides authentication options and examples for both Windows and Linux, but there is a mild Windows bias: Windows-specific login methods and certificate store options are described first and in more detail, and Windows tools (like PowerShell's Get-AzAccessToken) are referenced without Linux equivalents. However, Linux authentication flows are covered and most examples are OS-agnostic.
Recommendations
- Present authentication options in a neutral order (not Windows-first), or clarify that device code login is default for Linux.
- When referencing Windows-specific tools (e.g., PowerShell's Get-AzAccessToken), also mention Linux/macOS alternatives (such as using Azure CLI to obtain access tokens).
- Add explicit Linux/macOS examples where Windows-specific flows are described (e.g., certificate handling, access token acquisition).
- Clarify which authentication methods and flags are supported on Linux/macOS, and provide guidance for those platforms.
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
missing_linux_example
Summary
The documentation page for Azure Arc resource bridge system requirements exhibits mild Windows bias. Azure CLI installation links and requirements are presented with a Windows-centric focus (e.g., linking to Azure CLI Windows install docs, specifying x64/32-bit requirements without clarifying Linux/macOS equivalents). There are no explicit Linux/macOS examples or guidance for management machine setup, and no mention of Linux/macOS compatibility for CLI commands or file locations.
Recommendations
- Add explicit guidance for installing Azure CLI on Linux and macOS, including relevant links.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific requirements.
- Mention file location defaults for CLI-generated files on Linux/macOS (e.g., home directory, permissions).
- Include examples or notes for running az arcappliance commands on Linux/macOS.
- Ensure that references to Azure CLI bitness (x64/32-bit) are explained for Linux/macOS users (e.g., most Linux distributions are x64; clarify if 32-bit is relevant).
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 parity for both Linux and Windows in most sections, including installation URLs and agent configuration. However, there is a mild bias in the ordering of examples and references: Windows installation packages and tools (such as Windows Admin Center) are mentioned first or exclusively in some places, and Windows-specific cipher suite configuration is detailed before Linux/OpenSSL. Windows Admin Center is referenced as a service tag and endpoint, but SSH (the Linux equivalent) is only briefly mentioned. The cryptographic protocol section provides more detail for Windows than Linux.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than consistently listing Windows first.
- Expand Linux-specific guidance for TLS/cipher suite configuration, including links to OpenSSL configuration best practices.
- When referencing Windows Admin Center, also highlight SSH as the Linux management equivalent, and provide links to relevant SSH documentation.
- Ensure that troubleshooting and configuration sections provide equal detail for Linux and Windows, especially for security and networking topics.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Windows and Linux Azure Arc-enabled servers and provides parity in feature descriptions. However, there is a mild bias in example ordering: Azure PowerShell examples are presented after Azure CLI, and PowerShell is mentioned as a management option alongside CLI and portal. Azure CLI is correctly described as cross-platform, but PowerShell is presented without explicit mention of its cross-platform support (though Az.ConnectedMachine is available on Linux PowerShell Core). There are no Windows-only tools or missing Linux examples, but PowerShell is more prominent than, for example, bash scripting or Linux-native tools.
Recommendations
- Explicitly state that Azure PowerShell (Az.ConnectedMachine module) is available on Linux and macOS via PowerShell Core, not just Windows.
- Consider providing bash or shell script examples for common operations, especially for Linux users.
- Ensure that CLI examples are shown first and that PowerShell is clearly marked as optional for cross-platform use.
- Add a note clarifying that all management operations can be performed equally from Linux, macOS, or Windows environments.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but Windows examples and references (such as PowerShell syntax and Windows paths) are often presented first, and Windows-specific details (e.g., PowerShell version requirements, Windows log file paths) are more prominent. Linux examples are included and reasonably detailed, but Windows tools and patterns (e.g., PowerShell, Windows environment variables, Windows log paths) are mentioned before or more extensively than their Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in some sections to avoid implicit prioritization.
- Where Windows-specific tools (e.g., PowerShell) are referenced, ensure equivalent Linux commands (e.g., Bash) are given equal prominence and explanation.
- Clarify when remediation steps differ between Windows and Linux, and provide explicit Linux instructions (e.g., for log file locations, service management, permissions).
- Where file paths or environment variables are mentioned, always include both Windows and Linux equivalents together.
- Consider adding a summary table or section that highlights parity and differences between Windows and Linux troubleshooting steps.
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. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Maintain the current structure, as Bash and PowerShell examples are both present.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
- If possible, add a note clarifying that az CLI and Helm are cross-platform tools.
- Ensure that any future updates continue to provide both Bash and PowerShell examples.
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 provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are several instances where Windows-specific tools (such as PowerShell) and Windows-focused features are mentioned first or exclusively. Examples include references to PowerShell runbooks, Windows registry, and Windows Server management. Although Linux is mentioned in some scenarios (e.g., Azure Update Manager supports Windows and Linux, VM extensions for Windows or Linux), Windows examples and tools tend to be listed before Linux equivalents, and PowerShell is highlighted as a primary automation tool.
Recommendations
- Ensure that Linux examples and tools (such as Bash, shell scripts, and Linux-specific automation) are mentioned alongside PowerShell and Windows tools.
- When listing supported operating systems or tools, alternate the order or explicitly state parity between Windows and Linux.
- Provide links to Linux-specific documentation or examples for automation, monitoring, and configuration tasks.
- Highlight cross-platform SDKs and CLI usage equally, and avoid implying PowerShell is the default for automation.
- Add explicit examples or guidance for Linux VM management where only Windows is referenced.
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. While most features are platform-neutral or mention both Windows and Linux, there are instances where Windows-specific features (e.g., customizing guest OS settings for Windows VMs, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are highlighted. In the June 2024 section, Azure PowerShell is listed after Azure CLI and REST APIs, but no Linux-specific shell or tool is mentioned. The October 2024 section lists Windows-centric tools (System Center Configuration Manager, Group Policy) before Linux-centric tools (Ansible). Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks, but Windows tools and features are sometimes mentioned first or more prominently.
Recommendations
- Ensure Linux-centric tools (e.g., Ansible, Bash scripts) are mentioned alongside or before Windows-centric tools when listing automation options.
- Where possible, provide parity in examples for both Windows and Linux (e.g., PowerShell and Bash/CLI examples).
- Clarify when features are Windows-only to avoid confusion.
- Consider adding references to Linux guest customization and management features if available.
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 each command, ensuring parity for Linux/macOS and Windows users. However, in most sections, PowerShell examples are presented immediately after Bash, and the Bash examples are labeled first. There is no evidence of Windows-specific tools, patterns, or exclusive Windows instructions. The Azure CLI is used throughout, which is cross-platform.
Recommendations
- Maintain the current structure of providing both Bash and PowerShell examples.
- Consider clarifying that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- If possible, add a brief note for users on macOS/Linux that Bash examples are directly usable in their environments.
- Ensure that any referenced scripts (such as the 'Clean-up script') are available in both Bash and PowerShell versions, or clarify their platform compatibility.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. No Windows-specific tools, patterns, or terminology are used exclusively or prioritized. All instructions are cross-platform and rely on the Azure CLI, which is available on both Windows and Linux/macOS.
Recommendations
- Maintain the current structure of providing both Bash and PowerShell examples.
- Consider clarifying that all CLI commands are cross-platform and that Azure CLI is supported on Windows, Linux, and macOS.
- If desired, alternate the order of Bash and PowerShell examples in future documentation to further reduce perceived bias.
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 release notes for Workload Orchestration in Azure Arc predominantly use PowerShell syntax for CLI examples in the May 2025 release, despite the Azure CLI being cross-platform. Bash examples are used elsewhere, but PowerShell appears first and is the only shell shown for configuration file operations. There are no explicit Linux/macOS-specific examples or references, and no mention of Linux tools or patterns. However, the core features and CLI commands are cross-platform, and the documentation does not reference Windows-only tools or concepts outside of PowerShell syntax.
Recommendations
- Provide Bash equivalents for all PowerShell CLI examples, especially for configuration file operations.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and indicate shell-agnostic usage where possible.
- When showing CLI examples, alternate between Bash and PowerShell or show both.
- Explicitly mention Linux/macOS compatibility for CLI features and extensions.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Maintain the current structure, as Bash and PowerShell examples are both provided.
- Consider clarifying in the introduction that both Linux/macOS and Windows are fully supported.
- Optionally, alternate the order of Bash and PowerShell tabs in future documentation to avoid implicit prioritization.
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 present and detailed, but there is no Linux/macOS-specific guidance or explicit mention that PowerShell Core is cross-platform. The CLI examples are generic and suitable for all platforms, but the PowerShell section may give the impression of Windows preference, especially since there is no Bash or shell scripting example. The order of sections (CLI before PowerShell) is appropriate, but the presence of a detailed PowerShell section without a corresponding Bash/shell script example may be seen as a minor bias.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Explicitly mention that Azure PowerShell is available on all platforms via PowerShell Core, or clarify if the examples require Windows PowerShell.
- Optionally, add a Bash or shell script example for deploying dashboards using the Azure CLI to demonstrate Linux parity.
- Consider adding a note for Linux/macOS users about prerequisites for using Azure CLI and PowerShell.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is a slight 'windows_first' bias in mentioning Azure PowerShell as a primary tool alongside CLI, which may be unnecessary since PowerShell is predominantly used on Windows. No Linux-specific tools or shell examples (e.g., Bash, shell scripting) are provided, and the CLI example is generic but not explicitly Linux/macOS-focused. However, the Azure CLI is cross-platform, and the documentation does not prevent Linux/macOS users from completing the tasks.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding a Bash shell example or explicitly stating that the CLI example works on Linux/macOS.
- Mention that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Add a note about Azure Cloud Shell being accessible from any OS/browser.
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 cross-platform parity. 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, but PowerShell is given equal prominence. There are no Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Ensure that file path examples in PowerShell use forward slashes or note that backslashes are Windows-specific.
- Clarify that PowerShell examples are for Windows users, and Bash for Linux/macOS, to help users choose the right tab.
- Consider adding a note about cross-platform compatibility of Azure CLI and Helm.
- If possible, provide a brief summary or table at the top indicating which shell to use for each OS.
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 capability of Azure Copilot in the mobile app. While 'CLI' can refer to cross-platform tools (such as Azure CLI), 'PowerShell' is listed alongside it, and PowerShell is often associated with Windows, though it is now cross-platform. However, there are no explicit Linux/macOS-only examples, nor are Windows-specific tools or patterns prioritized elsewhere. No examples are given for either platform, and the documentation does not exclusively mention Windows tools.
Recommendations
- Clarify that Azure CLI and PowerShell are both cross-platform, and provide examples for both where appropriate.
- Explicitly mention Bash or shell scripting as an option for Linux/macOS users, if supported by Azure Copilot.
- If code snippet generation includes platform-specific scripts, provide examples for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
- Ensure that any references to PowerShell are accompanied by notes about its cross-platform support.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
minor_windows_tools
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured prominently and often alongside CLI. In several sections, PowerShell examples are given equal weight to CLI, which is cross-platform, but PowerShell is still more associated with Windows. The 'Next steps' section lists Azure CLI first, then PowerShell. There are no Linux/macOS-specific examples or explicit mention of shell environments (bash/zsh), but Docker and Azure CLI are cross-platform tools. There is a minor bias in the frequent mention of PowerShell and lack of explicit Linux/macOS shell examples.
Recommendations
- Add explicit bash/zsh shell examples for Linux/macOS users, especially for authentication flows and scripting.
- Clarify that Azure PowerShell is available cross-platform, but provide guidance for Linux/macOS users (e.g., installation links, shell usage).
- Where PowerShell is mentioned, also show equivalent bash commands or note that Azure CLI works identically across platforms.
- Consider including a section or tip for Linux/macOS users about using Azure CLI and Docker in their environments.
- Ensure parity in example ordering (e.g., alternate CLI and PowerShell, or group by platform).
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but consistently presents PowerShell as a first-class option alongside CLI. PowerShell is primarily a Windows tool, and its inclusion may signal a Windows-centric approach. However, Azure CLI is cross-platform and all CLI examples are present, so Linux/macOS users are not blocked. There are no Windows-only tools or patterns, and no missing Linux examples. The only minor bias is that PowerShell is featured equally with CLI, which may create slight friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider mentioning that PowerShell Core is available on Linux/macOS, but Azure CLI is generally more common in those environments.
- If analytics show most users are on Linux/macOS, consider presenting Azure CLI examples first.
- Add a brief note about the cross-platform nature of Azure CLI and PowerShell Core to reduce perceived Windows bias.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key tasks such as viewing usage and changing registry SKU. However, PowerShell examples are given alongside CLI examples, and PowerShell is mentioned explicitly in the 'Show registry usage' and 'Change registry SKU' sections. Azure CLI is cross-platform, but PowerShell is primarily associated with Windows, although it is available on Linux/macOS. There are no Linux-specific examples (e.g., Bash scripting), and CLI examples are not clearly prioritized over PowerShell. The order of listing tools sometimes puts PowerShell before REST API, and both CLI and PowerShell are mentioned together without clear Linux parity.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide Bash shell scripting examples for common tasks (e.g., changing SKU, checking usage).
- When listing tools, mention Azure CLI first, followed by PowerShell, and note PowerShell's cross-platform availability.
- Add a note clarifying that PowerShell examples work on Linux/macOS with PowerShell Core, but CLI is more common for Linux users.
- Consider including sample commands for Podman or Docker CLI where relevant, as these are popular on Linux.