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 1726-1750 of 2334 flagged pages
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 documentation does not provide parity in GUI client recommendations for Linux/macOS users, and the overall tone suggests Windows as the default environment.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
- Provide explicit examples for connecting from Linux/macOS using GUI tools, not just sqlcmd.
- When listing tools, avoid always mentioning Windows-only tools first; alternate or group by platform.
- Clarify that sqlcmd is available on both Windows and Linux, and provide installation guidance if needed.
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
Linux First
Summary
The documentation provides both Linux and Windows methods for base64 encoding files when creating Kubernetes secrets. The Linux example (using 'base64') is presented first, and the Windows example (using 'certutil' and 'findstr') is given immediately after. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and does not show significant Windows bias. However, the Windows-specific tool (certutil) is mentioned, and Windows users are given extra instructions for removing headers, which could be seen as a minor bias.
Recommendations
- Explicitly state that all Azure CLI and kubectl commands work on both Windows and Linux.
- Provide equivalent Linux/macOS commands for removing certificate headers (e.g., 'grep -v CERTIFICATE b64-encoded.txt > updated-b64.txt') alongside the Windows 'findstr' example.
- Clarify that OpenSSL, Azure CLI, and kubectl are cross-platform and provide installation links for Windows, Linux, and macOS.
- Consider grouping Windows and Linux instructions together, or using tabs to switch between OS-specific examples for improved clarity.
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 major tasks, but consistently presents Azure PowerShell (a Windows-centric tool) examples alongside or immediately after Azure CLI. There is no explicit Linux/macOS example or mention of Bash scripting, and PowerShell is presented as an equal alternative, despite its primary association with Windows. However, Azure CLI is cross-platform and the examples use standard environment variables for proxy configuration, which are compatible with Linux/macOS. No Windows-only tools or patterns are used, and Linux users can complete all tasks.
Recommendations
- Explicitly state that Azure CLI commands and environment variable examples are compatible with Linux/macOS.
- Add notes or examples showing Bash shell usage for Linux/macOS users, especially for environment variable setup.
- Clarify that Azure PowerShell can be used cross-platform, but is most familiar to Windows users.
- Consider showing Azure CLI (Linux/macOS-friendly) examples first, or labeling them as recommended for Linux/macOS.
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 for `azcmagent connect` displays mild Windows bias. Windows authentication options (interactive browser login, certificate store usage) are described first and in more detail, with explicit 'Windows only' labeling. Windows-specific tooling (PowerShell's Get-AzAccessToken) is mentioned for access token acquisition, while Linux alternatives are not referenced. However, Linux authentication methods (device code, Azure CLI) are documented and examples are generally cross-platform.
Recommendations
- Reorder authentication options so cross-platform methods (device code, Azure CLI, service principal) appear before Windows-only options.
- When referencing access token acquisition, mention Linux/macOS alternatives (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
- Clarify which examples and flags are cross-platform, and explicitly state Linux/macOS compatibility where relevant.
- Add a brief section or table summarizing authentication methods by OS/platform for quick reference.
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 page lists both Windows and Linux-related endpoints and requirements, but there is a mild bias toward Windows: Windows NTP server ('time.windows.com') is mentioned as the default, and several endpoints (e.g., 'login.windows.net', 'sts.windows.net', 'servicebus.windows.net') use Windows branding. The table includes a Linux-specific endpoint ('linuxgeneva-microsoft.azurecr.io') and references to Linux package sources, but Windows tools and URLs are mentioned first or exclusively in some cases. There are no OS-specific command examples or instructions, so the bias is limited to endpoint naming and notes.
Recommendations
- Clarify that NTP can use Linux NTP servers as well, and provide guidance for Linux environments.
- Where Windows-branded endpoints are mentioned (e.g., 'login.windows.net', 'sts.windows.net'), note if these are required for Linux as well, or provide Linux alternatives if applicable.
- Ensure that any references to default behaviors (such as NTP) include both Windows and Linux defaults.
- If management machines can be Linux, explicitly state so and provide any Linux-specific considerations.
- Review notes and examples for implicit Windows-first language and update 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 by linking to the Windows Azure CLI installation page first and referencing Azure CLI x64/32-bit requirements without clarifying Linux/macOS support. However, it does not provide Windows-only examples or tools, and the Azure CLI is cross-platform. No critical Linux/macOS information is missing, but Linux parity could be improved.
Recommendations
- Explicitly state that Azure CLI is supported on Linux and macOS, not just Windows.
- Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link.
- Clarify that the management machine can be Linux, macOS, or Windows, and note any OS-specific requirements (if any).
- If referencing CLI directory paths, mention typical Linux/macOS paths as well as Windows.
- Add a brief note that all CLI commands and configuration steps apply equally to Linux/macOS unless otherwise specified.
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 (a Windows-centric tool) is consistently included alongside CLI. In several sections, PowerShell examples are shown after CLI, but the CLI syntax uses backticks (`) for line continuation, which is a Windows/PowerShell convention and not standard for Linux shells. There is a minor tendency to mention Windows tools (PowerShell, Windows Admin Center) and Windows-specific scenarios first. However, Linux parity is generally maintained, with explicit Linux instructions for log locations and onboarding, and the Azure CLI is cross-platform.
Recommendations
- Use standard Bash line continuation (\) in CLI examples instead of backticks to improve Linux usability.
- Explicitly state that Azure CLI commands work on Linux/macOS and provide Bash syntax where relevant.
- Consider including Bash shell examples or clarifying that PowerShell is optional for Linux users.
- Where Windows-specific tools (like Windows Admin Center) are mentioned, balance with Linux equivalents or clarify their scope.
- Ensure that Linux log file paths and instructions are as prominent as Windows instructions.
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 an access token, but the Windows/PowerShell example is presented first and in greater detail (including a screenshot). PowerShell is referenced as the primary tool for Windows, while Bash is used for Linux. The prerequisites and related content sections mention both platforms and tools, but PowerShell is listed before Azure CLI in the related content. Overall, Linux parity is maintained, but Windows examples and tools are prioritized.
Recommendations
- Present Windows and Linux examples side-by-side or alternate which platform is shown first.
- Provide equally detailed screenshots and explanations for both Windows and Linux examples.
- List Azure CLI and Bash examples before or alongside PowerShell in related content.
- Ensure that all steps and explanations are equally clear 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 Azure Arc-enabled servers and provides parity in feature descriptions. However, there is a mild Windows bias in the ordering of examples and tools: PowerShell examples are presented after CLI, but the PowerShell section is detailed and tips about installing the module are included. The Azure CLI section does mention Linux shells, but Windows is referenced first in several places. No critical Linux functionality is missing, and all management tasks can be performed via CLI or portal, which are cross-platform.
Recommendations
- Ensure Linux and macOS are mentioned equally alongside Windows in introductory sentences.
- Consider alternating the order of CLI and PowerShell sections, or explicitly state that CLI is cross-platform and PowerShell is primarily for Windows users.
- Add explicit notes or links for macOS users where relevant (e.g., Azure CLI installation).
- Where possible, clarify that PowerShell can be used on Linux and macOS, or provide Bash examples for common tasks.
- Review screenshots and UI instructions to ensure they are not Windows-centric.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM extensions before Linux extensions, with a more extensive and detailed table for Windows. However, Linux extensions are also comprehensively covered, and deployment methods (CLI, PowerShell, portal, templates) are presented neutrally. No critical Windows-only bias is present, and Linux users can complete all tasks described.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side to emphasize parity.
- Ensure that Linux extension descriptions are as detailed as their Windows counterparts, including links to supported OS and additional information.
- Explicitly mention that all deployment methods (CLI, PowerShell, portal, templates) are available for both Windows and Linux, and provide example commands for both platforms where appropriate.
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 covers troubleshooting for both Windows and Linux Azure Connected Machine agent installations. However, there is a mild Windows bias: Windows log file paths and PowerShell-style commands are presented first in the verbose log section, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced before Linux equivalents. Linux examples and paths are included, but Windows is prioritized in ordering and detail.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid always showing Windows first.
- Ensure Linux log file paths and troubleshooting steps are as detailed as Windows.
- Where possible, provide parity in command syntax explanations (e.g., clarify sudo/elevated prompt for Linux as much as for Windows).
- Add explicit notes about Linux-specific troubleshooting (e.g., SELinux/AppArmor, systemd service management) if relevant.
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 provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are several instances where Windows/PowerShell tools and examples are mentioned first or exclusively. PowerShell is listed before other automation tools, and Windows-specific management features are highlighted. While Linux is referenced in some scenarios, Windows tools and terminology are often prioritized, which may create minor friction for Linux/macOS users.
Recommendations
- Ensure Linux examples and tools (such as Bash, Linux CLI, and Linux-specific VM extensions) are mentioned alongside or before Windows/PowerShell equivalents.
- When listing automation options, avoid always putting PowerShell first; alternate order or explicitly mention Linux-friendly tools.
- Add explicit Linux/macOS onboarding and management examples where possible, especially in sections referencing scripts or agent installation.
- Clarify parity between Windows and Linux support for features like Azure Update Manager, Azure Automation, and VM extensions.
- Include links or references to Linux-specific documentation and best practices.
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. There is a minor bias in ordering, but Linux parity is maintained throughout.
Recommendations
- Present Windows and Linux instructions side-by-side or in parallel tabs to avoid implicit prioritization.
- Alternate the order of Windows and Linux instructions in sections to ensure equal visibility.
- Explicitly mention macOS compatibility if the Bash script works on macOS.
- Clarify that both scripts are functionally equivalent and supported.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements (systemd, wget) are listed second and without links. Windows PowerShell is mentioned explicitly, but no Linux shell or command-line examples are provided. The overall guidance is cross-platform, but Windows examples and tools are prioritized.
Recommendations
- List Linux requirements before or alongside Windows requirements to avoid 'Windows-first' ordering.
- Provide download links or references for Linux tools (e.g., systemd, wget) similar to Windows.
- Include example Linux shell commands or scripts for onboarding, not just Windows/PowerShell references.
- Clarify parity in supported OSes and tools, and ensure Linux users have equal guidance for installation and troubleshooting.
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 directly after Bash, which is a minor 'windows_first' bias. No Windows-only tools or patterns are used, and all instructions are cross-platform via the Azure CLI. No Linux/macOS examples are missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash examples apply to Linux/macOS and PowerShell to Windows, to reinforce parity.
- Add a brief note clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that Bash examples are for Linux/macOS users.
- If possible, provide a single CLI example with notes on shell-specific syntax differences, to reduce duplication and emphasize cross-platform support.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
Windows First
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 consistently presented after Bash examples, which may indicate a minor 'windows_first' bias in ordering. No Windows-specific tools or patterns are used exclusively, and Linux/macOS users can complete all tasks without friction.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit bias.
- Explicitly mention that Bash examples are suitable for Linux and macOS users, and PowerShell for Windows users.
- Ensure that any editor instructions (e.g., changing file encoding) include cross-platform guidance (e.g., how to do this on Linux/macOS).
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, ensuring cross-platform parity. However, 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 commands are based on Azure CLI and Kubernetes, which are cross-platform. There are no missing Linux/macOS examples, and no Windows tools are mentioned.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that both are equally supported.
- Add a brief note at the top clarifying that all steps are fully supported on Linux, macOS, and Windows, and that Bash and PowerShell are shown for user convenience.
- If possible, provide guidance for users who may prefer Zsh or other Unix shells, though Bash is generally sufficient.
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 consistently shown after Bash. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI and Helm, which are cross-platform. No Windows-specific tools or terminology are prioritized, and Linux parity is maintained throughout. However, the presence of PowerShell examples may suggest a slight bias toward Windows users, but it is mitigated by Bash examples being present and shown first.
Recommendations
- Continue to provide Bash examples first, as Bash is the default shell for most Linux/macOS users.
- Consider clarifying that Bash examples are suitable for Linux/macOS and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- If possible, add a note at the top explaining which shell to use depending on the user's OS.
- Ensure that any future additions do not introduce Windows-only tools or terminology unless the feature is Windows-specific.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, but PowerShell examples are always shown immediately after Bash, and at times the PowerShell section is more verbose. There is no evidence of Windows-only tools, Windows-specific patterns, or missing Linux/macOS equivalents. The CLI commands are cross-platform and the instructions are equally applicable to Linux/macOS users. However, the presence of PowerShell examples throughout may create a slight impression of Windows prioritization.
Recommendations
- Continue to provide both Bash and PowerShell examples, but consider alternating the order or explicitly stating that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a brief note at the top clarifying that all CLI commands are cross-platform and that Bash is recommended for Linux/macOS users.
- Ensure that any advanced scripting or troubleshooting sections also include Bash equivalents if PowerShell is used.
- If possible, provide a table or summary mapping Bash and PowerShell commands for quick reference.
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 references Azure CLI installation, but in the 'Management machine requirements' section, the link for Azure CLI x64 installation points specifically to the Windows installation page. There are no explicit Linux/macOS examples or instructions, and no mention of Linux/macOS management machines, even though Azure CLI is cross-platform. The CLI commands shown are generic and not Windows-specific, but the documentation implicitly assumes Windows as the primary environment for deployment.
Recommendations
- Add explicit guidance for Linux and macOS management machines, including links to their Azure CLI installation pages.
- Clarify that the management machine can be Windows, Linux, or macOS, and provide any OS-specific requirements or considerations.
- Include example CLI commands for Linux/macOS where relevant, or note that the commands are identical across platforms.
- Ensure that references to CLI installation do not default to Windows unless the feature is Windows-only.
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 via managed identity on Azure Arc-enabled servers. However, Windows/PowerShell instructions and output are presented first, and PowerShell is referenced in the 'Related content' section before Azure CLI. The Linux Bash example is present and complete, but Windows tools and patterns are slightly prioritized.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to ensure equal visibility.
- In 'Related content', list Azure CLI and Bash examples before or alongside PowerShell to improve parity.
- Explicitly mention that both Windows and Linux are fully supported at the top of the article.
- Where possible, provide cross-platform guidance (e.g., using Azure CLI or REST API) before platform-specific tools.
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, but consistently lists Bash examples first. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There is a minor bias in the ordering of examples, but no functional impact for Linux/macOS users.
Recommendations
- Continue to provide both Bash and PowerShell examples for all commands.
- Consider clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, if not already clear.
- Ensure that any referenced scripts (e.g., 'Clean-up script') are available in both Bash and PowerShell versions, or note their compatibility.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While it does mention sqlcmd and provides a cross-platform sqlcmd example, SSMS is emphasized and listed first. No Linux-native GUI tools (such as Azure Data Studio) are mentioned. The documentation does not provide Linux/macOS-specific guidance or troubleshooting, and the overall tone assumes familiarity with Windows-centric tools.
Recommendations
- Mention Azure Data Studio as a cross-platform GUI alternative to SSMS for connecting to SQL Managed Instance.
- Provide explicit examples for connecting from Linux/macOS using sqlcmd, including installation instructions if needed.
- Include troubleshooting tips for Linux/macOS users, such as firewall or network configuration differences.
- List cross-platform tools first or equally, rather than prioritizing Windows-only tools.
- Clarify that SSMS is Windows-only and suggest alternatives for non-Windows 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, but the Windows instructions (using certutil and findstr) are given after the Linux example. The Windows tools are mentioned explicitly, but Linux is presented first and the overall workflow is cross-platform. All other commands (openssl, Azure CLI, kubectl) are platform-agnostic or Linux-oriented.
Recommendations
- Clarify that certutil and findstr are Windows-specific and provide equivalent Linux/macOS commands for removing headers if needed.
- Consider grouping Linux/macOS and Windows instructions more clearly, or providing a table comparing commands for each OS.
- Explicitly mention macOS compatibility where relevant (e.g., base64, openssl).
- Add a note that Azure CLI and kubectl commands work on all platforms.