145
Pages Scanned
37
Pages Flagged
145
Changed Pages
25.5%
% Pages Flagged
Scan Information
Started At: 2026-02-09 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
39 issues found
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 page consistently uses PowerShell syntax for all CLI examples, and references PowerShell scripts (.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor are Linux-friendly scripts (e.g., .sh) provided. The CLI commands are presented in PowerShell format, which may not be directly usable on Linux/macOS terminals. This creates friction for non-Windows users, especially since bulk deployment automation is only demonstrated via a PowerShell script.
Recommendations
- Provide CLI command examples in Bash syntax alongside PowerShell, or use generic shell syntax where possible.
- Offer equivalent Bash (.sh) scripts for bulk deployment and workflow deletion, or document how to use the PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
- Explicitly note that the Azure CLI commands are cross-platform and clarify any OS-specific requirements.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps needed.
Create Pull Request
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 instructions to run it in PowerShell. There are no examples or guidance for Linux/macOS users, nor is there mention of a Bash or cross-platform alternative. This creates friction for non-Windows users who may not have PowerShell installed or prefer native shell environments.
Recommendations
- Provide a Bash or cross-platform script for migration, or document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core).
- Explicitly mention if the script is compatible with PowerShell Core on Linux/macOS, and provide installation instructions if needed.
- Add examples for running the migration on Linux/macOS, including any prerequisites or differences.
- Clarify if the migration is Windows-only; if not, ensure Linux/macOS parity in instructions.
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 intended for Linux preparation but uses Windows-centric Azure PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. The text editor example references Notepad, a Windows tool, and does not mention Linux editors. There are no Linux-native command examples for sysctl configuration or file editing.
Recommendations
- Provide native Linux shell command examples for sysctl configuration (e.g., 'sudo sysctl ...', 'echo ... | sudo tee ...').
- Mention Linux text editors such as nano, vim, or gedit instead of or alongside Notepad.
- Clarify whether Invoke-AksEdgeNodeCommand is required or if direct Linux shell access is possible, and provide both options if so.
- Ensure all critical steps can be completed using Linux-native tools and commands.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd ...) and labels these blocks as 'powershell', despite the commands being cross-platform. There are no explicit Linux/macOS shell examples, and the PowerShell label may mislead Linux/macOS users. The documentation does not mention Linux tools or shell patterns, and Windows-style command blocks are shown first and exclusively.
Recommendations
- Replace 'powershell' code block labels with 'console' or 'shell' where appropriate, since the commands are cross-platform.
- Add explicit Linux/macOS shell examples or clarify that the commands work identically on Linux/macOS terminals.
- Mention that the sqlcmd tool is available on Linux/macOS and provide installation instructions or links for those platforms.
- Ensure that any references to decoding base64 secrets include Linux/macOS command examples (e.g., 'echo <base64> | base64 -d').
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides backup and restore examples using Windows tools and file paths (e.g., SSMS, Visual Studio Code, Azure Storage Explorer, and 'C:\Backupfiles\test.bak'), but does not offer equivalent Linux/macOS examples or mention cross-platform alternatives. Windows file paths and tools are referenced first and exclusively, creating friction for Linux/macOS users.
Recommendations
- Add Linux/macOS examples for database backup, such as using sqlcmd or Azure Data Studio.
- Provide sample file paths for Linux/macOS (e.g., '/home/user/Backupfiles/test.bak') alongside Windows paths.
- Mention cross-platform tools (e.g., Azure Data Studio, sqlcmd) where SSMS or Visual Studio Code are referenced.
- Clarify that Azure Storage Explorer and Visual Studio Code are available on Linux/macOS, and provide installation links for those platforms.
- Where commands reference Windows paths, add equivalent Linux/macOS commands and paths.
Azure Arc
Troubleshoot Azure Arc resource bridge issues
...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., http2 errors), Windows paths and error messages are shown first, and Linux-specific troubleshooting steps are limited. While Linux is acknowledged (e.g., glibc errors, Azure Linux OS), CLI examples and troubleshooting commands are often Windows-centric or lack explicit Linux alternatives.
Recommendations
- Provide Linux/macOS equivalents for PowerShell troubleshooting commands (e.g., use curl or wget for http2 tests).
- Include Linux/macOS-specific guidance for SSH folder permissions and DNS resolution (e.g., use chmod, chown, dig, nslookup).
- Ensure CLI examples are cross-platform, and clarify any OS-specific requirements or steps.
- Balance error message examples to include both Windows and Linux/macOS outputs.
- Explicitly mention that Azure CLI and az arcappliance commands are cross-platform, and provide installation/downgrade instructions for Linux/macOS alongside Windows.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The release notes for Azure Connected Machine agent generally provide parity between Windows and Linux, with download links and feature tables for both platforms. However, Windows examples and tools (such as PowerShell and MSI installer instructions) are often mentioned first or exclusively, especially in installation and troubleshooting sections. Some improvements and bug fixes reference Windows-specific tools (e.g., PowerShell scripts, MSI installer, GUI application) without Linux equivalents or guidance. The known issues section provides detailed Windows installer instructions but lacks similar troubleshooting for Linux RPM/DEB installers.
Recommendations
- Ensure troubleshooting and installation instructions are provided for Linux (RPM/DEB) installers, not just Windows MSI.
- When referencing Windows tools (e.g., PowerShell, msiexec), also mention Linux equivalents (e.g., shell commands for RPM/DEB installs).
- Present download links and feature tables with Linux and Windows side-by-side, rather than Windows first.
- Where improvements reference Windows-specific scripts (e.g., ExtensionCleanup.ps1), clarify if Linux has an equivalent or explicitly state if not applicable.
- Add Linux-specific troubleshooting guidance for common installer issues, similar to the Windows installer section.
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Linux and Windows ARM template examples for each extension, ensuring parity in template content. However, all deployment instructions and sample commands exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands and Windows-style file paths are shown first and throughout, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does mention that extensions can be deployed to Linux or Windows machines, but the tooling focus is Windows-centric.
Recommendations
- Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployments.
- Include Bash shell command samples for Linux/macOS users.
- Use neutral file path examples (e.g., relative paths or Linux-style paths) in addition to Windows-style paths.
- Explicitly state that Azure CLI can be used for deployments and link to relevant CLI documentation.
- Consider alternating the order of Linux and Windows examples or grouping them together to avoid Windows-first impression.
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 is a mild Windows bias: Windows examples and tools (such as PowerShell scripts and Microsoft Update) are often presented first or in greater detail, and some advanced automation (like stale resource cleanup) is only shown in PowerShell. Windows-specific tools (Control Panel, Group Policy, WSUS, Configuration Manager) are discussed in depth, while Linux equivalents (such as package manager automation or scripting) are not. Linux instructions are present and clear, but less detailed in some areas.
Recommendations
- Provide equivalent automation scripts for Linux (e.g., Bash scripts for stale resource cleanup using Azure CLI).
- Balance the order of examples so Linux and Windows are alternated or grouped equally.
- Expand Linux sections to include more details about package manager automation, logging, and integration with configuration management tools (e.g., Ansible, Puppet, Chef).
- Where PowerShell is used for Azure automation, offer Azure CLI examples for Linux/macOS users.
- Mention Linux-specific update automation tools (e.g., unattended-upgrades, cron jobs) alongside Windows Update/WSUS.
- Clarify that all major tasks can be completed on Linux as well as Windows, and highlight any parity gaps.
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 perform clean-up tasks. There are no examples or guidance for Linux/macOS users, such as running the script with PowerShell Core (pwsh) or alternative shell environments. The documentation implicitly assumes a Windows environment and does not mention cross-platform usage.
Recommendations
- Add instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux/macOS.
- Explicitly state whether the script is compatible with non-Windows platforms, and note any limitations.
- Provide example commands for Linux/macOS users, including how to invoke the script with pwsh and handle file permissions.
- If the script is Windows-only, clarify this in the prerequisites section.
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 consistently uses PowerShell scripts and Windows-style file paths in examples, with no equivalent Bash or Linux/macOS command-line instructions. Windows tools and conventions (e.g., PowerShell, backslash file paths, .ps1 scripts) are referenced exclusively or before any cross-platform alternatives. This creates friction for Linux/macOS users, who must translate examples and scripts themselves.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell examples, especially for az CLI commands and onboarding scripts.
- Use cross-platform file path conventions (forward slashes or note both styles) in JSON and script examples.
- Clarify that az CLI commands can be run on any OS, and show both Windows (PowerShell) and Linux/macOS (Bash) syntax where relevant.
- Offer onboarding scripts in both PowerShell (.ps1) and Bash (.sh) formats, or note how Linux/macOS users can adapt them.
- Avoid referencing Windows-specific file paths (e.g., C:\Users\...) in templates; provide Linux/macOS alternatives (e.g., /home/user/...).
Azure Arc
Prepare the Environment for Workload Orchestration
...rc/workload-orchestration/initial-setup-environment.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits Windows bias in several areas. The 'winget' command is used as the sole example for installing kubectl, which is a Windows-only tool, with no Linux/macOS installation guidance. In the 'Extract ZIP' section, the Bash tab uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS, and all example paths are Windows-style (e.g., C:\path\to\archive.zip). Linux-native tools (like unzip or tar) are not mentioned. Throughout, Windows tools and patterns are presented first or exclusively, and Linux/macOS users must infer or research their own equivalents.
Recommendations
- Provide Linux/macOS installation instructions for kubectl (e.g., using curl, apt, brew, or direct download).
- In the 'Extract ZIP' section, add Linux/macOS Bash examples using 'unzip' or 'tar', and use POSIX-style paths.
- Ensure that Bash examples are cross-platform, or clearly indicate when a command is Windows-specific.
- Where PowerShell and Bash are shown, ensure Bash examples are not using Windows-only commands.
- Add notes or links for Linux/macOS users where Windows-specific tools are referenced.
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 is heavily oriented toward Windows and PowerShell environments. All onboarding scripts and usage examples are provided exclusively as PowerShell (.ps1) scripts, with instructions to run them in a PowerShell terminal. Prerequisites reference Windows-specific tools like 'winget' for installing dependencies, and there are no equivalent instructions or examples for Linux or macOS users (e.g., bash scripts, shell commands, or alternative installation methods). This creates significant friction for non-Windows users attempting to follow the onboarding process.
Recommendations
- Provide equivalent onboarding scripts in bash or shell for Linux/macOS environments, or document how to run the PowerShell scripts cross-platform (e.g., using PowerShell Core).
- Include Linux/macOS installation instructions for prerequisites (e.g., using apt, yum, brew, or direct downloads instead of 'winget').
- Add explicit notes or sections for Linux/macOS users, clarifying any differences or additional steps required.
- If the scripts are intended to be cross-platform via PowerShell Core, state this clearly and provide guidance for installing and using PowerShell on Linux/macOS.
Azure Arc
Troubleshooting for Workload Orchestration
...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most examples and command snippets are provided in PowerShell syntax, with only a few Bash examples appearing in the 'Troubleshoot service groups' section. Many steps, especially those involving Azure CLI, Docker, and Kubernetes, are shown exclusively in PowerShell, even though these tools are cross-platform and commonly used on Linux/macOS. There are missing Linux/Bash equivalents for critical troubleshooting steps, which creates friction for non-Windows users.
Recommendations
- Provide Bash/Linux equivalents for all PowerShell command snippets, especially for Azure CLI, Docker, and Kubernetes commands.
- Use cross-platform syntax (e.g., az CLI, kubectl, docker) in examples, and avoid PowerShell-specific constructs unless necessary.
- Clearly indicate when a command is platform-specific, and offer alternatives for Linux/macOS users.
- Review and update the troubleshooting steps to ensure Linux/macOS users can follow them without needing to translate PowerShell syntax.
- Where PowerShell is used for scripting (e.g., variable assignment, Base64 encoding), provide Bash alternatives (e.g., export, base64 commands).
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell, but PowerShell examples are given equal prominence throughout, despite PowerShell being primarily a Windows tool. Azure CLI examples are cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash), and the CLI examples do not clarify Linux-specific nuances. PowerShell is mentioned in every authentication table row, and the 'Next steps' section links to both CLI and PowerShell guides, but not to Linux/macOS-specific workflows. The documentation does mention using alternative container tools (like podman), but this is a brief section and lacks detailed Linux/macOS guidance.
Recommendations
- Clarify that Azure CLI commands are cross-platform and provide explicit Bash/zsh examples for Linux/macOS users.
- Reduce the prominence of PowerShell unless a Windows-specific workflow is required; consider moving PowerShell examples to a separate section or tab.
- Add Linux/macOS-specific guidance for authentication, including environment variable usage and shell scripting patterns.
- Include links to Linux/macOS getting started guides in the 'Next steps' section.
- Expand the 'alternative container tool' section with more detailed podman/skopeo examples and troubleshooting tips for Linux/macOS environments.
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, but consistently presents Bash examples before PowerShell. There are no Windows-specific tools or patterns mentioned, and Linux parity is maintained throughout. No critical sections are Windows-only.
Recommendations
- Continue to provide both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS users, and PowerShell for Windows users, to further assist cross-platform readers.
- If possible, add notes about running Azure CLI on different platforms (Windows, Linux, macOS) and any platform-specific considerations.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides parity between Windows and Linux VM extensions, with dedicated tables for each OS and clear links to relevant information. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned equally, and partner extensions are shown for both OSes. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to reinforce parity.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, ARM templates) are fully supported for both Windows and Linux, perhaps with example links for each.
- Ensure that future updates continue to provide equal detail and links for both OSes.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI tool for connecting, which is Windows-only, and mentions it before the cross-platform sqlcmd tool. However, the main CLI example for connecting uses sqlcmd, which is available on both Windows and Linux. There are no Linux-specific connection examples (e.g., using Azure Data Studio or other Linux-native tools), and SSMS is referenced as the default GUI option. The Azure CLI commands shown are cross-platform, but the documentation does not highlight Linux/macOS client options or workflows.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
- Provide explicit Linux/macOS connection examples, including any prerequisites (e.g., installing sqlcmd or Azure Data Studio).
- Clarify that SSMS is Windows-only and recommend cross-platform tools for non-Windows users.
- Consider showing Linux/macOS examples first or alongside Windows examples to avoid implicit Windows-first bias.
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 Windows links are often listed first. There are Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl), and Linux installation instructions for curl are less explicit (just 'install curl package'). There is also a PowerShell-specific note about curl aliasing, but no equivalent Linux/macOS shell guidance. Overall, Linux/macOS users can complete the tasks, but Windows is prioritized and Linux guidance is less detailed.
Recommendations
- List installation links for all platforms in parallel order (e.g., Windows, Linux, macOS) or rotate which platform is listed first.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt-get install curl' or 'brew install curl').
- Add shell-specific notes for Linux/macOS where relevant (e.g., bash/zsh differences for curl).
- Balance PowerShell-specific notes with equivalent Linux/macOS shell guidance.
- Ensure all examples and guidance are equally detailed for all platforms.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly lists PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools (Azure CLI, Visual Studio Code extension) and does not present Windows examples before Linux equivalents, nor does it omit Linux support for critical tasks. No explicit Windows-first ordering or missing Linux examples are observed.
Recommendations
- Clarify which tools are cross-platform (e.g., Azure CLI, VS Code extension) and which are Windows-only (e.g., SSMS, SQL Server PowerShell, SQL Server Profiler).
- Add references to Linux/macOS-compatible management tools, such as 'sqlcmd', Azure Data Studio, or other CLI utilities.
- Explicitly state PowerShell scripting support is limited to Windows, and suggest Bash or other scripting alternatives for Linux/macOS users.
- Where possible, provide links or guidance for Linux/macOS users to achieve similar manageability and scripting tasks.
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 for both Windows and Linux, but the 'Interactive browser login' is described as 'Windows only' and is listed first. Windows certificate store options are explained in detail, while Linux equivalents are not mentioned. The access token example references a Windows PowerShell cmdlet ('Get-AzAccessToken') without mentioning Linux alternatives. Overall, Linux is supported, but Windows-specific tools and flows are presented first or exclusively.
Recommendations
- Present authentication options in a neutral order (e.g., device code login first, since it's default for Linux).
- When referencing Windows certificate stores, add a note about Linux certificate file storage and permissions.
- For access token acquisition, mention cross-platform methods (e.g., Azure CLI 'az account get-access-token') alongside PowerShell.
- Add explicit Linux/macOS examples where Windows-specific tools or flows are described.
- Clarify that all examples work on both Windows and Linux unless otherwise noted.
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
missing_linux_example
windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files when creating Kubernetes secrets, but the Windows-specific instructions (using certutil and findstr) are more detailed and appear after the Linux example. However, the Linux example is brief and does not address decoding or removing headers, while the Windows example does. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and does not show Windows bias.
Recommendations
- Expand Linux instructions for base64 encoding/decoding to match the detail provided for Windows (e.g., how to decode, how to remove headers if needed).
- Mention that base64 encoding/decoding can be done on macOS using the same Linux commands.
- Consider providing a PowerShell example for base64 encoding/decoding for Windows users, but also ensure parity with Linux/macOS shell commands.
- Clarify that OpenSSL, Azure CLI, and kubectl are cross-platform and provide links or notes for installation on all OSes.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation references Azure CLI installation with links that default to Windows instructions and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-specific commands or tools, and the CLI commands shown are cross-platform. No explicit Linux/macOS examples or installation guidance are given, but there is no critical Windows-only content.
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 specify any OS-specific requirements.
- Provide example CLI commands and file paths for Linux/macOS environments.
- Ensure parity in documentation for management machine prerequisites and troubleshooting steps across platforms.
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 in the critical 'Acquire an access token using REST API' section. The PowerShell example is more visually prominent, with a screenshot and detailed explanation preceding the Bash example. Windows group membership requirements are listed before Linux equivalents in prerequisites. References to PowerShell are made before Azure CLI in related content.
Recommendations
- Present Linux/Bash and Windows/PowerShell examples side-by-side or alternate their order to avoid Windows-first bias.
- Ensure screenshots and example outputs for both platforms are equally prominent.
- List Linux prerequisites before or alongside Windows prerequisites.
- Mention Azure CLI and Bash examples before or alongside PowerShell in related content.
- Consider adding parity notes or clarifications for macOS users where relevant.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring Linux and Windows parity. However, in some sections, PowerShell examples are shown immediately after Bash, and in a few cases, minor Windows-specific notes (such as carriage return handling) are included. The Bash examples are consistently presented first, and Linux-specific instructions (such as base64 encoding) are given. No Windows-only tools or patterns are used, and Linux users can complete all tasks without friction.
Recommendations
- Maintain Bash and PowerShell parity for all steps.
- Ensure Linux-specific notes (such as file encoding, base64 commands) are clearly marked.
- Consider clarifying that Bash examples are suitable for Linux/macOS, and PowerShell for Windows, to help users select the right tab.
- If possible, add a brief introductory note indicating cross-platform support.
- Continue to avoid Windows-only tools or commands unless the feature is Windows-specific.
Azure Arc
What's 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 presents new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral, there are instances where Windows-specific features or tools are mentioned first or exclusively. For example, the June 2025 update highlights customization for Windows VMs, and Windows Server Management is detailed in January 2025. In October 2024, Windows-centric tools like System Center Configuration Manager and Group Policy are listed before Linux-friendly options like Ansible. Azure PowerShell is also listed alongside Azure CLI and REST APIs, but not prioritized. Linux-specific features are present (e.g., SSH-based Arc agent installation), but Windows examples and tools tend to appear first or are more detailed.
Recommendations
- Ensure Linux and Windows features are presented with equal prominence and detail.
- When listing at-scale agent installation methods, mention Linux-friendly tools (e.g., Ansible, Bash scripts) before or alongside Windows tools.
- Provide explicit examples or links for Linux/macOS users where Windows tools (e.g., Group Policy, SCCM) are referenced.
- Consider alternating the order of Windows and Linux features in release notes to avoid implicit prioritization.
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 throughout, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, rather than in parallel tabs or with equal prominence. There are no Windows-specific tools or patterns used; all commands rely on the Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux users can complete all tasks as described.
Recommendations
- Consider presenting Bash and PowerShell examples in parallel tabs or with equal prominence, rather than consistently listing Bash first.
- Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Add a brief note at the start clarifying that both Bash and PowerShell are supported, and users should select the shell appropriate for their OS.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the PowerShell section is presented immediately after Bash and is equally detailed. There is no evidence of Windows-only tools or patterns, but PowerShell is featured as a primary scripting option alongside Bash, which may suggest a slight Windows bias. Bash is presented first, which is positive for Linux parity. All instructions are cross-platform via the Azure CLI, and no Windows-specific tools or patterns are used.
Recommendations
- Clarify that both Bash and PowerShell examples are cross-platform and can be used on Windows, Linux, and macOS.
- Explicitly mention that Azure CLI commands work on all major operating systems.
- Consider adding a note that PowerShell Core is available on Linux and macOS, reducing Windows bias.
- If possible, add a brief section or note for macOS users, confirming compatibility.
- Ensure that Bash and PowerShell examples are kept in sync and equally detailed.
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 always shown after Bash, which is a minor bias ('windows_first') as Linux/macOS users see their examples first. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All commands use the Azure CLI and Helm, which are cross-platform.
Recommendations
- Maintain the current structure, as Bash and PowerShell parity is excellent.
- Consider clarifying that both Bash and PowerShell examples are equivalent and suitable for their respective platforms.
- If possible, add a short note at the top indicating that all steps can be performed on Linux, macOS, or Windows, depending on shell preference.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell examples, which is a minor bias in favor of Linux/macOS users ('windows_first' bias, but in reverse). There are no Windows-specific tools, patterns, or commands used, and all instructions are cross-platform via the Azure CLI and Helm. No critical steps are Windows-only.
Recommendations
- Maintain the current structure, as both Bash and PowerShell examples are provided.
- Consider alternating the order of Bash and PowerShell tabs in some sections to further balance presentation.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows (with Bash or PowerShell).
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 between Linux/macOS and Windows users. However, in nearly all sections, Bash examples are presented before PowerShell examples. No Windows-specific tools, patterns, or terminology are used exclusively, and Linux examples are not missing. The only minor bias is the consistent ordering of Bash before PowerShell, which favors Linux users rather than Windows.
Recommendations
- Maintain the current structure, as both Bash (Linux/macOS) and PowerShell (Windows) examples are provided for all commands.
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that both environments are fully supported.
- Add a brief note at the top clarifying that all commands are cross-platform and users should select the tab matching their OS.
Azure Portal
Get subscription and tenant IDs in the Azure portal
...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is consistently mentioned first and receives slightly more emphasis. While Azure CLI is cross-platform, the ordering and phrasing may subtly favor Windows users. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Alternate the order in which Azure PowerShell and Azure CLI are mentioned, or explicitly note that Azure CLI is cross-platform.
- Add brief clarifications that Azure CLI works on Linux/macOS, and PowerShell is available cross-platform but may be more familiar to Windows users.
- Consider providing a short example command for both Azure CLI and PowerShell, rather than just linking to external docs.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash/Linux shell examples for those commands. Throughout the rest of the release notes, CLI instructions are generally shown in Bash syntax, but the presence of PowerShell-only examples and the occasional use of Windows-style command formatting suggests a mild Windows bias.
Recommendations
- For every CLI example shown in PowerShell, provide an equivalent Bash/Linux shell example.
- When referencing CLI commands, use cross-platform syntax (e.g., avoid PowerShell backticks for line continuation; use Bash line continuation with '\' as well).
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide guidance for users of each platform.
- Review all examples to ensure Linux/macOS users can easily follow along without confusion.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell is always shown after Bash and receives equal coverage. There are no Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, PowerShell examples are included throughout, which may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux/macOS. The Bash examples are always presented first, mitigating the bias.
Recommendations
- Consider clarifying that PowerShell examples are for users on Windows or those who prefer PowerShell, and Bash is suitable for Linux/macOS.
- Explicitly state that all commands are cross-platform and can be run on any OS with Azure CLI and Helm installed.
- Optionally, provide a note about PowerShell Core availability on Linux/macOS for users who prefer PowerShell.
- Ensure that Bash examples are always shown first, as is currently done, to prioritize Linux/macOS parity.
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is not strictly Windows-only, PowerShell is more commonly associated with Windows environments, and its mention before Bash or Linux shell scripting may signal a Windows-first bias. No explicit Linux/macOS examples or tools are referenced, and the documentation does not clarify parity for Linux users.
Recommendations
- Explicitly mention Bash or Linux shell scripting as supported output types for code generation.
- Provide examples or clarify that Azure Copilot can generate scripts for Bash, Azure CLI, and PowerShell, covering all major platforms.
- Ensure that references to scripting tools are inclusive, e.g., 'Generating CLI, Bash, and PowerShell scripts.'
- Add a note about cross-platform compatibility for generated scripts.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the PowerShell example is given equal prominence and appears immediately after the CLI example, which may suggest a slight Windows bias. There are no Linux-specific command-line examples (e.g., Bash scripts), and PowerShell is primarily a Windows-centric tool, though it is available cross-platform. The documentation does not mention Linux tools or patterns (such as shell scripting or using Docker CLI directly) and does not provide explicit Linux/macOS guidance.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for common tasks such as importing images.
- Clarify that Azure CLI is cross-platform and works natively on Linux/macOS, and recommend it as the default for non-Windows users.
- Mention that PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux/macOS environments.
- Consider including a section or note for Linux/macOS users about using Azure CLI in their native shell environments.
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 parity between Azure CLI and Azure PowerShell throughout, but consistently presents Azure PowerShell examples alongside Azure CLI. Azure PowerShell is a Windows-centric tool, and its inclusion as a primary example may create friction for Linux/macOS users, especially since PowerShell is less commonly used on those platforms. However, all CLI commands are cross-platform and there are no Windows-only tools or patterns. No Linux-specific examples or shell scripts are provided, but the CLI coverage is sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is cross-platform, but more commonly used on Windows.
- Consider providing Bash shell script examples for common import scenarios, especially for Linux/macOS users.
- Explicitly state that Azure CLI commands work on all platforms (Windows, Linux, macOS).
- If possible, add a note or section about using Azure CLI in Bash or other Linux-native environments.
- Review the order of examples: consider showing Azure CLI first, or only, unless PowerShell is required.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides a generally cross-platform approach, using Helm and Azure CLI commands, which work on Windows, Linux, and macOS. However, there are minor signs of Windows bias: the environment variable is set using the Windows-style 'set' command without a Linux/macOS equivalent, and the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-specific) mentioned before Portal. No PowerShell-specific commands are given, and most examples use cross-platform tools, but the lack of explicit Linux/macOS shell equivalents for environment variable setting may create friction.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands when setting environment variables (e.g., ACR_NAME).
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS as well as Windows.
- When listing options for creating AKS clusters, consider mentioning Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Review all shell command examples to ensure both Windows and Linux/macOS users are accommodated.
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
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the Bash example is presented first. All other command-line examples use Bash syntax or are cross-platform Azure CLI commands. No Windows-specific tools or patterns are favored, and Linux users are not blocked from completing any tasks.
Recommendations
- Maintain parity by continuing to provide both Bash and PowerShell examples where relevant.
- Consider explicitly stating that all Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Optionally, provide a note that PowerShell Core is available on Linux/macOS for users who prefer PowerShell.