Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 2176-2200 of 2334 flagged pages
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.
Create Pull Request
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.
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 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.
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.
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 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 Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents Windows download links and version numbers before Linux equivalents and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and installer behaviors. However, Linux support is clearly present, and Linux-specific changes are documented. There are no critical sections that exclude Linux users, but some minor friction exists due to Windows-first ordering and references to Windows tools.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them together to avoid implying priority.
- Where installer troubleshooting is discussed, provide equivalent Linux instructions or clarify when an issue is Windows-only.
- When referencing Windows tools (e.g., PowerShell, msiexec), provide Linux equivalents (e.g., shell commands, package managers) where relevant, or explicitly state when an issue or instruction is Windows-specific.
- Consider adding a brief section summarizing Linux-specific installation or troubleshooting tips, similar to the Windows installer guidance.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Windows and Linux support for Run command on Azure Arc-enabled servers, but there is a subtle bias toward Windows: PowerShell is highlighted as a primary experience alongside Azure CLI and REST, and examples or next steps list PowerShell before REST API, with no explicit mention of Bash or Linux shell scripting. The documentation does not provide Linux-specific examples or tools, and minor Linux limitations (e.g., name length) are relegated to notes.
Recommendations
- Add explicit Linux/Bash scripting examples and workflows alongside PowerShell examples.
- Highlight Linux shell usage in the 'Experiences' section, e.g., Bash or sh, not just PowerShell.
- Ensure parity in next steps by including a dedicated Linux example page or section.
- Mention Linux-specific considerations or best practices more prominently, not just in notes.
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
Powershell Heavy
Windows Tools
Summary
The documentation generally presents authentication options and usage patterns that apply to both Windows and Linux. However, there is a mild Windows bias: Windows-specific authentication methods (interactive browser login, certificate store usage) are described before Linux equivalents, and PowerShell tools (Get-AzAccessToken) are mentioned for access token retrieval without Linux alternatives. The interactive browser login is called out as Windows-only, but Linux options are present and described. Windows certificate store usage is detailed, while Linux certificate handling is only briefly mentioned. Examples and usage instructions are mostly OS-neutral, but some flags and workflows are explained with Windows-first language.
Recommendations
- Add explicit Linux/macOS instructions for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token') alongside PowerShell examples.
- Clarify certificate handling for Linux (e.g., where to store PEM/PFX files, recommended permissions, sample file paths).
- Where authentication methods differ by OS, present Linux/macOS options first or in parallel with Windows options.
- If possible, provide example commands for Linux/macOS shells (bash/zsh) alongside any Windows/PowerShell-specific examples.
- For certificate-based authentication, include a Linux example for specifying the certificate path and permissions.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM extensions before Linux VM extensions, listing a more extensive set of Windows extensions and providing more detailed descriptions and links for Windows scenarios. However, Linux extensions are also covered with equivalent tables and links, and partner extensions are shown for both platforms. No CLI or PowerShell command examples are present, and deployment methods are listed in a neutral order.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to emphasize parity.
- Ensure that the number and detail of Linux extension entries matches Windows where possible, or clarify if certain extensions are Windows-only.
- Add explicit examples or links for deploying extensions on Linux using Azure CLI, PowerShell, and templates, if such examples exist for Windows.
- Highlight cross-platform deployment methods and note any platform-specific limitations.
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 both Windows and Linux release notes and download links, but consistently lists Windows first in download links and feature tables. Some instructions and known issues reference Windows-specific tools (e.g., PowerShell, msiexec) without Linux equivalents. There are also several Windows-only improvements and bug fixes, but these are clearly marked. Linux-specific changes are included where relevant, but Linux users may need to follow links for installation instructions rather than having direct commands shown.
Recommendations
- Alternate the order of Windows and Linux in download links and feature tables, or list them alphabetically.
- Where Windows-specific installation instructions are given (e.g., using msiexec or PowerShell), provide equivalent Linux commands or a direct link to Linux installation instructions.
- Add explicit Linux installation/upgrade command examples in the release notes for parity with Windows instructions.
- Continue clearly marking OS-specific changes, but ensure Linux improvements are highlighted equally.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Windows and Linux support for Run command on Azure Arc-enabled servers, but it lists PowerShell and Azure CLI as the primary experiences, with PowerShell examples and links shown before Linux-specific details. There are no explicit Linux command examples or Linux tool references in the main page, and the 'Next steps' section lists PowerShell before REST API and does not highlight Linux-specific guidance.
Recommendations
- Add explicit examples or references for Linux shell usage (e.g., Bash scripts) in the main documentation.
- Ensure parity in the 'Next steps' section by including links or notes for Linux-specific usage, such as Bash or shell scripting.
- Where PowerShell is mentioned, clarify that Bash or other Linux shells are equally supported and provide examples.
- Consider alternating the order of Windows and Linux references, or presenting them side-by-side, to avoid implicit prioritization.