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 1801-1825 of 2334 flagged pages
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using sqlcmd, but these examples are shown exclusively in PowerShell syntax (with the PowerShell prompt and formatting). There is no explicit Linux/macOS shell example, even though the underlying commands (kubectl, sqlcmd) are cross-platform. The use of PowerShell formatting and prompt may confuse Linux/macOS users, and the documentation implicitly prioritizes Windows usage patterns.
Recommendations
- Provide equivalent Linux/macOS shell (bash) examples alongside PowerShell examples, especially for sqlcmd and kubectl commands.
- Use a generic shell prompt (e.g., $ or #) for cross-platform commands, or clarify that the commands work on all platforms.
- Explicitly mention that sqlcmd and kubectl are cross-platform tools and provide installation guidance for Linux/macOS if needed.
- Avoid using PowerShell-specific formatting unless the command is truly Windows-only.
Create Pull Request
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 Example
Windows First
Summary
The documentation provides both Linux and Windows approaches for base64 encoding files, but the Windows method (certutil) is presented as a special case, with additional manual steps required. The Linux command (base64) is shown first and described as usable on 'any Linux distribution.' The Windows example is included, but requires extra manual intervention (removing headers) and additional commands. There is no PowerShell-heavy bias, and all Azure CLI and kubectl examples are cross-platform. The overall bias is minor, with Windows tools mentioned but not prioritized.
Recommendations
- Clarify that both Linux and Windows users can use OpenSSL and Azure CLI/kubectl.
- Provide a PowerShell example for base64 encoding on Windows, which may be more familiar to Windows users than certutil.
- Explicitly state that the Azure CLI and kubectl commands work on both Windows and Linux.
- Consider mentioning cross-platform tools (e.g., Git Bash, WSL) for Windows users who prefer Linux-style commands.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is listed before sqlcmd and there are no examples for popular Linux/macOS GUI tools (such as Azure Data Studio or DBeaver). The documentation does not mention Linux-specific connection patterns or troubleshooting, and the focus on SSMS may create friction for Linux/macOS users.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit examples for connecting using Azure Data Studio or other Linux/macOS-compatible tools.
- Ensure that Linux/macOS users are aware that sqlcmd is available natively and provide installation instructions or links.
- Consider listing cross-platform tools before or alongside SSMS to avoid Windows-first bias.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are consistently presented alongside CLI, and in some sections, PowerShell is shown before CLI. There is a slight bias toward Windows/PowerShell, as PowerShell is a Windows-centric tool, and its inclusion may imply Windows as a primary platform. However, Azure CLI examples are present and are cross-platform, and Linux-specific instructions (such as environment variable export syntax) are included. No Windows-only tools or patterns are used, and Linux users can complete all tasks.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and PowerShell is primarily for Windows users.
- Add a short note clarifying that both Azure CLI and PowerShell are supported, but CLI is recommended for Linux/macOS environments.
- Consider including bash shell script examples for common tasks, especially for onboarding and updating clusters.
- Where environment variables are set, show both Linux (export) and Windows (set) syntax for parity.
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 page for Azure Arc resource bridge system requirements shows minor Windows bias in the management machine requirements section, where the Azure CLI installation link defaults to the Windows version. However, the overall content is cross-platform, and does not reference Windows-only tools or patterns. No PowerShell examples or Windows-specific commands are present, and Linux/macOS users can complete all tasks described.
Recommendations
- Update the Azure CLI installation link in the management machine requirements section to reference the generic Azure CLI install page, or provide links for Windows, Linux, and macOS.
- Explicitly state that the management machine can be Windows, Linux, or macOS, as long as Azure CLI is installed.
- Add a note clarifying that all CLI commands are cross-platform unless otherwise stated.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with parity in most features and fixes. However, Windows download links and version numbers are consistently listed first, and Windows-specific installer tools (MSI, PowerShell, Command Prompt) are referenced in troubleshooting and known issues, with no equivalent Linux installer guidance or troubleshooting. Some improvements and bug fixes reference Windows tools/scripts (e.g., ExtensionCleanup.ps1, MSI signature verification), while Linux equivalents are not always described.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
- Add Linux-specific troubleshooting guidance for installer issues, including common commands (e.g., using rpm, dpkg, systemctl) and privilege escalation (e.g., sudo).
- When referencing Windows tools/scripts (e.g., PowerShell, MSI), provide Linux equivalents or clarify if the feature is Windows-only.
- Ensure that bug fixes and improvements for Linux are described with equal detail and visibility as Windows items.
- Consider a summary table or section highlighting Linux-specific changes and known issues, similar to Windows.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell in all major workflows. PowerShell examples are included alongside CLI, and in some cases, Windows-specific notes are given (e.g., PowerShell syntax, log file locations). However, Linux parity is generally maintained: CLI examples are cross-platform, Linux log file locations are specified, and Linux onboarding is referenced. Windows examples (PowerShell) are sometimes shown before CLI or Linux equivalents, and Windows-specific notes are occasionally highlighted.
Recommendations
- Ensure CLI examples are always shown before or alongside PowerShell, as CLI is cross-platform.
- Explicitly state that Azure CLI commands work on both Windows and Linux, and provide any necessary Linux-specific syntax or troubleshooting tips.
- Where PowerShell is used, clarify its applicability (Windows only) and provide Bash or shell alternatives if relevant.
- Review the order of examples to avoid Windows-first bias; consider alternating or grouping by platform.
- Expand Linux-specific guidance where possible (e.g., onboarding, log locations, troubleshooting).
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, explicitly mentioning both platforms and providing URLs for both installation packages. However, there are minor signs of Windows bias: Windows installation resources are listed first in tables, Windows Admin Center is referenced as a management tool (with no Linux equivalent mentioned), and Windows-specific TLS configuration issues are highlighted with a dedicated troubleshooting link. Linux is referenced, but Windows tools and patterns are sometimes prioritized or mentioned first.
Recommendations
- List Linux and Windows installation URLs side-by-side or alternate their order to avoid Windows-first bias.
- When referencing management tools like Windows Admin Center, clarify if there are Linux alternatives or explicitly state that it is Windows-only.
- Provide links to Linux-specific troubleshooting or configuration guidance (e.g., OpenSSL TLS configuration) alongside Windows guidance.
- Ensure examples and guidance for proxy, firewall, and TLS configuration are equally detailed for both platforms.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Windows and Linux platforms for Azure Arc-enabled servers and provides parity in most sections. However, there is a mild Windows bias: PowerShell examples are provided alongside Azure CLI, and PowerShell is presented as a primary scripting option, which is more relevant to Windows users. In some sections, Windows-specific extensions are listed first, and PowerShell is mentioned before Linux shell alternatives. Azure CLI commands are shown as cross-platform, but PowerShell is still given equal prominence, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Explicitly state that Azure CLI commands work on both Linux and Windows, and consider showing Linux shell (bash/zsh) usage examples where relevant.
- Where PowerShell is mentioned, clarify its availability on Linux/macOS and provide links to installation instructions for those platforms.
- Consider adding sample scripts or command snippets for bash/zsh where appropriate, especially for Linux users.
- Ensure that Linux-specific extensions or scenarios are given equal prominence in lists and examples.
- Review the order of examples and tools to avoid always listing Windows/PowerShell first.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but there is a mild bias toward Windows. Windows examples and log file paths are often mentioned first, and PowerShell syntax is used in Windows examples. Windows-specific tools and concepts (such as PowerShell, environment variables, and Windows log paths) are referenced before their Linux equivalents. However, Linux examples and paths are present and reasonably detailed.
Recommendations
- Alternate Windows and Linux examples so Linux is not always second.
- Provide Bash or shell script equivalents for any PowerShell-heavy examples.
- Where referencing log file locations or config paths, mention Linux paths first or equally.
- Ensure troubleshooting steps and remediation advice reference both Windows and Linux commands/tools where applicable.
- Clarify when a solution is Windows-specific and offer Linux alternatives if possible.
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux examples for key configuration tasks, but Windows/PowerShell examples are consistently presented first. In some sections, Windows-specific command syntax (PowerShell) is highlighted before Linux (bash), and references to Windows tools (e.g., 'elevated command console') appear before their Linux equivalents. However, Linux parity is generally maintained, and most examples are given for both platforms.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Clarify that both Windows and Linux are equally supported for Azure Arc-enabled server extensions.
- Where possible, use generic CLI examples (e.g., Azure CLI) before platform-specific commands.
- Explicitly mention macOS support if applicable, or clarify its status.
- Use neutral language (e.g., 'run as administrator or root') instead of Windows-centric terms like 'elevated command console'.
Azure Arc
What is Azure Arc-enabled VMware vSphere?
...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle signs of Windows bias. Windows/PowerShell examples and references are often mentioned first or exclusively, such as in links to Windows-specific tabs and PowerShell runbooks. Linux equivalents are referenced but not always with equal prominence or detail. Some links default to Windows tabs, and automation examples highlight PowerShell before Python. There are no explicit Linux command examples or Linux-centric workflow illustrations.
Recommendations
- Ensure that all linked guides and quickstarts include Linux/macOS examples and reference them equally alongside Windows.
- When listing supported automation tools (PowerShell, Python, etc.), avoid putting Windows tools first unless justified by usage statistics.
- Add explicit Linux/macOS command-line examples (e.g., Bash, CLI) where PowerShell is referenced.
- Review linked pages to ensure Linux parity in tabs and examples.
- Where possible, provide screenshots or walkthroughs for Linux environments in addition to Windows.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell CLI examples for updating external validation status, but consistently presents Bash examples first. There are no Windows-specific tools, patterns, or exclusive references; all API and CLI instructions are cross-platform. No PowerShell-only or Windows-only bias is present, and Linux parity is maintained throughout.
Recommendations
- Continue to provide both Bash and PowerShell examples for CLI commands.
- Consider explicitly stating that the Azure CLI commands work identically on Linux, macOS, and Windows.
- If possible, add a short note clarifying that the examples are cross-platform and that the Azure CLI is supported on all major OSes.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used exclusively or preferentially. All commands use the Azure CLI and Helm, both cross-platform tools. There are no missing Linux examples, nor is there any evidence of Windows-only tools or instructions.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell examples are supported on all platforms where Azure CLI and Helm are available.
- Add a brief note clarifying that Bash examples are suitable for Linux/macOS terminals and Windows users using WSL or Git Bash.
Azure Arc
Delete Resources in Workload Orchestration
...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for each command, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and the tab labels sometimes use 'PowerShell' instead of 'Windows', which may subtly imply Windows as a primary platform. There are no missing Linux examples or exclusive Windows tools/patterns.
Recommendations
- Ensure Bash and PowerShell examples are presented with equal prominence, possibly alternating their order or using neutral tab labels such as 'Linux/macOS' and 'Windows'.
- Clarify that both Bash and PowerShell examples are functionally equivalent and applicable depending on the user's OS.
- Consider adding a brief note at the top indicating that all commands are cross-platform via Azure CLI, and users can choose their preferred shell.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity between Linux/macOS and Windows users. However, in each section, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing, and no Windows-only tools are referenced.
Recommendations
- Continue to provide both Bash and PowerShell examples for all CLI operations.
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows, to reinforce parity.
- Add a short note clarifying that Azure CLI commands work on all platforms (Windows, Linux, macOS) and that Bash examples are suitable for Linux/macOS users.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are sometimes shown immediately after Bash, and certain minor details (such as base64 encoding) are explained in both environments. No Windows-specific tools or patterns are used, and Linux/macOS equivalents are present throughout. The documentation does not prioritize Windows tools or omit Linux examples, but PowerShell is given equal prominence, which may be unnecessary given the cross-platform nature of Azure CLI and Kubernetes.
Recommendations
- Consider listing Bash examples first in each section, as Bash is the default shell for Linux/macOS and is also available on Windows via WSL.
- Clarify that Bash examples are suitable for Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Where possible, consolidate examples to highlight cross-platform commands (e.g., Azure CLI, Docker, kubectl) and minimize shell-specific syntax unless necessary.
- Ensure that any shell-specific instructions (such as file encoding or base64 commands) are clearly marked for their respective environments.
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 nearly every section, Bash examples are shown first, followed by PowerShell. No Windows-specific tools or patterns are used exclusively, and all commands rely on cross-platform Azure CLI and Helm tools. There are no missing Linux examples, nor are Windows tools mentioned before their Linux equivalents.
Recommendations
- Maintain the current structure, as Linux/macOS parity is strong.
- Consider alternating the order of Bash and PowerShell tabs in some sections, or explicitly note that Bash is suitable for Linux/macOS and PowerShell for Windows, to reinforce parity.
- Ensure that any future additions continue to provide both Bash and PowerShell examples.
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 before PowerShell. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There are no missing Linux examples or Windows-only instructions.
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.
- Optionally, add a note at the top explaining the cross-platform nature of Azure CLI and the provided examples.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used, and all commands are cross-platform (Azure CLI, Helm).
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid perceived bias.
- Explicitly mention that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a brief note clarifying that Azure CLI and Helm are available on all major 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 throughout, but PowerShell examples are consistently presented after Bash. There are no Windows-exclusive tools or patterns, and Linux parity is maintained for all commands. No critical steps are Windows-only, and the Azure CLI and kubectl are cross-platform.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell are supported on Windows, Linux, and macOS to reinforce cross-platform parity.
- If possible, add a note clarifying that PowerShell Core is available on Linux/macOS, not just Windows.
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 primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux/Windows example is provided, SSMS is presented as the default client, potentially creating friction for Linux/macOS users. No Linux-native GUI tools (e.g., Azure Data Studio, DBeaver) are mentioned. Azure CLI commands are cross-platform, but the client connection guidance is slightly Windows-biased.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting from macOS and Linux, including GUI and CLI tools.
- Clarify that sqlcmd is available on Linux/macOS and provide installation guidance or links.
- Consider listing sqlcmd first, or equally, when describing connection options.
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 explanations about PowerShell's curl alias, but there are no equivalent Linux/macOS-specific notes or troubleshooting tips. The Linux installation for curl is mentioned only as 'install curl package' without a link or further guidance, which is less helpful than the Windows section.
Recommendations
- Present installation links for all platforms (Windows, Linux, macOS) in parallel, rather than listing Windows first.
- Provide Linux/macOS-specific troubleshooting tips or notes, similar to the PowerShell/cmd.exe guidance for Windows.
- Add direct links or instructions for installing curl on Linux and macOS, not just a brief mention.
- Ensure parity in detail and guidance for all platforms, including version checks and command usage.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical tasks, but consistently presents Azure PowerShell (a Windows-centric tool) alongside Azure CLI. In some sections, PowerShell examples are shown immediately after CLI, and environment variable examples are given for both Bash (Linux/macOS) and PowerShell (Windows). However, there are no Linux-specific command-line tools (e.g., shell scripts, curl, etc.) or explicit macOS guidance. The documentation is not Windows-only, but the presence of PowerShell throughout and the lack of Linux/macOS-specific examples creates mild Windows bias.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
- Add notes or examples for Linux/macOS users where relevant (e.g., shell scripting, handling environment variables, troubleshooting).
- Consider including troubleshooting tips for Linux/macOS environments, such as proxy configuration nuances.
- Where possible, clarify that all commands (except PowerShell) are compatible with Linux/macOS.