Azure Arc
926
Total Pages
755
Linux-Friendly Pages
171
Pages with Bias
18.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
432 issues found
Showing 276-300 of 432 flagged pages
Azure Arc
Quickstart for Azure Arc-enabled System Center Virtual Machine Manager (SCVMM)
...t-connect-system-center-virtual-machine-manager-to-arc.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows prerequisites and tools (PowerShell, WinRM, tar.exe, archiveint.dll) are discussed in detail, with installation instructions and troubleshooting focused on Windows. Windows examples and instructions are presented first in most sections, and PowerShell is the primary scripting language. Linux instructions are present but less detailed, and Linux users are warned of slower performance and possible issues, with no troubleshooting or parity guidance. Some Windows-specific tools (WinRM, tar.exe) are mentioned without Linux equivalents or alternatives.
Recommendations
- Provide equally detailed Linux instructions, including troubleshooting steps and prerequisites (e.g., required packages, permissions).
- List Linux and Windows instructions side-by-side or in parallel tabs, rather than Windows-first.
- Mention Linux equivalents for Windows tools (e.g., clarify if WinRM is required on Linux, or what alternatives exist).
- Offer guidance for optimizing script performance on Linux, or explain the root causes of slower execution.
- Include explicit instructions for installing required dependencies on Linux (e.g., tar, Azure CLI, SSH).
- Clarify any limitations or differences in functionality between Windows and Linux deployments.
Create Pull Request
Azure Arc
Support matrix for Azure Arc-enabled System Center Virtual Machine Manager
...pport-matrix-for-system-center-virtual-machine-manager.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows Server and SCVMM are inherently Windows-centric technologies, but the documentation repeatedly foregrounds Windows requirements, tools (WinRM, Windows Management Framework), and examples. Linux is mentioned only as an alternative for running the helper script, with warnings about performance issues, and Linux requirements are listed after Windows ones. There are no Linux-specific examples or guidance for common tasks, and Windows tools (WinRM, PowerShell, Windows Management Framework) are referenced without Linux equivalents or alternatives.
Recommendations
- Provide Linux-specific examples and troubleshooting steps for running the helper script and deploying the Resource Bridge.
- Clarify which steps are platform-agnostic and which require Windows-only tools, and offer Linux alternatives where possible.
- Include guidance for configuring WinRM or equivalent remote management on Linux, if supported, or explicitly state limitations.
- List Linux software requirements and installation steps before or alongside Windows requirements for parity.
- Address performance issues on Linux with actionable advice or workarounds, rather than just warnings.
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 presented 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, but does include a cross-platform sqlcmd example.
Recommendations
- Mention cross-platform GUI tools such as Azure Data Studio or DBeaver alongside SSMS for Linux/macOS users.
- Provide explicit Linux/macOS connection examples (e.g., using Azure Data Studio or other SQL clients) in addition to sqlcmd.
- Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
- Ensure that examples and instructions are not Windows-first, but rather platform-neutral or inclusive.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for all major platforms for most tools, but there are subtle Windows biases: Windows installation links are often listed first, and there are specific notes about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS troubleshooting. The curl installation instructions for Linux are less explicit ("install curl package") compared to a direct link for Windows. There are also PowerShell-specific notes, but no Bash/zsh equivalents.
Recommendations
- List installation links for Linux, macOS, and Windows in a consistent order (e.g., alphabetical or rotating which is first).
- Provide explicit installation instructions or links for curl on Linux and macOS, not just 'install curl package'.
- Where PowerShell-specific notes are given, consider adding Bash/zsh equivalents or clarifying when platform-specific issues may arise.
- Ensure troubleshooting notes are balanced across platforms, not just Windows/PowerShell.
Azure Arc
Data collection and reporting | Azure Arc-enabled data services
...zure-arc/data/privacy-data-collection-and-reporting.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform and does not provide command-line examples or instructions that are Windows-specific. However, in the 'Arc-enabled SQL Server' billing data example, the sample payload includes 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', which may give the impression that Windows is the primary or only supported platform for this scenario. There are no Linux/macOS-specific examples or explicit parity statements, and the only OS-specific reference is to Windows.
Recommendations
- Add Linux-based examples in the billing data section, e.g., with 'osType': 'Linux', and a non-Hyper-V manufacturer/model.
- Explicitly state that Azure Arc-enabled data services support both Windows and Linux environments where applicable.
- If the data collection and reporting process is identical across platforms, clarify this to reassure Linux/macOS users.
- Consider including a table or section summarizing OS/platform support for all resource types discussed.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation refers to Azure CLI as the required management tool and links to both general and Windows-specific installation pages, but does not clarify or provide explicit instructions/examples for Linux or macOS users. The 'Management machine requirements' section links to the Windows Azure CLI installation page and does not mention Linux or macOS, which may lead Linux users to believe Windows is required. No PowerShell or Windows-only commands are present, but the lack of Linux parity in examples and links is a minor bias.
Recommendations
- Explicitly state that the management machine can be Windows, Linux, or macOS.
- Provide links to Azure CLI installation instructions for all supported platforms, not just Windows.
- Add a note or section confirming that all CLI commands work on Linux/macOS and that no Windows-specific tools are required.
- If there are any platform-specific considerations (e.g., file paths, permissions), document them for Linux/macOS 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
Powershell Heavy
Windows Tools
Summary
The documentation generally presents authentication options and examples in a cross-platform manner, but there is a mild Windows bias in the authentication section. The 'Interactive browser login' is labeled as 'Windows only' and described first, while the Linux default ('Device code login') is described second. The access token section references the PowerShell cmdlet 'Get-AzAccessToken' as the only example for obtaining a token, with no Linux/CLI equivalent. Additionally, certificate authentication from the Windows certificate store is described in detail, but there is no equivalent Linux-specific guidance for certificate storage.
Recommendations
- Reorder authentication options to present cross-platform or Linux-default methods (such as device code login) before Windows-only options.
- When referencing PowerShell cmdlets (e.g., Get-AzAccessToken), also provide equivalent Azure CLI commands (e.g., 'az account get-access-token') for Linux/macOS users.
- For certificate-based authentication, add Linux-specific instructions for storing and referencing certificates (e.g., using PEM files in the filesystem) and clarify any platform-specific differences.
- Where features are Windows-only (such as using the Windows certificate store), clearly label them as such and, where possible, provide Linux/macOS alternatives or explicitly state if none exist.
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 authentication, and lists Windows NTP as the default in the notes. Windows-related endpoints (e.g., login.windows.net, servicebus.windows.net) are mentioned alongside generic Azure endpoints. However, Linux-specific requirements are also present (e.g., packages.microsoft.com for Linux installation packages, log collection for Linux components, SSH as a connectivity requirement), and the documentation does not provide command-line examples or instructions that are Windows-only. The Windows bias is mostly in the listing of Windows endpoints and defaults, rather than in actionable steps or guidance.
Recommendations
- Clarify when Windows-specific endpoints (e.g., time.windows.com) are only required for Windows deployments, and provide equivalent Linux guidance (e.g., mention typical Linux NTP servers like pool.ntp.org).
- Where Windows is listed as the default (e.g., NTP), explicitly state Linux alternatives and when to use them.
- Ensure parity in notes and explanations for both Windows and Linux management machines and appliance VMs.
- If possible, provide a summary table or section that distinguishes Windows-only, Linux-only, and cross-platform requirements.
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 both Windows and Linux release notes and download links, but there is a consistent pattern of Windows being listed first in download links and feature tables. Some improvements and known issues reference Windows-specific tools (e.g., PowerShell, msiexec) and workflows, with explicit instructions for Windows installer elevation, while Linux equivalents are not always described. There are several Windows-only features or bug fixes, but Linux-only changes are also called out when present. Overall, the documentation is usable for Linux users, but the ordering and some instructions show a mild Windows bias.
Recommendations
- Alternate the order of Windows and Linux in download links and feature tables, or present them in parallel to avoid the perception of Windows-first bias.
- Where Windows-specific installation or troubleshooting steps are given (e.g., using msiexec or PowerShell), provide equivalent Linux instructions (e.g., using rpm, dpkg, or systemctl) when relevant.
- Highlight Linux-only changes or known issues as clearly as Windows-only ones.
- Consider a short section or callout for Linux/macOS users with links to relevant installation and troubleshooting guides.
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 are minor signs of Windows bias: Windows log file locations and PowerShell/Windows command syntax are mentioned first in several sections, and Windows-specific tools (e.g., PowerShell, Windows environment variables) are referenced. Linux equivalents are provided, but Windows examples and terminology often precede Linux, and some remediation steps reference Windows paths or tools before Linux alternatives.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not consistently second.
- Where file paths or tools are referenced, provide both Windows and Linux equivalents side-by-side.
- Ensure remediation steps mention Linux commands and paths equally, not just as an afterthought.
- Where PowerShell or Windows environment variables are used in examples, provide corresponding Bash/Linux shell examples.
- Consider grouping Windows and Linux troubleshooting sections separately for clarity and parity.
Azure Arc
What's 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 a few instances where Windows-specific features or tools are mentioned first or exclusively. For example, the June 2025 entry highlights customization of Windows VMs, and the October 2024 entry lists Windows-centric tools (System Center Configuration Manager, Group Policy) before mentioning Ansible (a cross-platform tool). Azure PowerShell is also listed alongside Azure CLI and REST APIs, but not prioritized. Linux is mentioned in May 2025 for Arc agent installation, but overall, Windows tools and patterns appear before their Linux equivalents in some sections.
Recommendations
- When listing at-scale agent installation methods, mention cross-platform tools (e.g., Ansible) before or alongside Windows-specific tools (e.g., Group Policy, SCCM).
- Ensure Linux and macOS examples or tools are given equal prominence, especially in sections about agent installation and VM management.
- Where possible, clarify which features are Windows-only and which are cross-platform, to help users quickly identify relevant information.
- Add explicit Linux/macOS examples or references for VM customization and management where applicable.
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. Bash examples are consistently presented before PowerShell, and Linux-specific notes (such as removing carriage returns) are included. No Windows-only tools or patterns are used, and all commands are cross-platform (az CLI, docker, kubectl). The only minor bias is that PowerShell examples are given, but Bash is always shown first.
Recommendations
- Continue to provide Bash and PowerShell examples side-by-side.
- Consider clarifying that Bash examples are suitable for Linux/macOS and Windows users using WSL or Git Bash.
- Explicitly mention that az CLI, docker, and kubectl commands are cross-platform.
- Add a brief note at the top indicating that Bash examples are for Linux/macOS and PowerShell for Windows, for user clarity.
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 every CLI operation, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. There are no missing Linux examples or Windows-only tools mentioned.
Recommendations
- Maintain the current approach of providing both Bash and PowerShell examples.
- Consider clarifying that Azure CLI commands work equally well on Linux, macOS, and Windows.
- Optionally, alternate the order of Bash and PowerShell tabs or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to reinforce parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first. Both tabs are fully fleshed out and parity is maintained in the commands. There is no exclusive use of Windows tools or patterns, and no missing Linux examples. However, the inclusion of PowerShell as the only alternative to Bash (rather than, for example, zsh or fish) may indicate a slight Windows bias. The use of the Azure CLI (az), which is cross-platform, mitigates most friction.
Recommendations
- Ensure the Bash tab remains the default or first tab, as Bash is the most common shell for Linux/macOS users.
- Consider clarifying in the introduction that all commands are cross-platform and that Azure CLI is supported on Windows, Linux, and macOS.
- Optionally, add a note for macOS users that Bash commands are directly usable in Terminal.
- If possible, provide a generic shell tab (e.g., 'Shell') to indicate compatibility with other POSIX shells.
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
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every command and script section, but PowerShell examples are consistently shown immediately after Bash, and in some cases, variable naming and explanations are duplicated for PowerShell. There is no evidence of Windows-only tools or patterns being prioritized, nor are Linux equivalents missing. All CLI commands are cross-platform (Azure CLI, kubectl), and Bash is always presented first. However, the presence of PowerShell examples throughout may create a slight perception of Windows bias.
Recommendations
- Ensure Bash and PowerShell examples are equally prominent and clearly labeled.
- Consider adding a brief note at the start clarifying that all commands are cross-platform and that Bash is suitable for Linux/macOS users, while PowerShell is for Windows users.
- If possible, provide a single unified CLI example where the command syntax is identical, to reduce duplication and potential confusion.
- Review variable naming conventions to ensure they are platform-agnostic and do not favor Windows/PowerShell patterns.
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, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are always present and sometimes shown immediately after Bash, which may create a slight perception of Windows preference. There are no Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Ensure Bash examples are always shown first, as Bash is the default shell for Linux/macOS and is also available on Windows via WSL or Git Bash.
- Clarify in the introduction that all steps are cross-platform and that PowerShell is provided for Windows users, while Bash is suitable for Linux/macOS and also for Windows users with Bash environments.
- Consider adding a brief note about using Bash on Windows (e.g., via WSL or Git Bash) for users who prefer Bash.
- If possible, provide a generic 'Azure CLI' tab for steps where the syntax is identical, to reduce duplication and emphasize cross-platform parity.
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 page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash or Linux shell examples for those commands. While the Azure CLI is cross-platform, showing only PowerShell syntax can create friction for Linux/macOS users. However, most other CLI instructions use Bash syntax, and there is no mention of Windows-specific tools or patterns outside of PowerShell.
Recommendations
- For every CLI example shown in PowerShell, provide a Bash/Linux shell equivalent.
- Clarify that Azure CLI commands work on all platforms and note any OS-specific syntax differences.
- Use generic CLI syntax (without PowerShell backticks or variable notation) where possible, or show both Windows and Linux/macOS variants side by side.
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 release notes for Azure Connected Machine agent generally provide parity between Windows and Linux, with features and fixes listed for both platforms. However, there is a mild Windows bias: Windows download links and version numbers are consistently listed before Linux, installer troubleshooting and instructions reference Windows tools (msiexec, PowerShell, Command Prompt) exclusively, and some improvements (e.g., ExtensionCleanup.ps1, GUI accessibility) are Windows-only with no Linux equivalents or alternative instructions. Linux-specific issues and fixes are present, but Windows patterns and tools are mentioned first and more often.
Recommendations
- Where installer troubleshooting is discussed, add equivalent Linux instructions (e.g., using rpm, dpkg, systemctl) for parity.
- When referencing scripts or tools (e.g., ExtensionCleanup.ps1), clarify if there are Linux alternatives or note that the feature is Windows-only.
- Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
- Include Linux/macOS command-line examples or troubleshooting steps alongside Windows/PowerShell examples when relevant.
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 release notes for Azure Connected Machine agent generally provide parity between Windows and Linux in terms of feature and bug fix coverage. However, there are signs of Windows bias: Windows download links and version numbers are consistently listed before Linux, installer instructions and troubleshooting are focused on Windows tools (e.g., PowerShell, msiexec), and some improvements reference Windows-specific scripts (.ps1) or GUI elements without Linux equivalents. Linux-specific issues and enhancements are included, but Windows patterns and terminology are more prominent throughout.
Recommendations
- Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side to avoid implicit prioritization.
- Include Linux installer troubleshooting steps (e.g., using rpm, dpkg, systemctl) alongside Windows instructions for common issues.
- Where Windows-specific tools/scripts (e.g., ExtensionCleanup.ps1, msiexec) are mentioned, clarify if there are Linux equivalents or note their absence.
- Add more explicit Linux command examples and troubleshooting tips where relevant.
- Ensure that GUI improvements or features are clearly marked as Windows-only and, if possible, mention Linux alternatives or limitations.
Azure Arc
Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters.
.../main/articles/azure-arc/kubernetes/cluster-connect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Shell Inconsistency
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) instructions in parallel throughout, but in several places, PowerShell examples are given equal prominence, and some shell commands (such as variable assignment and output) use PowerShell syntax that is not portable to Linux/macOS. The final example for using kubectl is shown as a PowerShell code block, and variable assignment in PowerShell is shown before or alongside Bash, which may confuse Linux/macOS users. However, Azure CLI is available for all platforms and is shown in all critical steps, so Linux/macOS users can complete the workflow.
Recommendations
- Ensure that all shell commands (especially those using kubectl, variable assignment, and token extraction) are shown in Bash syntax when targeting cross-platform users, and clearly mark PowerShell examples as Windows-only.
- Show Bash/Linux/macOS examples first, or provide tabs for Bash, PowerShell, and Azure CLI where appropriate.
- In sections where PowerShell is used for variable assignment or token extraction, provide equivalent Bash commands for Linux/macOS users.
- For kubectl usage, use generic shell code blocks or provide both Bash and PowerShell examples.
- Clarify that Azure PowerShell instructions are intended for Windows users, and encourage Linux/macOS users to use Azure CLI and Bash.
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 generally presents Windows download links and features before Linux equivalents and occasionally references Windows-specific tools (e.g., PowerShell, msiexec) and installer behaviors. However, Linux support is consistently present, and Linux-specific changes are also called out. There are no critical sections that exclude Linux, but minor ordering and tool references may create slight friction for Linux/macOS users.
Recommendations
- Present download links for Windows and Linux in parallel or randomize their order to avoid implicit prioritization.
- Where installer troubleshooting is discussed, provide equivalent Linux guidance (e.g., for RPM/DEB issues or common Linux install pitfalls) if relevant.
- When referencing Windows tools (e.g., PowerShell, msiexec), clarify that these are Windows-specific and, if possible, link to Linux installation or troubleshooting instructions.
- In tables, consider listing Linux and Windows columns in alternating order or grouping cross-platform features together.
- Continue to call out Linux-only and Windows-only changes explicitly, as is already done.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides installation path information for both Windows and Linux, but lists the Windows path first and includes extra detail about PATH variable handling on Windows. No Linux/macOS examples are missing, and no Windows-only tools or PowerShell commands are referenced in the main CLI usage sections.
Recommendations
- Present Linux and Windows installation paths in parallel or alternate the order to avoid implicit prioritization.
- Add equivalent details for Linux, such as whether the installation path is added to $PATH automatically, and any steps needed to refresh the shell.
- Explicitly mention macOS support or limitations if applicable.
- Ensure future examples and troubleshooting steps include both Windows and Linux command syntax where differences exist.
Azure Arc
CLI reference for `azcmagent disconnect`
...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows mild Windows bias by describing the interactive browser login as 'Windows only' and listing it first among authentication options. Additionally, the only explicit access token retrieval example references the Windows PowerShell cmdlet 'Get-AzAccessToken', with no Linux/macOS equivalent shown. However, Linux authentication methods (device code, Azure CLI) are described and supported, and examples are generally cross-platform.
Recommendations
- Provide Linux/macOS equivalents for access token retrieval (e.g., Azure CLI 'az account get-access-token' or Microsoft Entra client usage).
- Clarify that device code and Azure CLI authentication methods are fully supported on Linux/macOS, and consider listing them before or alongside Windows-specific methods.
- Add notes or examples for Linux/macOS users where authentication or usage patterns differ.
- Avoid listing Windows-only options first unless they are most common for all 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
Powershell Heavy
Summary
The documentation page exhibits minor Windows bias. The authentication options section lists 'Interactive browser login (Windows only)' first and describes it as the default, while Linux is mentioned secondarily. The only external tool referenced for obtaining an access token is the Windows PowerShell cmdlet 'Get-AzAccessToken', with no mention of Linux/macOS equivalents (e.g., Azure CLI). However, most command examples and instructions are platform-neutral, and Linux authentication flows are described.
Recommendations
- List Linux authentication flows (device code, Azure CLI) before or alongside Windows options to avoid Windows-first ordering.
- Provide Linux/macOS equivalents for obtaining access tokens, such as using 'az account get-access-token' with Azure CLI.
- Clarify which examples and flags apply equally to Linux/macOS and Windows, and explicitly mention cross-platform compatibility.
- Add a brief note or table summarizing authentication defaults per OS for quick reference.
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 VM extensions, listing a larger number of Windows-specific extensions and providing more detailed links for Windows scenarios. However, Linux extensions are also covered in a dedicated section with parity in deployment methods and partner extensions. No exclusive use of Windows tools or missing Linux examples is observed.
Recommendations
- Alternate the order of Windows and Linux extension tables in the documentation, or present them side-by-side to emphasize equal support.
- Ensure that the number and detail of Linux extension examples matches those for Windows, where possible.
- Add explicit statements or visual cues highlighting Linux support in introductory sections.
- Where links reference Windows-specific guides, ensure Linux equivalents are also linked and visible.