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 2126-2150 of 2334 flagged pages
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 instructions for base64 encoding files, but the Linux example is presented first and is more concise. The Windows section uses certutil and findstr, which are Windows-specific tools, and requires manual steps to remove headers. There is no PowerShell bias, and all other examples (openssl, Azure CLI, kubectl) are cross-platform. The bias is minor and limited to the base64 encoding step.
Recommendations
- Add PowerShell examples for base64 encoding on Windows, as PowerShell is available by default and more modern than certutil.
- Clarify that certutil is available only on certain Windows editions and provide alternatives for Windows users (e.g., PowerShell).
- Consider presenting Linux and Windows instructions side-by-side for parity.
- Explicitly mention that Azure CLI and kubectl commands are cross-platform and provide links to installation instructions for Windows, Linux, and macOS.
Create Pull Request
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, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and Linux-specific tools/examples are not missing. No critical Linux functionality is omitted.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to emphasize equal support.
- Explicitly state that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Add a brief introductory note highlighting Linux support to reinforce parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell, which is a minor form of ordering bias ('windows_first' or 'linux_first'). No evidence of Windows-only tools, missing Linux examples, or exclusive Windows patterns is found.
Recommendations
- Maintain the current parity of examples for both Bash and PowerShell.
- Consider alternating the order of Bash and PowerShell tabs in different sections, or clarify that Bash is shown first for consistency, not preference.
- Explicitly state that both Linux/macOS and Windows environments are supported, if not already clear.
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 examples, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider clarifying that Bash examples are suitable for Linux/macOS and Windows users using WSL or Git Bash, while PowerShell is native to Windows.
- If possible, add a note at the top explaining which environments each example is intended for.
- Ensure that any future updates continue to provide equivalent examples for both platforms.
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 first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. 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, DBeaver, or Squirrel SQL alongside SSMS.
- Provide example connection instructions for at least one Linux-native GUI client.
- Consider listing sqlcmd (which is cross-platform) before SSMS, or equally, to avoid Windows-first bias.
- Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides installation instructions for client tools across platforms, but there is a noticeable Windows bias. Windows installation links are listed first in several places, and PowerShell/cmd.exe usage is specifically called out for Windows users. The explanation about 'curl' in PowerShell is Windows-centric, and Linux installation instructions for 'curl' are less explicit. While Linux and macOS are mentioned, Windows tools and patterns are prioritized or described in more detail.
Recommendations
- List Linux and macOS installation instructions before or alongside Windows, not after.
- Provide explicit Linux installation instructions for 'curl' (e.g., 'sudo apt install curl') rather than just 'install curl package'.
- Clarify PowerShell-specific notes as Windows-only, and provide equivalent Linux/macOS guidance where relevant.
- Ensure examples and explanations are balanced across platforms, not favoring Windows terminology or tools.
- Add macOS installation instructions for 'curl' if missing.
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 and tools (e.g., 'time.windows.com', 'sts.windows.net', 'servicebus.windows.net'), and Windows NTP is mentioned as the default in the context of Hyper-V. Windows-related endpoints are listed alongside general endpoints, sometimes before Linux equivalents. However, Linux-specific endpoints (e.g., 'packages.microsoft.com', 'linuxgeneva-microsoft.azurecr.io') are also included, and SSH is referenced as a connectivity requirement, which is cross-platform. No PowerShell-only examples or Windows-only commands are present.
Recommendations
- Clarify when Windows-specific endpoints (e.g., 'time.windows.com') are only required for Windows deployments, and provide Linux alternatives (e.g., 'ntp.ubuntu.com') if applicable.
- Where Windows tools or services are mentioned (such as NTP), explicitly note Linux equivalents or provide guidance for Linux users.
- Ensure that Linux-related endpoints and requirements are given equal prominence and explanation as Windows ones.
- Consider grouping Windows-specific and Linux-specific requirements separately for clarity.
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 using links and examples that default to Windows (e.g., 'Azure CLI x64' links to the Windows install page). There are no explicit Linux/macOS installation instructions or examples, and the management machine requirements do not clarify cross-platform compatibility. However, the overall content is generic and does not rely on Windows-only tools or patterns.
Recommendations
- Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside Windows.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide cross-platform examples where relevant.
- Ensure CLI commands and file paths are shown in a cross-platform manner (e.g., using generic paths or showing both Windows and Linux/macOS examples).
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
Powershell Heavy
Windows Tools
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 and version numbers are consistently listed first, and Windows-specific installer instructions (e.g., PowerShell, msiexec, GUI) are emphasized. Known issues and troubleshooting focus on Windows installer behaviors, with no equivalent Linux guidance. Windows tools and patterns (e.g., PowerShell, msiexec, GUI) are mentioned without Linux alternatives (such as shell commands or package managers).
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side to avoid implicit prioritization.
- Provide Linux-specific troubleshooting guidance and known issues, such as common installer problems or commands for resolving issues.
- When referencing Windows tools (e.g., PowerShell, msiexec), also mention Linux equivalents (e.g., bash, rpm, dpkg, systemctl) where relevant.
- Ensure that any instructions or recommendations for installation, upgrades, or configuration are mirrored for Linux users, including command-line examples.
- Add a section summarizing Linux-specific improvements, known issues, and workarounds, similar to the Windows installer guidance.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides parity for both Windows and Linux platforms, with clear sections and examples for each. However, there is a mild Windows bias: Windows instructions and tools (such as PowerShell, Group Policy, Microsoft Update, and Control Panel) are often described in greater detail and appear first in several sections. The cleanup script for removing stale resources is only provided in PowerShell, with no Linux shell equivalent. References to Windows-specific tools (e.g., Msiexec, Registry Editor) are prominent, while Linux instructions are more concise and rely on standard package managers.
Recommendations
- Provide Linux shell (bash) equivalents for resource cleanup scripts, or at least mention how Linux users can achieve similar results using Azure CLI.
- Ensure Linux examples are given equal prominence and detail as Windows examples, especially for advanced tasks (e.g., scripting, automation).
- Where possible, avoid listing Windows instructions first unless there is a clear reason (e.g., user base statistics). Consider alternating or grouping by OS.
- Expand Linux sections to include troubleshooting tips and automation methods similar to those provided for Windows.
- Mention cross-platform tools (Azure CLI) as the primary method where applicable, and clarify PowerShell is optional for Windows users.
Azure Arc
CLI reference for `azcmagent connect`
...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation gives Windows-specific authentication options (interactive browser login and certificate store usage) before Linux equivalents, and references Windows tools (PowerShell's Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods are described, and most examples are cross-platform.
Recommendations
- Reorder authentication options so Linux-default methods (device code, Azure CLI) are presented before Windows-only options.
- For access token acquisition, mention Linux/macOS alternatives (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
- Clarify which authentication options are cross-platform and which are Windows-only, ideally in a table or with clear labels.
- Add explicit Linux/macOS example commands where Windows-specific instructions are given (e.g., certificate store usage).
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 with managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and examples are presented first, and PowerShell is referenced more prominently in related content. There is minor Windows-first ordering and emphasis, but Linux parity is generally maintained.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Ensure related content links reference Azure CLI and Bash examples equally alongside PowerShell.
- Explicitly state that both Windows and Linux are supported at the start of technical sections.
- Where possible, provide cross-platform scripting guidance (e.g., Python, .NET Core) in addition to OS-specific shell examples.
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 Windows examples and references are often presented first. PowerShell/Windows-specific command syntax is shown before Linux equivalents, and Windows file paths and tools (e.g., `%ProgramData%`, PowerShell syntax) are mentioned more prominently. Linux examples are present but sometimes secondary.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Provide Linux-specific troubleshooting steps and file paths with equal prominence to Windows.
- Where possible, use cross-platform command syntax or clarify differences for each OS.
- Ensure Linux log file locations and commands are referenced alongside Windows equivalents in all sections.
- Add explicit notes when remediation steps differ between Windows and Linux (e.g., service management, file permissions).
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, mentioning both Windows and Linux support in several places. However, there is a slight Windows bias: Windows tools (PowerShell) are mentioned before Linux equivalents, and some links and examples default to Windows tabs or Windows-specific scenarios. PowerShell is referenced as a primary automation tool, while Bash or Linux shell examples are not explicitly mentioned. The 'next steps' section and some linked guides also default to Windows-focused instructions.
Recommendations
- Explicitly mention Bash or Linux shell options alongside PowerShell in automation sections.
- Ensure linked guides and quickstarts provide Linux/macOS instructions or examples where applicable.
- Where possible, present Windows and Linux options equally (e.g., 'PowerShell or Bash' instead of just 'PowerShell').
- Review links and tabs to ensure Linux parity (e.g., not defaulting to Windows tabs in linked documentation).
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 appears before Bash. There are no Windows-specific tools or patterns used, and all commands are based on the Azure CLI, which is cross-platform. No Linux-specific examples (e.g., zsh, fish shell) are missing, but the documentation does not explicitly mention macOS compatibility. The only minor bias is the ordering of PowerShell and Bash examples, with PowerShell sometimes appearing first.
Recommendations
- Ensure Bash examples are always shown before PowerShell to reinforce Linux/macOS parity.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding a note about Azure CLI compatibility across platforms.
- Optionally, provide a generic shell example (sh/zsh/fish) or clarify that Bash commands work on macOS as well.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell examples are given equal prominence and detail as Bash, and the tab order presents Bash first, then PowerShell. There is no evidence of Windows-only tools or patterns, and all commands use the cross-platform Azure CLI. However, the inclusion of PowerShell examples may suggest a slight Windows bias, as Linux/macOS users are less likely to use PowerShell. No Linux-specific tools or shell scripting patterns are highlighted.
Recommendations
- Clarify that PowerShell examples are for users who prefer PowerShell, and Bash is recommended for Linux/macOS.
- Consider adding a note that Azure CLI commands work identically on Linux, macOS, and Windows.
- If possible, provide a third tab for macOS/Linux terminal usage, or explicitly mention that Bash examples are suitable for both Linux and macOS.
- Ensure that any file path or environment variable usage is compatible with Linux/macOS conventions.
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 every command, ensuring parity for Linux and Windows users. However, PowerShell examples are consistently shown immediately after Bash, which may indicate a minor 'windows_first' bias in ordering, but no critical bias is present.
Recommendations
- Consider alternating the order of Bash and PowerShell examples or clarifying that Bash is suitable for Linux/macOS and PowerShell for Windows.
- Add a brief note at the start explaining which shell is recommended for each OS.
- Ensure that all CLI commands are tested and work identically in both Bash and PowerShell environments.
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 operation, 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-specific tools, patterns, or terminology are used, and all commands are cross-platform (Azure CLI). There are no missing Linux examples or Windows-only instructions.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note clarifying that Azure CLI commands work on all platforms and that Bash examples are suitable for Linux/macOS users.
- Ensure any future additions (e.g., troubleshooting, file editing) include Linux/macOS equivalents if Windows-specific tools are mentioned.
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 each section, Bash examples are consistently presented before PowerShell, which is a minor 'windows_first' bias in ordering. No Windows-only tools, patterns, or missing Linux examples are present. All commands use cross-platform Azure CLI and Helm tools.
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 Bash is shown first for consistency, not platform preference.
- Ensure that any future additions maintain parity and do not introduce Windows-only tools or instructions unless the feature is Windows-specific.
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. In some sections, PowerShell examples are shown immediately after Bash, and the PowerShell syntax is used for variable assignment and command chaining. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. However, the presence of PowerShell examples may suggest a slight Windows bias, as Linux/macOS users are unlikely to use PowerShell.
Recommendations
- Consider making Bash the default or primary example, with PowerShell as an optional tab for Windows users.
- Clarify that Bash examples are recommended for Linux/macOS users, and PowerShell for Windows users.
- Ensure that Bash examples are shown first in all code blocks.
- Add a note explaining that all commands are cross-platform and can be run in Bash on Windows (WSL) or in macOS/Linux terminals.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides cross-platform guidance for Azure Arc-enabled Kubernetes clusters, with most examples and instructions using Azure CLI and kubectl, which are available on Windows, Linux, and macOS. However, in the section about installing Azure kubelogin, Windows and Mac instructions are mentioned first, and Linux instructions are detailed separately. This is a minor ordering bias, but all necessary Linux information is present. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found.
Recommendations
- When mentioning installation instructions for tools like Azure kubelogin, present Linux, macOS, and Windows options together or in alphabetical order to avoid implicit prioritization.
- Explicitly state that all CLI commands are cross-platform and provide links to platform-specific installation guides for Azure CLI and kubectl.
- Ensure screenshots and portal instructions are not Windows-centric (none detected here, but review for future updates).
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples throughout, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and sometimes the Bash tab is listed first. There are no Windows-specific tools or patterns, and all commands use the cross-platform Azure CLI. No critical steps are Windows-only, and Linux users can complete all tasks. The only minor bias is the ordering of PowerShell and Bash examples, which may subtly favor Windows users by always including PowerShell, but this is mitigated by the presence of Bash examples.
Recommendations
- Ensure Bash and PowerShell examples are equally prominent, perhaps alternating their order or clarifying that Bash is for Linux/macOS and PowerShell for Windows.
- Consider adding a brief note at the top explaining which shell to use for each OS.
- If possible, provide a generic CLI example without shell-specific syntax for universal clarity.
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 every command, but consistently presents Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No critical sections are Windows-only, and all tasks can be completed on Linux/macOS using the Azure CLI.
Recommendations
- Continue to provide both Bash and PowerShell examples for cross-platform parity.
- Consider explicitly stating that all commands are supported on Linux, macOS, and Windows.
- If possible, add a brief note clarifying that Azure CLI works across platforms and that Bash examples are suitable for Linux/macOS users.
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 and links for each. However, Windows extensions are listed first, which may subtly signal prioritization. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are presented neutrally, and partner extensions are shown for both OSes. No critical Linux omissions or Windows-only tools are present.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or explicitly state that both are equally supported.
- Add a brief introductory statement emphasizing Linux parity and support.
- Ensure that linked deployment guides (e.g., Azure CLI, PowerShell) include Linux-specific examples where applicable.