145
Pages Scanned
38
Pages Flagged
145
Changed Pages
26.2%
% Pages Flagged
Scan Information
Started At: 2026-02-08 00:00:07
Finished At: 2026-02-10 18:44:36
Status: completed
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 145
Files Completed: 145
Problematic Pages
40 issues found
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. While ARM templates for both Linux and Windows are included, the deployment workflow is PowerShell-centric, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Additionally, PowerShell examples are presented first and referenced throughout, reinforcing a Windows-first approach.
Recommendations
- Add equivalent Azure CLI deployment examples alongside PowerShell, especially for template deployment (e.g., az deployment group create ...).
- Explicitly mention that PowerShell commands can be run cross-platform, but highlight Azure CLI as a native option for Linux/macOS users.
- Consider providing Bash script samples for Linux users where relevant.
- Clarify in the prerequisites or introduction that both PowerShell and CLI are supported, and link to cross-platform installation guides.
Create Pull Request
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-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, and does not provide native Linux shell examples for sysctl configuration. The text editor suggestion ('Notepad') is also Windows-oriented, and there is a lack of parity for Linux command-line workflows.
Recommendations
- Provide native Linux shell commands for sysctl configuration (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee ...').
- Replace or supplement 'Invoke-AksEdgeNodeCommand' examples with direct Linux shell commands for local execution.
- Suggest Linux-native text editors (e.g., nano, vim) instead of Notepad.
- Clarify when Windows tools are required and offer Linux alternatives wherever possible.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides several command examples using PowerShell syntax (e.g., 'kubectl exec ...' with PowerShell prompt and formatting), and the SQL connectivity example is shown only with PowerShell. There are no explicit Linux/macOS shell (bash) examples, and PowerShell is used as the default shell for command snippets, which may create friction for Linux/macOS users.
Recommendations
- Add equivalent bash/Linux/macOS shell examples for all kubectl and sqlcmd commands.
- Use a neutral shell prompt (e.g., '$') or clarify that commands work in both PowerShell and bash.
- Mention that sqlcmd and kubectl commands are cross-platform and provide guidance for Linux/macOS users where relevant.
- Avoid using PowerShell-specific formatting unless the command is Windows-only.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., C:\Backupfiles\test.bak), referencing Windows tools (SQL Server Management Studio, Notepad/OneNote), and omitting explicit Linux/macOS equivalents for backup/restore commands and file paths. Linux/macOS users may need to adapt instructions and paths, but the overall process is not Windows-exclusive.
Recommendations
- Provide Linux/macOS file path examples alongside Windows paths in backup/restore commands (e.g., /home/user/Backupfiles/test.bak).
- Mention cross-platform alternatives to Windows-specific tools (e.g., Azure Data Studio instead of SSMS, or generic text editors instead of Notepad/OneNote).
- Clarify that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
- Add explicit notes or examples for Linux/macOS users where commands or paths differ.
- Where possible, show both Windows and Linux/macOS command syntax for kubectl cp and other shell commands.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation lists 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 extension are mentioned, Windows tools are referenced more frequently and appear before Linux alternatives. There are no Linux-specific management tools or examples provided, and PowerShell scripting is emphasized without mention of Bash or cross-platform scripting options.
Recommendations
- Add examples or references for Linux/macOS management tools, such as sqlcmd or Azure Data Studio.
- Mention Bash scripting support or cross-platform scripting approaches alongside PowerShell.
- Clarify which tools are cross-platform and which are Windows-only, especially for SSMS and SQL Server PowerShell.
- Consider listing Azure CLI and Visual Studio Code extension before Windows-only tools to reduce Windows-first bias.
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 for both Windows and Linux, but several sections show Windows bias. The 'Interactive browser login' is described as Windows-only and appears first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references the Windows PowerShell cmdlet 'Get-AzAccessToken' without Linux alternatives. Overall, Linux is supported, but Windows-specific tools and patterns are mentioned first or exclusively.
Recommendations
- Present Linux authentication options (device code, Azure CLI) before or alongside Windows options to avoid 'windows_first' bias.
- For certificate-based authentication, clarify Linux usage (e.g., storing certificates in files, recommended locations, permissions) and provide explicit Linux guidance.
- For access token acquisition, mention cross-platform methods (e.g., Azure CLI 'az account get-access-token') alongside PowerShell examples.
- Where Windows tools (like certificate stores or PowerShell cmdlets) are referenced, provide Linux/macOS equivalents or clarify if they are not available.
- Ensure examples and sample commands are shown for both Windows and Linux environments, including shell syntax where relevant.
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 feature. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting (e.g., Invoke-WebRequest, Resolve-DnsName), Windows paths are referenced in error messages, and Windows tools (RDP, remote PowerShell) are mentioned. Linux equivalents (e.g., curl, dig, ssh) are not provided alongside these examples. In some cases, Windows-specific troubleshooting steps are given first or exclusively, creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS equivalents for PowerShell commands (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
- Include troubleshooting steps for Linux management machines, such as using SSH or terminal commands instead of RDP.
- When referencing file paths or error messages, clarify if they are OS-specific and provide Linux/macOS versions where applicable.
- Ensure CLI examples and troubleshooting steps are presented for both Windows and Linux environments, or note any OS-specific requirements.
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_tools
powershell_heavy
windows_first
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there is a notable Windows bias in several areas: Windows tools (Control Panel, Group Policy, Microsoft Update, WSUS, Configuration Manager) are described in detail, with lengthy step-by-step instructions, while Linux equivalents (package managers) are covered more briefly. PowerShell is heavily used for scripting and automation examples, especially for cleanup tasks, with no equivalent Bash or Linux scripting examples. Windows sections often appear first or are more detailed, and some advanced automation (e.g., stale resource cleanup) is only shown for Windows/PowerShell.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, especially for automation tasks such as stale resource cleanup.
- Expand Linux sections to include more detailed guidance, such as using cron jobs for automatic upgrades or removal, and managing package repositories.
- When describing upgrade/uninstall/configuration steps, ensure parity in detail and troubleshooting tips for Linux distributions.
- Consider presenting Windows and Linux sections in parallel or with equal prominence, rather than Windows-first.
- For proxy configuration, include troubleshooting and service restart instructions for Linux, similar to Windows.
- Where PowerShell scripts are provided, offer a Bash equivalent or note limitations for Linux 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 script (RGCleanScript.ps1) for resource clean-up, with only PowerShell usage examples and instructions. There are no Bash, shell, or Linux/macOS-compatible script options or examples. The documentation assumes the user is running PowerShell, which is traditionally a Windows tool, and does not mention cross-platform alternatives or compatibility.
Recommendations
- Provide a Bash or shell script equivalent for Linux/macOS users, or clarify if the PowerShell script is cross-platform and can be run using PowerShell Core (pwsh) on Linux/macOS.
- Add usage examples for Linux/macOS environments, including how to execute the script with PowerShell Core.
- Mention any prerequisites or installation steps for PowerShell Core on Linux/macOS if the script is compatible.
- If the script is Windows-only, explicitly state this limitation and suggest manual clean-up steps or alternative methods for Linux/macOS users.
Azure Arc
Bulk Review, Publish, and Deploy with Workload Orchestration
...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples, and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell scripts for Linux/macOS users. There are no explicit Linux/macOS CLI examples or instructions, and PowerShell is presented as the default scripting environment, which may create friction for non-Windows users.
Recommendations
- Provide CLI command examples in Bash syntax alongside PowerShell, especially for az CLI commands, which are cross-platform.
- Offer equivalent Bash shell scripts for bulk_deployment.ps1 and workflow-delete.ps1, or clarify if the scripts are compatible with PowerShell Core on Linux/macOS.
- Explicitly mention cross-platform compatibility of the az CLI commands and scripts, and note any Windows-specific requirements.
- Add a section or note for Linux/macOS users describing how to run the scripts or adapt the workflow.
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation shows evidence of Windows bias, particularly in the file extraction step, where only Windows tools (Expand-Archive via Bash/PowerShell and winget for kubectl) are provided, with no Linux/macOS equivalents. The rest of the guide is generally cross-platform, using Azure CLI and kubectl, but the initial setup steps assume a Windows environment or require Windows-specific tools, which may cause friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS alternatives for file extraction (e.g., 'unzip' or 'tar' commands) in the relevant sections.
- For kubectl installation, include platform-appropriate commands (e.g., 'curl' or package manager instructions for Linux/macOS) instead of only 'winget'.
- When showing Bash examples, ensure the commands are not Windows-specific (e.g., avoid using Expand-Archive in Bash tabs; use platform-appropriate tools).
- Clearly indicate which commands are Windows-only and provide parity for other platforms.
- Consider adding a platform selection tab (Windows, Linux, macOS) for all setup steps that differ by OS.
Azure Arc
Onboarding Scripts for Workload Orchestration
...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page is heavily biased toward Windows environments. All onboarding scripts are provided as PowerShell (.ps1) scripts, and users are instructed to use PowerShell terminals. The prerequisite steps recommend using 'winget', a Windows-only package manager, to install Azure CLI and kubectl. No Linux/macOS equivalents or instructions are provided, and there are no Bash or shell script examples. This creates friction for Linux/macOS users who wish to onboard workload orchestration resources in Azure Arc.
Recommendations
- Provide Bash or shell script equivalents for onboarding tasks, or clarify if the scripts are cross-platform.
- Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or manual download).
- Mention that PowerShell Core is available on Linux/macOS, and clarify if the .ps1 scripts are compatible with PowerShell Core.
- Add explicit guidance for Linux/macOS users, including terminal commands and environment setup steps.
- Consider providing Docker-based or cross-platform onboarding options if possible.
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 almost all CLI/script examples using PowerShell syntax, including backticks for line continuation and Windows-style file paths (e.g., C:\Users\...). There are no Bash or Linux/macOS shell equivalents, and the JSON template contains Windows file paths. The onboarding scripts are referenced as PowerShell (.ps1) only, with no mention of Bash or cross-platform alternatives. This creates friction for Linux/macOS users, who must adapt the examples and scripts themselves.
Recommendations
- Provide Bash/zsh shell equivalents for all PowerShell CLI examples, using standard Linux/macOS syntax (e.g., line continuation with \ or newlines).
- Use cross-platform file paths in JSON templates (e.g., /home/user/...), or note that paths should be adapted for the user's OS.
- Clarify whether onboarding scripts (.ps1) are supported on Linux/macOS (via PowerShell Core), and provide Bash versions if possible.
- Add explicit notes or sections for Linux/macOS users, highlighting any OS-specific requirements or adaptations.
- Where possible, show az CLI commands in a cross-platform way, avoiding PowerShell-specific syntax.
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 migration script and example, with no mention of a Bash, shell, or cross-platform equivalent. The script is named with a .ps1 extension and instructions are given for running it in PowerShell, which is typically associated with Windows environments. There is no guidance for Linux/macOS users, nor any indication if the script can be run with PowerShell Core on non-Windows platforms.
Recommendations
- Clarify whether the PowerShell script is compatible with PowerShell Core on Linux/macOS.
- Provide explicit instructions for running the migration script on Linux/macOS, including installation steps for PowerShell if required.
- If possible, offer a Bash or cross-platform script alternative, or note if only PowerShell is supported.
- Mention any prerequisites or limitations for non-Windows users.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward PowerShell and Windows-style command usage. Most examples, including Azure CLI, kubectl, and Docker commands, are presented in PowerShell syntax, with no equivalent Bash or Linux shell examples for critical troubleshooting steps. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but the rest of the document lacks Linux parity. This creates friction for Linux/macOS users, who must adapt Windows-centric instructions to their environments.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, kubectl, and Docker commands.
- Clearly indicate when a command is cross-platform and provide syntax for both Windows (PowerShell) and Linux/macOS (Bash).
- Avoid using PowerShell-specific constructs (e.g., ConvertTo-Json, Out-File, Base64 encoding via [Convert]) without showing Bash alternatives.
- Review file encoding instructions to ensure they are relevant for Linux/macOS users (e.g., UTF-8 with BOM is a Windows-specific concern).
- Add notes or tabs for Linux/macOS users where file paths, environment variables, or command syntax differ.
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 to CLI, which is less relevant for Linux/macOS users. In several sections, PowerShell is presented as a primary option alongside CLI, and there are no explicit Linux/macOS-specific examples or notes. The use of PowerShell commands and terminology may create friction for non-Windows users. Additionally, while the CLI is cross-platform, the documentation does not clarify this, nor does it provide shell-specific guidance (e.g., bash, zsh) or address Linux/macOS credential storage nuances.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- De-emphasize PowerShell by presenting CLI examples first and PowerShell as an alternative, or move PowerShell examples to a separate tab or section labeled 'Windows/PowerShell'.
- Add explicit Linux/macOS shell examples (e.g., bash, zsh) for environment variable usage and credential management.
- Include notes or tips about credential storage locations and behaviors on Linux/macOS (e.g., where docker config files are stored).
- Where relevant, mention that PowerShell Core is available cross-platform, but clarify that most Linux/macOS users will use bash/zsh with Azure CLI.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but there is a notable emphasis on PowerShell, which is primarily a Windows-centric tool. Azure CLI is cross-platform, but PowerShell examples are given equal prominence, and in some cases, PowerShell-specific instructions (such as module installation) are mentioned. There are no Linux/macOS-specific examples or notes about using Azure CLI on those platforms, and PowerShell is presented as a primary alternative, which may create friction for Linux/macOS users.
Recommendations
- Clearly indicate that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add brief notes or links about running Azure CLI on Linux/macOS, including installation instructions.
- Consider demoting PowerShell examples to a secondary position or clarifying their relevance for Windows users.
- Add troubleshooting tips relevant to Linux/macOS environments (e.g., shell differences, authentication issues).
- Explicitly state that all Azure CLI commands work on Linux/macOS unless otherwise noted.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, with dedicated tables for each OS and clear links to Linux-specific resources. However, Windows extensions are listed first, which may subtly prioritize Windows in the reader's perception. All deployment methods (CLI, PowerShell, Portal, ARM templates) are mentioned equally, and Linux examples are present throughout. No critical functionality is Windows-only, and Linux users can complete all tasks described.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or combining them into a single table with OS columns to emphasize equal support.
- Explicitly state at the beginning that all features and deployment methods are available for both Windows and Linux, to reinforce parity.
- Where possible, provide example links or references for both Windows and Linux in deployment instructions (e.g., CLI, PowerShell, Portal, ARM templates).
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. However, Linux parity is maintained with Bash examples and explicit Linux instructions. Both platforms are covered, but Windows is prioritized in ordering and example prominence.
Recommendations
- Present Windows and Linux examples side-by-side, or alternate which platform is shown first.
- Explicitly state that both Windows and Linux are supported at the start of example sections.
- Where possible, provide cross-platform scripting options (e.g., Azure CLI) in addition to PowerShell and Bash.
- Ensure screenshots and output examples for both platforms are equally visible.
- Avoid language that implies Windows is the default or primary platform unless justified.
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 shown first, followed by PowerShell, which is a minor bias ('windows_first') as Windows users may expect PowerShell examples to be prioritized. No evidence of missing Linux examples, exclusive Windows tools, or PowerShell-heavy bias is found. All tooling (az CLI, Helm) is cross-platform.
Recommendations
- Maintain Bash examples first, as this is standard for Azure documentation and reflects the cross-platform nature of the tools.
- Consider explicitly stating that all commands are cross-platform and that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash).
- Ensure that any future additions do not introduce Windows-only tools or patterns unless the feature is Windows-specific.
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 step, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are shown before PowerShell, which is a minor bias ('windows_first') as Windows users may expect PowerShell examples first. There are no Windows-only tools, patterns, or missing Linux examples; all CLI commands are cross-platform (az CLI).
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is shown first for consistency.
- Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS-specific guidance if needed.
- If possible, clarify that az CLI commands work identically on all platforms, and highlight any OS-specific caveats if they exist.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, but consistently presents Bash examples first. No Windows-specific tools, patterns, or terminology are used, and Linux parity is maintained throughout. There are no missing Linux examples or exclusive Windows tools mentioned.
Recommendations
- Maintain Bash examples first, as this is a common convention and supports Linux/macOS users.
- Ensure that any referenced scripts or linked resources (such as the 'Clean-up script') also provide cross-platform compatibility.
- Continue to avoid Windows-specific terminology or tools unless necessary for a Windows-only feature.
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 shown before PowerShell, which is a minor bias in favor of Linux/macOS users (not Windows). No evidence of Windows bias, such as Windows-only tools or missing Linux examples, is present.
Recommendations
- No changes needed for Linux parity; both Bash and PowerShell examples are provided.
- If desired, alternate the order of Bash and PowerShell tabs in different sections to balance presentation.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
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 it also mentions sqlcmd, which is cross-platform, SSMS is presented as the default/favored option. The examples and instructions do not provide parity for Linux/macOS GUI tools (e.g., Azure Data Studio), nor do they mention Linux-native alternatives to SSMS. However, the sqlcmd example is shown for both Linux and Windows, and Azure CLI commands are cross-platform.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for Linux/macOS users.
- Provide explicit examples for connecting using Azure Data Studio or other Linux/macOS SQL clients.
- Clarify that sqlcmd is available on Linux, macOS, and Windows, and provide installation instructions or links for non-Windows platforms.
- Consider listing cross-platform tools before Windows-only tools, or at least equally.
- Add a note about connecting from macOS/Linux environments, including any relevant firewall/network considerations.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides installation links for tools across Windows, Linux, and macOS, but Windows links are often listed first. There are specific notes about using cmd.exe instead of PowerShell on Windows, and a PowerShell-specific caveat for curl. However, Linux installation instructions are less explicit (e.g., 'install curl package'), and Linux/macOS users may need to infer steps or consult external documentation.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for tools like curl, similar to the detail given for Windows.
- Include notes for Linux/macOS users where Windows-specific caveats are mentioned (e.g., clarify curl usage on Linux/macOS shells).
- Ensure parity in troubleshooting tips and version checks for all platforms.
Azure Arc
Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows approach (using certutil and findstr) is described in detail and appears after the Linux example. The Linux method uses the standard base64 command, while Windows users are directed to use certutil and findstr, with manual steps to remove headers. All other examples (openssl, Azure CLI, kubectl) are cross-platform and do not show Windows bias. The Windows tools are mentioned explicitly, but Linux instructions are given first.
Recommendations
- Clarify that certutil and findstr are Windows-specific, and provide PowerShell alternatives for base64 encoding if possible.
- Consider providing a PowerShell example for base64 encoding, which is more modern and widely used on Windows.
- Explicitly state that the base64 command is available on Linux/macOS, and that certutil is for Windows.
- Ensure parity by mentioning that openssl, Azure CLI, and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
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 consistently refers to Azure CLI installation and usage, but in several places, links and examples reference Windows-specific installation pages (e.g., Azure CLI x64 for Windows), and the CLI directory is described generically without explicit Linux/macOS parity. However, there are no PowerShell-specific commands, Windows-only tools, or critical sections that prevent Linux/macOS users from completing the task. The management machine requirements and CLI usage are generally cross-platform, but Windows is referenced first or more explicitly.
Recommendations
- Add explicit references and links for Azure CLI installation on Linux and macOS alongside Windows.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific guidance if needed.
- When describing CLI directory/file locations, mention typical Linux/macOS paths and conventions.
- Ensure all example commands are cross-platform and note any OS-specific differences if present.
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 mentions Azure CLI, PowerShell, and REST API as supported experiences, but highlights PowerShell alongside Azure CLI in metadata and customer intent. There is a subtle emphasis on PowerShell (a Windows-centric tool) and Windows terminology appears first in the supported OS list. However, Linux is clearly supported and referenced, and there are no missing Linux examples or tools. The only Linux-specific note is a restriction, not a usage example.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows/PowerShell examples in linked pages.
- Mention Bash or other Linux-native scripting tools in the overview, not just PowerShell.
- List supported operating systems in alphabetical order or explicitly state parity.
- Add a positive Linux-specific example or use case to balance the Linux restriction note.
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
powershell_heavy
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in most features and fixes. However, Windows download links are consistently listed first, and Windows-specific installer instructions (e.g., PowerShell, msiexec, GUI, UAC) are described in detail, while Linux equivalents (such as RPM, systemctl, or command-line install instructions) are not mentioned or are referenced only via links. Some bug fixes and improvements are Windows-only, but Linux-specific changes are also noted. Overall, the bias is minor and does not prevent Linux users from accessing relevant information.
Recommendations
- Alternate the order of download links or list Linux and Windows together to avoid implicit prioritization.
- Provide Linux installer troubleshooting steps (e.g., using RPM, systemctl, sudo) alongside Windows installer guidance.
- Include Linux command-line examples or references where Windows tools (PowerShell, msiexec) are mentioned.
- Ensure that Linux-specific issues and fixes are described with equal detail as Windows-specific ones.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring Linux and Windows parity. However, PowerShell examples are always shown alongside Bash, sometimes immediately after Bash, which may create a slight impression of Windows prioritization. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform via Azure CLI. The Azure portal instructions are platform-neutral. There are no missing Linux examples, and no Windows tools are referenced exclusively.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note at the start clarifying that all CLI commands are cross-platform and Bash examples are for Linux/macOS users.
- Ensure that any screenshots or portal instructions do not reference Windows-specific UI elements.
- If possible, provide a table or summary mapping Bash/PowerShell usage to OS platforms for clarity.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first. All commands use the Azure CLI, which is cross-platform, and there are no Windows-specific tools, paths, or patterns. No Linux examples are missing, and there is no PowerShell-heavy bias. The only minor bias is that Bash (Linux/macOS) is shown first, which is actually favorable to non-Windows users.
Recommendations
- No action required. The documentation already provides parity between Linux (Bash) and Windows (PowerShell) users.
- Continue to ensure that both Bash and PowerShell examples are kept up to date and equivalent.
- Consider clarifying in the prerequisites that the Azure CLI is required and is available on all platforms.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI operation, ensuring parity for Linux/macOS and Windows users. However, in each section, PowerShell examples are consistently shown after Bash examples, indicating a minor 'windows_first' bias in ordering. There are no Windows-only tools, patterns, or missing Linux examples; all commands use cross-platform tools (Azure CLI, kubectl) and are equally applicable to Linux/macOS environments.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash is shown first for consistency, not platform preference.
- Add a note clarifying that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
- If possible, provide a brief explanation of how to install Azure CLI and kubectl on both Linux/macOS and Windows in the prerequisites or link to official installation guides.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash syntax is used elsewhere, but PowerShell appears first and is the only example for some commands. There are no Linux-specific tools or patterns mentioned, but the presence of PowerShell-only examples and occasional Windows-style command formatting suggests a mild Windows bias.
Recommendations
- Provide both Bash and PowerShell examples for all CLI commands, especially in sections where only PowerShell is shown.
- Use Bash syntax (with \ for line continuation) as the default or show Bash first, since Azure CLI is cross-platform.
- Clarify that Azure CLI commands work on all platforms and provide notes about any OS-specific differences.
- Avoid using Windows-specific environment variable syntax ($var) unless also showing the Linux equivalent (e.g., $rg vs. $RG).
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 examples for deploying Azure dashboards using Azure CLI and Azure PowerShell. The PowerShell section is presented after the CLI section, but PowerShell is highlighted as a primary method. Both tools are cross-platform, but PowerShell is often associated with Windows, and the documentation does not mention Bash or shell scripting alternatives. There are no explicit Linux/macOS-only examples or references to Linux-native tools. The JSON templates and Azure CLI commands are platform-agnostic, but the inclusion of PowerShell and its detailed example may create a slight Windows bias.
Recommendations
- Clarify that Azure CLI and PowerShell are both cross-platform and supported on Linux/macOS.
- Add explicit Bash or shell scripting examples for deploying dashboards, or note that Azure CLI commands can be run in Bash on Linux/macOS.
- Mention that PowerShell Core (pwsh) is available on Linux/macOS, and provide guidance for Linux/macOS users where relevant.
- Consider including a short note or section about using Azure CLI in Bash or other Linux shells.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell before CLI. While both are supported, PowerShell is a Windows-centric tool, and listing it first may subtly prioritize Windows users. No explicit Linux/macOS bias or missing examples are present, but minor ordering bias exists.
Recommendations
- List CLI (cross-platform) before PowerShell to emphasize Linux/macOS parity.
- Clarify that both Bash (for Linux/macOS) and PowerShell (for Windows) scripts can be generated.
- Provide examples or links showing script generation for both Bash and PowerShell, if relevant.
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 throughout, and in some sections (such as variable naming and file paths), Windows conventions are used (e.g., backslashes in PowerShell file paths). Bash examples are always shown first, but the PowerShell tab is present for every command, which may create friction for Linux/macOS users who do not use PowerShell. There are no Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Linux/macOS-specific issues or omissions are detected.
Recommendations
- Consider clarifying that PowerShell examples are for Windows users, and Bash for Linux/macOS, to reduce confusion.
- If possible, add a note that PowerShell can be used on Linux/macOS, but Bash is more common.
- Ensure file paths and variable conventions in PowerShell examples do not confuse Linux users (e.g., use forward slashes or clarify path differences).
- If a task is identical in Bash and PowerShell, consider consolidating into a single example or making Bash the default, with PowerShell as an optional tab.
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 mentioned first in all cases and receives slightly more prominence. There are no Windows-only tools or patterns, but the ordering and phrasing may subtly favor Windows users. No Linux/macOS-specific examples or guidance are missing, as Azure CLI is cross-platform and included.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions, or list Azure CLI first to better reflect cross-platform parity.
- Explicitly note that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
- Consider adding a brief example command for both Azure CLI and PowerShell in the main body, not just in tips, to reinforce parity.
- Use neutral language such as 'You can use Azure CLI or PowerShell...' instead of always leading with PowerShell.
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 mostly cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle Windows biases: the environment variable setup uses the Windows 'set' command without showing the Linux/macOS equivalent ('export'), and the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-specific) mentioned before Portal. No explicit Linux/macOS examples are given for environment variable setup, and there are no PowerShell-specific commands, but the omission of Linux/macOS equivalents creates minor friction.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- Clarify that Azure CLI commands are cross-platform and, where relevant, mention Linux/macOS usage.
- When listing cluster creation options, consider listing Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Add a note that all CLI commands work on Linux/macOS unless otherwise specified.
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 consistently lists Azure PowerShell (a Windows-centric tool) alongside Azure CLI and gives it equal prominence. The PowerShell example is detailed and appears immediately after the CLI example, which may create friction for Linux/macOS users who are less likely to use PowerShell. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not mention Linux-native tools or workflows beyond Azure CLI.
Recommendations
- Prioritize Azure CLI examples, as CLI is cross-platform and preferred by Linux/macOS users.
- Add Bash shell examples for common workflows, especially for importing images and authentication.
- Clarify that Azure PowerShell is optional and primarily for Windows users; consider placing PowerShell examples after CLI and Bash examples.
- Explicitly mention that Azure CLI and Cloud Shell are fully supported on Linux/macOS.
- Consider including a section on using Docker CLI directly for Linux/macOS users, where appropriate.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is presented first. The PowerShell example is included, but it uses Unix-style tools (tr -d '\r'), which may not be native to Windows PowerShell. All subsequent CLI commands are shown in Bash/Azure CLI syntax, and Kubernetes commands are Bash-based. There are no Windows-only tools or patterns, and Linux examples are present throughout. The bias is minor, mainly in the ordering and the PowerShell example's reliance on Unix utilities.
Recommendations
- Ensure the PowerShell example uses native PowerShell methods for string manipulation instead of Unix tools like 'tr'.
- Clarify that Bash and PowerShell examples are equivalent and provide guidance for Windows users if any Bash commands require adaptation.
- Consider alternating the order of Bash and PowerShell tabs or explicitly state that both environments are supported.
- Add a note about using Azure CLI in PowerShell on Windows, including any differences in output formatting or command syntax.