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 1826-1850 of 2334 flagged pages
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com', 'sts.windows.net', 'servicebus.windows.net', 'login.windows.net') and Windows NTP as a default, which may imply Windows-centric patterns. Windows NTP is mentioned as the default for Hyper-V, but Linux NTP alternatives are not discussed. Some URLs and notes reference Windows, but Linux equivalents or patterns are not always provided or explained. However, the documentation does mention Linux-specific endpoints (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com') and SSH as a connectivity requirement, which is cross-platform.
Recommendations
- Add explicit Linux NTP server examples (e.g., 'ntp.ubuntu.com', 'pool.ntp.org') and clarify when Windows NTP is required versus when Linux NTP is appropriate.
- Where Windows-specific URLs or services are mentioned, provide Linux equivalents or clarify if the requirement applies to both OS types.
- Ensure examples and notes do not default to Windows patterns unless the feature is Windows-only.
- Add clarification on management machine OS requirements and provide guidance for both Windows and Linux administrators.
Create Pull Request
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 and links to the Windows installation page first, but does not provide parity for Linux/macOS users (e.g., links to their installation instructions or mention them explicitly). All CLI examples are generic and not Windows-specific, but the management machine requirements and CLI links are Windows-centric.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside the Windows link.
- Clarify that the management machine can be Windows, Linux, or macOS, as Azure CLI is cross-platform.
- Provide example CLI commands for Linux/macOS where relevant (e.g., file paths, shell syntax differences).
- Ensure that references to 'current CLI directory' are clear for all OSes (e.g., explain how to find the working directory on Linux/macOS).
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 clear parity in feature and bug fix descriptions. However, Windows download links and version numbers are consistently listed before Linux, and Windows-specific installer instructions (e.g., PowerShell, msiexec, GUI) are detailed, while Linux installation methods and troubleshooting are referenced only via links. Some improvements and bug fixes reference Windows tools (e.g., PowerShell scripts, MSI signature verification), but Linux equivalents are not always explained in the same detail.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers to avoid Windows-first bias.
- Provide explicit Linux installation and troubleshooting instructions (e.g., command-line examples for RPM/DEB, systemctl usage) alongside Windows installer guidance.
- Where Windows tools/scripts are mentioned (e.g., PowerShell, MSI), briefly note the Linux equivalent or clarify if not applicable.
- Ensure that Linux-specific improvements and bug fixes are described with equal detail as Windows items.
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 clear parity between Windows and Linux VM extensions, with dedicated tables for each OS and links to relevant usage and deployment information. However, the Windows extensions table is presented before the Linux extensions table, which is a minor 'windows_first' bias. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned equally for both OSes, and partner extensions are shown for both platforms. 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, templates) are available for both Windows and Linux extensions.
- Add a brief introductory note clarifying that Azure Arc-enabled servers support both Windows and Linux equally, to reinforce cross-platform support.
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
Minor Windows Tools
Summary
The documentation covers troubleshooting Azure Connected Machine agent issues for both Windows and Linux, providing parity in error codes, exit codes, and troubleshooting steps. However, in the 'Agent verbose log' section, Windows examples are presented first and use PowerShell syntax, while Linux examples follow. There is a minor mention of Windows-specific log file locations and PowerShell requirements, but Linux equivalents are also provided. Overall, the bias is minimal and does not significantly impact Linux/macOS users.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid 'windows_first' bias.
- Where possible, provide both Windows and Linux log file paths together rather than separately.
- Explicitly mention macOS support or limitations if applicable.
- Ensure that troubleshooting steps reference both Windows and Linux commands/tools equally.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are consistently shown alongside CLI and portal instructions. Some minor Windows-specific notes (e.g., PowerShell command syntax, log file locations) are included, but Linux equivalents are also provided. Windows examples and tools are not exclusive, but are sometimes referenced first or with more detail. The documentation is not Windows-only and covers Linux scenarios, but there is a slight tendency to mention Windows tools and patterns before Linux equivalents.
Recommendations
- Ensure Linux and macOS instructions/examples are always present and equally detailed.
- Where PowerShell is referenced, clarify that it is available on Linux/macOS as well, or provide Bash/Linux shell alternatives where appropriate.
- Alternate the order of CLI and PowerShell examples so Linux users see their preferred tools first in some sections.
- Explicitly note cross-platform compatibility for Azure CLI and agent commands.
- Review log file instructions to ensure Linux paths are shown with equal prominence to Windows paths.
Azure Arc
Automatic extension upgrade for Azure Arc-enabled servers
...e-arc/servers/manage-automatic-vm-extension-upgrade.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Windows and Linux Azure Arc-enabled servers and provides parity in feature descriptions and CLI examples. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In some sections, Windows is mentioned before Linux (e.g., 'Windows and Linux'), and PowerShell is presented alongside CLI, which is more cross-platform. All examples are available for both platforms, but PowerShell is not natively available on most Linux systems.
Recommendations
- Emphasize Azure CLI as the primary cross-platform tool for managing extensions, and clarify that PowerShell is optional for Linux users.
- Consider listing Linux and Windows in alternating order or using 'Linux and Windows' where appropriate.
- Add a note clarifying that Azure PowerShell is available on Linux via PowerShell Core, but Azure CLI is the recommended cross-platform approach.
- Ensure that all screenshots and portal instructions are generic and not Windows-specific.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens, but the Windows/PowerShell example is presented first and in more detail, including a screenshot. The Linux example is present and functional, but the ordering and emphasis slightly favor Windows. The 'Related content' section lists PowerShell before Azure CLI, which is more cross-platform.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which comes first to avoid implicit prioritization.
- Include equal detail and screenshots for both Windows and Linux workflows.
- In 'Related content', list Azure CLI before PowerShell, or clarify CLI is cross-platform.
- Explicitly state that both Windows and Linux are fully supported and provide parity in instructions.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in the 'Run the script' and 'Retry command' sections. The Windows-specific note about PowerShell ISE is included, but there is no equivalent Linux-specific guidance. Both platforms are supported, and Linux parity is generally good.
Recommendations
- Present Windows and Linux instructions in parallel or alternate the order to avoid always showing Windows first.
- Add Linux-specific notes or troubleshooting tips if relevant (e.g., shell compatibility, permissions).
- Explicitly mention macOS support if the Bash script works on macOS, or clarify if it does not.
- Ensure screenshots and UI instructions are platform-neutral or clarify any platform-specific differences.
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
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle indications of Windows bias. PowerShell is mentioned as a primary automation tool alongside Azure CLI and SDKs, and some links (such as Azure Automation and AVS onboarding) default to Windows-specific tabs or examples. Windows features and tools are sometimes referenced before Linux equivalents, though Linux support is acknowledged throughout. No critical sections are Windows-only, and Linux users can complete all tasks, but Windows examples and terminology are slightly more prominent.
Recommendations
- Ensure that automation examples and links reference both PowerShell and Bash/CLI equally, or provide Linux/macOS-specific guidance where relevant.
- When listing supported tools and SDKs, avoid placing Windows-specific tools (e.g., PowerShell) before cross-platform options (e.g., Azure CLI, REST API).
- For links that default to Windows tabs (such as AVS onboarding or Azure Automation), add explicit Linux tabs or examples, or clarify Linux support.
- Consider adding a section or callout summarizing Linux/macOS parity and supported scenarios for non-Windows users.
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere and includes both Windows and Linux-related updates. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but Linux is also referenced (Arc agent installation on Linux via SSH). However, in several places, Windows tools and technologies (e.g., System Center Configuration Manager, Group Policy, Azure PowerShell) are mentioned before or more prominently than their Linux equivalents (e.g., Ansible). Windows examples and tools tend to be listed first, and Windows-specific features are sometimes highlighted without equal Linux coverage.
Recommendations
- When listing tools or methods for agent installation at scale, ensure Linux-native options (e.g., Ansible, shell scripts) are given equal prominence and not always listed last.
- For features that apply to both Windows and Linux VMs, clarify applicability and provide examples for both platforms.
- Where PowerShell is mentioned, also reference Bash/Azure CLI equivalents if available.
- Review the order of tool listings to avoid always putting Windows tools first.
- Add links or references to Linux-specific documentation where relevant.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, which may subtly reinforce Windows as a primary platform. No Windows-specific tools or patterns are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or Windows-only tools mentioned.
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 beginning clarifying that all Azure CLI commands are cross-platform and Bash examples are intended for Linux/macOS users.
- Ensure screenshots and portal instructions are neutral and do not reference Windows-specific UI elements.
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 command-line tasks, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash, and some PowerShell-specific nuances (like base64 encoding) are explained. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks without friction. Minor bias exists in the ordering and the presence of PowerShell-specific explanations.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
- Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- Ensure that any PowerShell-specific explanations (e.g., base64 encoding) are matched with Bash/Linux equivalents, which is already done in most cases.
- If possible, provide a brief summary at the start clarifying cross-platform support.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash (Linux/macOS) tab is presented first. All commands use the cross-platform Azure CLI, and there are no Windows-specific tools or patterns. No critical steps are Windows-only, and Linux/macOS users are fully supported.
Recommendations
- Maintain the current structure, as Bash examples are shown first and all commands are cross-platform.
- Ensure that any future additions (such as troubleshooting or advanced scenarios) continue to provide parity for Linux/macOS users.
- Consider clarifying in the introduction that all examples are cross-platform unless otherwise noted, to reassure non-Windows users.
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 cross-platform parity. However, in each section, Bash examples are consistently shown first, followed by PowerShell. There are no Windows-only tools, patterns, or references, and Linux/macOS users can fully follow the tutorial without friction.
Recommendations
- Maintain the current structure, as both Bash and PowerShell examples are provided.
- Consider alternating the order of Bash and PowerShell examples in some sections to avoid implicit bias toward Bash users.
- Explicitly state at the beginning that both Linux/macOS (Bash) and Windows (PowerShell) are fully supported, to reassure users.
- If possible, add a brief note clarifying that all commands are cross-platform unless otherwise specified.
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 examples are always shown after Bash. There is no evidence of Windows-only tools or patterns, and all commands use cross-platform Azure CLI and Helm. However, the PowerShell examples are present throughout, which may slightly favor Windows users, but Linux/macOS parity is maintained.
Recommendations
- Consider explicitly stating that all commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add a note clarifying that PowerShell Core is available on Linux and macOS, so PowerShell examples are not Windows-exclusive.
- If possible, provide a generic shell example or clarify that Bash and PowerShell are both supported on all platforms.
- Ensure that Bash and PowerShell tabs are equally prominent and clarify that users can choose either based on their environment.
Azure Arc
Simplify Network Configuration Requirements with Azure Arc Gateway
...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Windows and Linux examples for key tasks, but Windows/PowerShell examples are often presented first or with more detail. PowerShell commands are included alongside Azure CLI, and some instructions reference Windows-specific paths or tools (e.g., PowerShell, Windows Admin Center) before their Linux equivalents. However, Linux is supported throughout, and Linux-specific instructions (such as log file locations) are present. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Explicitly mention macOS support and provide macOS-specific instructions where relevant.
- Ensure parity in detail and clarity between Windows and Linux instructions (e.g., log file locations, script examples).
- Where possible, use cross-platform CLI examples as the default, and reference PowerShell only as an alternative.
- Clarify when a tool or path is Windows-only and provide the Linux/macOS equivalent immediately.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows and Linux VM extension tables separately, but the Windows extensions section appears first and is more extensive. The deployment methods (Azure portal, CLI, PowerShell, ARM templates) are listed without bias, and Linux-specific extensions and partner tools are well represented. There are no PowerShell-heavy examples or exclusive Windows tools mentioned. However, the ordering of Windows before Linux and the longer Windows extension table may subtly reinforce Windows as the primary platform.
Recommendations
- Consider presenting Windows and Linux extension tables side-by-side or in alphabetical order to avoid implicit prioritization.
- Ensure parity in extension descriptions and links for both platforms.
- If possible, balance the depth of information between Windows and Linux sections.
- Explicitly state that both Windows and Linux are equally supported at the start of the Extensions section.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed explanation and output imagery. The Linux/Bash example follows, but is slightly less detailed. References to Windows tools (PowerShell) appear before Linux equivalents (Bash, SSH), and related content links mention PowerShell before Azure CLI.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to emphasize parity.
- Provide equally detailed explanations and output imagery for both Windows and Linux examples.
- In related content, list Azure CLI and Bash examples before or alongside PowerShell.
- Ensure that prerequisite instructions for Linux are as clear and prominent as those for Windows.
- Explicitly state that both Windows and Linux are fully supported and provide links to Linux-specific tutorials where relevant.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, ensuring parity for both platforms. However, Windows instructions and notes are presented before Linux instructions in the 'Run the script' and 'Retry command' sections, which is a minor form of bias ('windows_first'). No critical functionality is missing for Linux users, and all necessary steps are covered for both OSes.
Recommendations
- Present Windows and Linux instructions in parallel (side-by-side) or alternate the order in sections to avoid always showing Windows first.
- Add explicit mention that macOS users can follow the Linux (Bash) instructions if applicable.
- Ensure screenshots and UI references are OS-neutral or clarify if any steps differ for Linux/macOS users.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown immediately after Bash, and in some sections, the PowerShell tab is labeled as a peer to Bash rather than as a Windows-specific alternative. There are no Windows-only tools or patterns, and all instructions are based on the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, but the ordering of PowerShell examples may subtly prioritize Windows users.
Recommendations
- Clarify that Bash examples are for Linux/macOS and PowerShell for Windows, possibly by labeling the tabs as 'Linux/macOS (Bash)' and 'Windows (PowerShell)'.
- Ensure Bash examples are shown first in all sections to reinforce Linux/macOS parity.
- Consider adding a brief note at the start indicating that all CLI commands are cross-platform and can be run on any OS with Azure CLI installed.
- If applicable, mention that PowerShell Core is available on Linux/macOS, but Bash is the default shell for those platforms.
Azure Arc
Service Groups for Workload Orchestration
...cles/azure-arc/workload-orchestration/service-group.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all command-line operations, ensuring parity for Linux/macOS and Windows users. However, in each section, PowerShell examples are consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools, patterns, or exclusive Windows instructions are present; all commands use the cross-platform Azure CLI. There are no missing Linux examples or Windows-only tools.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state that both Bash and PowerShell examples are provided for cross-platform compatibility.
- Ensure that any troubleshooting or advanced sections also include Bash and PowerShell parity if command-line instructions are needed.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd) and marks these blocks as 'powershell', which may imply Windows-centric usage. There are no explicit Linux/macOS shell examples, and PowerShell is used as the default for command blocks, even though the commands themselves are cross-platform. The documentation does not mention Linux tools or shell patterns, nor does it clarify that the examples work equally well on Linux/macOS.
Recommendations
- Provide explicit Linux/macOS shell examples (e.g., bash) alongside PowerShell examples.
- Clarify that the kubectl and sqlcmd commands are cross-platform and can be run from any OS with the appropriate tools installed.
- Avoid labeling command blocks as 'powershell' when the commands are not PowerShell-specific.
- Mention prerequisites for Linux/macOS users, such as installing mssql-tools and kubectl.
- Consider showing bash syntax first or equally with PowerShell to avoid Windows-first bias.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is listed before sqlcmd, and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The overall guidance and examples are slightly Windows-centric, but Linux users can complete the task using sqlcmd.
Recommendations
- Mention cross-platform SQL client tools (e.g., Azure Data Studio, DBeaver, Squirrel SQL) alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using GUI tools, not just sqlcmd.
- Ensure that Linux/macOS instructions and examples are presented with equal prominence to Windows/SSMS examples.
- Clarify that sqlcmd works on both Windows and Linux, and provide installation links for both platforms.