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 1701-1725 of 2334 flagged pages
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 in Bash, but the May 2025 release section includes PowerShell syntax for CLI commands, which may suggest a Windows-first bias. There are no explicit Linux/macOS examples or mentions of Linux-specific tools or patterns. However, the Azure CLI is cross-platform, and most examples are generic. The bias is minor and limited to occasional use of PowerShell syntax.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or clarify that Azure CLI commands work identically across platforms.
- Add explicit Linux/macOS example blocks where PowerShell syntax is shown.
- Mention cross-platform compatibility of Azure CLI in the documentation introduction.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Continue to provide both Bash and PowerShell examples for parity.
- Consider alternating the order of Bash and PowerShell tabs in future documentation, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that all CLI commands are cross-platform and can be run on any OS with Azure CLI and Helm installed.
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 consistently presented after Bash. There are no Windows-only tools or patterns used, and all commands are cross-platform (using the Azure CLI and Helm). However, the presence of PowerShell examples may suggest a slight Windows bias, especially since PowerShell is not the default shell on Linux/macOS, but this is mitigated by Bash examples being present and shown first.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for Linux/macOS users.
- Consider clarifying that PowerShell examples are for users who prefer PowerShell, which is available cross-platform, but Bash is recommended for Linux/macOS.
- Explicitly state that all commands are intended to work on both Linux and Windows, and that Azure CLI and Helm are cross-platform tools.
- Optionally, add a note at the top indicating that Bash is the recommended shell for Linux/macOS users, and PowerShell is available for those who prefer it.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows links are often listed first, and there are several Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl, and referencing PowerShell's curl alias). Linux installation instructions are less explicit (e.g., 'install curl package' without a link), and Linux/macOS examples are not always equally detailed. This creates minor friction for Linux/macOS users.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide explicit installation instructions or links for Linux/macOS tools (e.g., for curl, link to official Linux/macOS installation guides).
- Clarify PowerShell-specific notes as Windows-only, and provide equivalent Linux/macOS guidance where relevant.
- Ensure all tool installation instructions are equally detailed for all 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 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 and in greater detail, including a screenshot, which may subtly prioritize Windows users. The 'Related content' section also mentions PowerShell before Azure CLI, which is more cross-platform.
Recommendations
- Present Windows and Linux examples in parallel or alternate which is shown first to avoid implicit prioritization.
- Ensure screenshots and example outputs are provided for both Windows and Linux, not just Windows.
- In 'Related content', mention Azure CLI before or alongside PowerShell to emphasize cross-platform tooling.
- Consider providing additional context or troubleshooting tips for Linux users, such as common permission issues.
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 an example is provided for both Linux and Windows, SSMS is listed first and no Linux-native graphical client (such as Azure Data Studio or DBeaver) is mentioned. The documentation does not provide parity in client tool recommendations or examples for Linux/macOS users.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS.
- Provide explicit examples for connecting using sqlcmd on Linux/macOS, including any authentication or encoding nuances.
- List Linux/macOS tools and examples before or alongside Windows tools, not after.
- Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
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 when creating Kubernetes secrets. The Linux example (using 'base64') is given first, followed by Windows-specific instructions using 'certutil' and 'findstr'. There is a minor bias in mentioning Windows tools and patterns, but Linux parity is maintained throughout the guide. All critical steps are covered for both platforms.
Recommendations
- Explicitly mention macOS compatibility for the 'base64' command, as it works similarly to Linux.
- Provide PowerShell alternatives for Windows users (e.g., using '[Convert]::ToBase64String') to increase accessibility.
- Clarify that all Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, and macOS.
- Consider grouping Linux/macOS and Windows instructions separately for clarity.
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 provides parity between Windows and Linux for most aspects of Azure Arc-enabled server connectivity. However, Windows-specific tools (Windows Admin Center) and resources are mentioned before their Linux equivalents, and Windows installation/download URLs are listed first in tables. Some sections, such as cryptographic protocol configuration, focus on Windows-specific guidance and troubleshooting, with Linux guidance being less detailed or referenced externally. Overall, Linux users can complete the tasks, but Windows is subtly prioritized.
Recommendations
- Present Windows and Linux examples/resources side-by-side or in parallel, rather than listing Windows first.
- Expand Linux-specific guidance, such as TLS configuration and troubleshooting, to match the detail provided for Windows.
- Where Windows tools (e.g., Windows Admin Center) are mentioned, clarify Linux alternatives or note their applicability.
- Ensure tables and lists alternate or group Windows and Linux resources equally.
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 a link that defaults to Windows instructions and mentions Azure CLI x64/32-bit requirements, but does not specify Linux/macOS compatibility or provide explicit guidance for those platforms. No Linux/macOS-specific examples or clarifications are given, and the management machine requirements section links to Windows installation first. However, the overall content is not Windows-specific and the Azure CLI is cross-platform.
Recommendations
- Add explicit mention that Azure CLI is supported on Linux and macOS, and provide links to Linux/macOS installation instructions alongside the Windows link.
- Clarify that the management machine can be Windows, Linux, or macOS, and specify any platform-specific requirements if applicable.
- Include example commands or screenshots for Linux/macOS where relevant, especially for CLI usage.
- Ensure parity in documentation structure so Linux/macOS users are not left to infer compatibility.
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 tools and services, such as 'time.windows.com' for NTP and 'sts.windows.net' for Custom Location. Windows NTP is mentioned explicitly, and Windows-related endpoints (e.g., 'login.windows.net', 'servicebus.windows.net') are listed. However, Linux-specific endpoints and tools are also referenced, such as 'packages.microsoft.com' for Linux installation packages and 'linuxgeneva-microsoft.azurecr.io' for log collection. The examples and instructions do not exclusively focus on Windows, but Windows endpoints and terminology appear first or more prominently in some cases.
Recommendations
- Clarify that NTP can use either Windows or Linux NTP servers, and provide Linux NTP server examples (e.g., 'pool.ntp.org').
- Ensure parity in endpoint descriptions by mentioning Linux equivalents where relevant (e.g., for authentication or time sync).
- Review the order of endpoint listings to avoid consistently placing Windows-specific endpoints first unless required by technical order.
- Add explicit notes for cross-platform compatibility, especially for management machines that may run Linux or macOS.
- Where possible, provide Linux/macOS command-line examples or references alongside Windows/PowerShell instructions.
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
Windows Tools
Summary
The documentation generally provides parity between Windows and Linux, offering error codes, exit codes, and troubleshooting steps for both platforms. However, there is a mild Windows bias: Windows log file paths and PowerShell command syntax are presented before Linux equivalents in some sections, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced. Linux examples are present and clear, but Windows examples are shown first in the verbose logging section, and Windows-specific troubleshooting details (e.g., PowerShell version requirements, log file locations) are mentioned before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Where possible, present Windows and Linux commands side-by-side for easier comparison.
- Ensure Linux troubleshooting steps and log file locations are given equal prominence and detail.
- Explicitly mention Linux prerequisites and permissions in all relevant sections, not just in notes.
- Consider adding a summary table of key paths and commands for both platforms at the top of the troubleshooting section.
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
Windows Tools
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there are subtle biases: Windows/PowerShell are mentioned first in several places (e.g., runbooks, onboarding tabs), and some links default to Windows-specific tabs or examples. Azure Automation is described with a PowerShell-first perspective, and some linked guides and features (like Windows Server management, ESUs) are Windows-centric, though this is expected for those features. Linux is supported and mentioned, but often as a secondary consideration.
Recommendations
- When referencing automation (e.g., Azure Automation runbooks), explicitly mention both PowerShell and Bash/Python equally, and provide links/examples for both platforms.
- Where documentation links default to Windows tabs or examples, add parallel links or clarify Linux/macOS support.
- In lists of supported tools or interfaces (e.g., CLI, PowerShell, SDKs), avoid always listing PowerShell before CLI or SDKs; alternate order or clarify cross-platform parity.
- For configuration and monitoring features, ensure Linux-specific capabilities and limitations are clearly documented alongside Windows.
- Add more explicit Linux/macOS examples or callouts where relevant, especially in onboarding and automation scenarios.
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 'Recovering from failed deployments' sections. There are minor Windows-first ordering and a PowerShell-specific troubleshooting note, but Linux parity is maintained throughout.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid Windows-first bias.
- Add any Linux-specific troubleshooting notes if relevant (e.g., shell compatibility, permissions).
- Ensure screenshots and UI references are OS-neutral or clarify if they are Windows-specific.
- Explicitly mention macOS support if the Bash script works on macOS, or clarify its limitations.
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 provides a chronological list of new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or explicitly mention both Windows and Linux, there are minor signs of Windows bias: Windows VM customization is mentioned before Linux, Windows Server Management is highlighted, and Windows tools like Azure PowerShell are listed before Linux equivalents (Azure CLI). However, Linux support is also referenced (e.g., Arc agent installation on Linux via SSH, Ansible playbook), and most features are not OS-specific.
Recommendations
- Ensure Linux and Windows examples are presented together or alternate their order.
- When listing tools, consider mentioning cross-platform tools (Azure CLI, Ansible) before Windows-specific ones (PowerShell, Group Policy).
- Add explicit Linux/macOS guidance where only Windows tools are referenced (e.g., System Center Configuration Manager, Group Policy).
- Highlight Linux-specific features or improvements when 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, rather than alternating or giving equal prominence. There are no Windows-only tools or patterns, and all instructions use the Azure CLI, which is cross-platform. No Linux/macOS-specific examples or troubleshooting are missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in each section, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples are intended for Linux/macOS users.
- If relevant, provide troubleshooting tips for Linux/macOS environments (e.g., shell quoting, file path differences).
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides release notes for Azure Arc Workload Orchestration, with CLI examples predominantly using Bash syntax. However, in the May 2025 release section, PowerShell syntax is used for CLI examples, which may suggest a Windows-first bias. No Windows-specific tools or patterns are mentioned, and Linux equivalents are generally present via Bash examples elsewhere. The overall impact is minor, as the Azure CLI is cross-platform and the examples are mostly generic.
Recommendations
- Ensure all CLI examples are provided in both Bash and PowerShell syntax, or clarify that the Azure CLI commands work identically across Windows, Linux, and macOS.
- Where PowerShell syntax is used, add a Bash equivalent for Linux/macOS users.
- Consider standardizing CLI examples to Bash unless the feature is Windows-specific, or provide both syntaxes side-by-side.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first. There are no Windows-specific tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Linux examples are missing, and there is no exclusive mention of Windows tools.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note clarifying that Bash examples are intended for Linux/macOS environments and PowerShell for Windows, to help users quickly identify which section is relevant.
- Ensure parity in variable naming and file path conventions between Bash and PowerShell examples (e.g., use forward slashes in Bash, backslashes in PowerShell).
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 examples, which is a minor 'windows_first' bias. No Windows-exclusive tools or patterns are used, and all commands are cross-platform (Azure CLI, Helm).
Recommendations
- Continue to provide both Bash and PowerShell examples for all steps.
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that both are equally supported.
- Add a note clarifying that all examples are cross-platform and can be run on Linux, macOS, or Windows (with Bash or PowerShell).
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, ensuring cross-platform parity. However, PowerShell examples are present throughout, which may be unnecessary for Linux/macOS users, and in some sections, PowerShell examples are shown immediately after Bash, potentially giving Windows users slightly more prominence. No Windows-specific tools or patterns are used, and Linux examples are not missing. The Azure CLI and Helm are used, both of which are cross-platform.
Recommendations
- Consider clarifying that PowerShell examples are primarily for Windows users, while Bash is for Linux/macOS.
- If possible, add a note at the top of each code section indicating which OS the example is intended for.
- Ensure Bash examples are always shown first, as is currently the case.
- Optionally, provide a single cross-platform example (Bash) for steps where PowerShell does not add meaningful value.
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
Powershell Heavy
Windows Tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere, with some bias toward Windows. Windows-specific features (e.g., customizing guest OS settings for Windows VMs, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are mentioned, but these are not flagged as bias due to their inherent Windows focus. However, in sections describing tooling, Azure PowerShell is listed alongside Azure CLI and REST APIs, and Windows tools (System Center Configuration Manager, Group Policy) are mentioned before Linux equivalents (Ansible). PowerShell is referenced as a management option, and Windows-centric tools are listed first in out-of-band agent installation methods.
Recommendations
- When listing management tools, alternate the order so Linux tools (e.g., Ansible) are not always last.
- Provide explicit Linux/macOS command examples (e.g., Bash, SSH) where PowerShell is referenced.
- Clarify which features are cross-platform and which are Windows-only to help Linux/macOS users quickly identify relevant content.
- Include links to Linux-focused documentation or examples where possible.
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, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are mentioned, and Linux examples are not missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
- Explicitly state that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows, to clarify cross-platform applicability.
- If possible, provide a brief note about using Azure CLI in both environments, highlighting any OS-specific nuances.
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 throughout, but PowerShell examples are consistently shown after Bash examples. There are no Windows-exclusive tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Windows-specific tools or terminology are prioritized. The only minor bias is that Bash (Linux/macOS) examples are always shown first, with PowerShell (Windows) examples following.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or clarify that Bash is shown first for consistency but both are equally supported.
- Explicitly state at the top that all commands are cross-platform and that both Bash and PowerShell are supported.
- If possible, provide a note about how to run PowerShell on Linux/macOS for users who prefer it.
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 is a minor 'windows_first' bias. No Windows-specific tools or patterns are mentioned exclusively, and Linux examples are not missing.
Recommendations
- Maintain the current parity of examples for both Bash and PowerShell.
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
- If possible, add a note clarifying that all commands are cross-platform via Azure CLI, and users should select their preferred shell.
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 presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering, but no critical bias in content or functionality.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that both are equally supported.
- Ensure that any referenced tooling (e.g., az, helm) is cross-platform and clarify installation instructions for Linux/macOS if not already covered elsewhere.
- Add a note confirming that all steps are fully supported on Linux/macOS and Windows, to reassure users.