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 1851-1875 of 2334 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but there are subtle Windows biases: Windows installation links are listed first for kubectl and curl, and there is a specific note about using cmd.exe instead of PowerShell for curl on Windows 10, without equivalent Linux/macOS guidance. The curl installation for Linux is less explicit (just 'install curl package'), lacking a direct link or command example. There is also a PowerShell-specific note about curl aliases, but no comparable Linux/macOS shell notes.
Recommendations
- List installation links for all platforms in parallel or alphabetical order to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions for curl (e.g., 'sudo apt install curl', 'brew install curl') with direct links.
- Include shell-specific notes for Linux/macOS where relevant (e.g., bash/zsh nuances for curl or kubectl).
- Balance platform-specific notes: if mentioning PowerShell quirks, also mention any relevant Linux/macOS shell quirks.
- Consider providing example commands for checking tool versions on all platforms, not just Windows.
Create Pull Request
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 PowerShell examples are consistently presented alongside CLI and sometimes before Linux-native approaches. There are no Linux-specific command-line examples (e.g., Bash scripts), and the use of PowerShell is emphasized, which may create friction for Linux/macOS users who typically use Bash and Azure CLI. However, Azure CLI examples are present and fully functional for Linux/macOS users, and environment variable instructions use Bash syntax where appropriate.
Recommendations
- Ensure Azure CLI examples are always presented first, as CLI is cross-platform and native to Linux/macOS.
- Add explicit Bash script examples for common tasks, especially for onboarding and updating clusters.
- Clarify that Azure PowerShell is available cross-platform, but recommend Azure CLI for Linux/macOS users.
- Consider including a 'Linux/macOS' tab or section for any steps where environment setup differs.
- Review and minimize PowerShell-centric language unless the task is Windows-specific.
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 shows mild Windows bias. Windows-specific services (e.g., time.windows.com, login.windows.net, sts.windows.net, servicebus.windows.net) are referenced, and Windows NTP is mentioned as the default for Hyper-V. Windows-related endpoints appear before Linux equivalents in some cases. However, Linux endpoints and requirements (e.g., packages.microsoft.com for Linux package downloads, SSH port 22, log collection for Linux components) are also included, and the documentation is generally cross-platform.
Recommendations
- Clarify when Windows-specific endpoints (e.g., time.windows.com) are only needed for Windows-based deployments, and provide Linux alternatives (e.g., ntp.ubuntu.com or pool.ntp.org) where relevant.
- Explicitly state whether management machines and appliance VMs can be Linux-based, and if so, highlight any Linux-specific requirements or differences.
- Where Windows and Linux endpoints/tools are both relevant, list them together or in parallel, rather than Windows-first.
- Add example configurations for both Windows and Linux environments, especially for network and firewall settings.
- Ensure notes specify when a requirement is OS-specific (e.g., 'Windows NTP' vs. 'Linux NTP').
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with parity in most features and fixes. However, Windows download links are consistently listed before Linux, and Windows-specific tools (e.g., PowerShell, msiexec, GUI installer) are referenced in troubleshooting and known issues sections. Some improvements and bug fixes are described with Windows tools or patterns, while Linux equivalents are not always mentioned or explained in the same detail.
Recommendations
- Alternate the order of Windows and Linux download links or present them together to avoid implicit prioritization.
- When referencing Windows-specific tools (e.g., PowerShell, msiexec), provide Linux equivalents (e.g., shell commands, package managers) where relevant.
- Expand troubleshooting and known issues to include Linux-specific guidance, not just Windows installer scenarios.
- Ensure that improvements or bug fixes described for Windows (such as installer logic or GUI changes) are matched with Linux details if applicable, or explicitly state if not relevant.
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 provides authentication options and examples for both Windows and Linux, but there is a mild Windows bias: Windows-specific login methods and certificate store options are described first and in more detail, and Windows tools (like PowerShell's Get-AzAccessToken) are referenced without Linux equivalents. However, Linux authentication flows are covered and most examples are OS-agnostic.
Recommendations
- Present authentication options in a neutral order (not Windows-first), or clarify that device code login is default for Linux.
- When referencing Windows-specific tools (e.g., PowerShell's Get-AzAccessToken), also mention Linux/macOS alternatives (such as using Azure CLI to obtain access tokens).
- Add explicit Linux/macOS examples where Windows-specific flows are described (e.g., certificate handling, access token acquisition).
- Clarify which authentication methods and flags are supported on Linux/macOS, and provide guidance for those platforms.
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
Missing Linux Example
Summary
The documentation page for Azure Arc resource bridge system requirements exhibits mild Windows bias. Azure CLI installation links and requirements are presented with a Windows-centric focus (e.g., linking to Azure CLI Windows install docs, specifying x64/32-bit requirements without clarifying Linux/macOS equivalents). There are no explicit Linux/macOS examples or guidance for management machine setup, and no mention of Linux/macOS compatibility for CLI commands or file locations.
Recommendations
- Add explicit guidance for installing Azure CLI on Linux and macOS, including relevant links.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific requirements.
- Mention file location defaults for CLI-generated files on Linux/macOS (e.g., home directory, permissions).
- Include examples or notes for running az arcappliance commands on Linux/macOS.
- Ensure that references to Azure CLI bitness (x64/32-bit) are explained for Linux/macOS users (e.g., most Linux distributions are x64; clarify if 32-bit is relevant).
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 for both Linux and Windows in most sections, including installation URLs and agent configuration. However, there is a mild bias in the ordering of examples and references: Windows installation packages and tools (such as Windows Admin Center) are mentioned first or exclusively in some places, and Windows-specific cipher suite configuration is detailed before Linux/OpenSSL. Windows Admin Center is referenced as a service tag and endpoint, but SSH (the Linux equivalent) is only briefly mentioned. The cryptographic protocol section provides more detail for Windows than Linux.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than consistently listing Windows first.
- Expand Linux-specific guidance for TLS/cipher suite configuration, including links to OpenSSL configuration best practices.
- When referencing Windows Admin Center, also highlight SSH as the Linux management equivalent, and provide links to relevant SSH documentation.
- Ensure that troubleshooting and configuration sections provide equal detail for Linux and Windows, especially for security and networking topics.
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 bias in example ordering: Azure PowerShell examples are presented after Azure CLI, and PowerShell is mentioned as a management option alongside CLI and portal. Azure CLI is correctly described as cross-platform, but PowerShell is presented without explicit mention of its cross-platform support (though Az.ConnectedMachine is available on Linux PowerShell Core). There are no Windows-only tools or missing Linux examples, but PowerShell is more prominent than, for example, bash scripting or Linux-native tools.
Recommendations
- Explicitly state that Azure PowerShell (Az.ConnectedMachine module) is available on Linux and macOS via PowerShell Core, not just Windows.
- Consider providing bash or shell script examples for common operations, especially for Linux users.
- Ensure that CLI examples are shown first and that PowerShell is clearly marked as optional for cross-platform use.
- Add a note clarifying that all management operations can be performed equally from Linux, macOS, or Windows environments.
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 (such as PowerShell syntax and Windows paths) are often presented first, and Windows-specific details (e.g., PowerShell version requirements, Windows log file paths) are more prominent. Linux examples are included and reasonably detailed, but Windows tools and patterns (e.g., PowerShell, Windows environment variables, Windows log paths) are mentioned before or more extensively than their Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in some sections to avoid implicit prioritization.
- Where Windows-specific tools (e.g., PowerShell) are referenced, ensure equivalent Linux commands (e.g., Bash) are given equal prominence and explanation.
- Clarify when remediation steps differ between Windows and Linux, and provide explicit Linux instructions (e.g., for log file locations, service management, permissions).
- Where file paths or environment variables are mentioned, always include both Windows and Linux equivalents together.
- Consider adding a summary table or section that highlights parity and differences between Windows and Linux troubleshooting steps.
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, 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 structure, as Bash and PowerShell examples are both present.
- 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 az CLI and Helm are cross-platform tools.
- Ensure that any future updates continue to provide both Bash and PowerShell examples.
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-specific tools (such as PowerShell) and Windows-focused features are mentioned first or exclusively. Examples include references to PowerShell runbooks, Windows registry, and Windows Server management. Although Linux is mentioned in some scenarios (e.g., Azure Update Manager supports Windows and Linux, VM extensions for Windows or Linux), Windows examples and tools tend to be listed before Linux equivalents, and PowerShell is highlighted as a primary automation tool.
Recommendations
- Ensure that Linux examples and tools (such as Bash, shell scripts, and Linux-specific automation) are mentioned alongside PowerShell and Windows tools.
- When listing supported operating systems or tools, alternate the order or explicitly state parity between Windows and Linux.
- Provide links to Linux-specific documentation or examples for automation, monitoring, and configuration tasks.
- Highlight cross-platform SDKs and CLI usage equally, and avoid implying PowerShell is the default for automation.
- Add explicit examples or guidance for Linux VM management where only Windows is referenced.
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 mention both Windows and Linux, there are instances where Windows-specific features (e.g., customizing guest OS settings for Windows VMs, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are highlighted. In the June 2024 section, Azure PowerShell is listed after Azure CLI and REST APIs, but no Linux-specific shell or tool is mentioned. The October 2024 section lists Windows-centric tools (System Center Configuration Manager, Group Policy) before Linux-centric tools (Ansible). Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks, but Windows tools and features are sometimes mentioned first or more prominently.
Recommendations
- Ensure Linux-centric tools (e.g., Ansible, Bash scripts) are mentioned alongside or before Windows-centric tools when listing automation options.
- Where possible, provide parity in examples for both Windows and Linux (e.g., PowerShell and Bash/CLI examples).
- Clarify when features are Windows-only to avoid confusion.
- Consider adding references to Linux guest customization and management features if available.
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 most sections, PowerShell examples are presented immediately after Bash, and the Bash examples are labeled first. There is no evidence of Windows-specific tools, patterns, or exclusive Windows instructions. The Azure CLI is used throughout, which is cross-platform.
Recommendations
- Maintain the current structure of providing both Bash and PowerShell examples.
- Consider clarifying that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- If possible, add a brief note for users on macOS/Linux that Bash examples are directly usable in their environments.
- Ensure that any referenced scripts (such as the 'Clean-up script') are available in both Bash and PowerShell versions, or clarify their platform compatibility.
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 release notes for Workload Orchestration in Azure Arc predominantly use PowerShell syntax for CLI examples in the May 2025 release, despite the Azure CLI being cross-platform. Bash examples are used elsewhere, but PowerShell appears first and is the only shell shown for configuration file operations. There are no explicit Linux/macOS-specific examples or references, and no mention of Linux tools or patterns. However, the core features and CLI commands are cross-platform, and the documentation does not reference Windows-only tools or concepts outside of PowerShell syntax.
Recommendations
- Provide Bash equivalents for all PowerShell CLI examples, especially for configuration file operations.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and indicate shell-agnostic usage where possible.
- When showing CLI examples, alternate between Bash and PowerShell or show both.
- Explicitly mention Linux/macOS compatibility for CLI features and extensions.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all steps, 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 used, and all commands are cross-platform (az CLI, Helm).
Recommendations
- Maintain the current structure, as Bash and PowerShell examples are both provided.
- Consider clarifying in the introduction that both Linux/macOS and Windows are fully supported.
- Optionally, alternate the order of Bash and PowerShell tabs in future documentation to avoid implicit prioritization.
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, and in some sections (e.g., variable naming, file paths), Windows conventions (backslashes, PowerShell syntax) are used. Bash examples are always shown first, but PowerShell is given equal prominence. There are no Windows-only tools or patterns; 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
- Ensure that file path examples in PowerShell use forward slashes or note that backslashes are Windows-specific.
- Clarify that PowerShell examples are for Windows users, and Bash for Linux/macOS, to help users choose the right tab.
- Consider adding a note about cross-platform compatibility of Azure CLI and Helm.
- If possible, provide a brief summary or table at the top indicating which shell to use for each OS.
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 presents Azure CLI installation links and references with Windows as the default or first option. However, it does not provide explicit Windows-only examples, nor does it reference Windows-specific tools or patterns. The CLI commands shown are cross-platform, and there are no PowerShell-specific instructions or Windows-only tooling. Linux/macOS users may experience minor friction due to Windows-centric links and ordering.
Recommendations
- Provide Azure CLI installation links for Linux and macOS alongside Windows, or use a generic cross-platform link.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide explicit statements or examples for Linux/macOS users.
- Ensure that CLI commands and file paths are shown in a cross-platform manner (e.g., avoid Windows-style paths unless necessary).
- Add a note or section about supported operating systems for the management machine, including Linux and macOS.
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, templates) are mentioned without bias, and partner extensions are shown for both OSes. No critical Linux features are missing, and Linux examples are present where relevant.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or combining them into a single table with OS columns to reinforce parity.
- Explicitly state that all deployment methods (Azure CLI, PowerShell, portal, templates) are available for both Windows and Linux extensions.
- Ensure that linked usage/deployment guides for Linux extensions are as comprehensive as their Windows counterparts.
- Add a brief note at the start clarifying that both Windows and Linux are fully supported and covered in this documentation.
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 presented before PowerShell, which is a minor 'windows_first' bias (since PowerShell is the Windows shell, but Bash is shown first). No exclusive Windows tools or patterns are used, and all commands rely on cross-platform Azure CLI and Helm tools. There are no missing Linux examples, and no Windows-specific tools or terminology are prioritized.
Recommendations
- Maintain the current parity by continuing to provide both Bash and PowerShell examples.
- Consider alternating the order of Bash and PowerShell tabs or clarifying that both are equally supported.
- Explicitly mention that all examples are cross-platform and can be used on Linux, macOS, and Windows (with PowerShell or Bash).
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 there are no examples for popular Linux/macOS SQL clients (e.g., DBeaver, Azure Data Studio). The documentation also lacks explicit parity for Linux/macOS users in terms of graphical client options.
Recommendations
- List cross-platform tools (e.g., Azure Data Studio, DBeaver) alongside SSMS for connecting to SQL Managed Instance.
- Provide explicit Linux/macOS client examples and instructions, including graphical tools.
- Ensure that Linux/macOS users are not implicitly directed to Windows-only solutions by listing cross-platform options first or equally.
- Clarify that sqlcmd is available on both Windows and Linux, and provide installation instructions or links for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There are explicit notes about Windows PowerShell and cmd.exe, but Linux-specific instructions are less detailed (e.g., 'Linux: install curl package' without a link). The note about 'curl' in PowerShell is prominent, but no equivalent Linux/macOS shell guidance is given. Overall, Linux/macOS users can complete the task, but the documentation favors Windows in ordering and detail.
Recommendations
- List installation links for all platforms in parallel order (Windows, Linux, macOS) or alphabetically to avoid Windows-first bias.
- Provide explicit Linux/macOS installation instructions or links for tools like 'curl', matching the detail given for Windows.
- Add shell-specific notes for Linux/macOS (e.g., bash/zsh usage of curl) similar to the PowerShell note.
- Balance platform-specific guidance: if mentioning Windows cmd.exe or PowerShell, also mention Linux/macOS equivalents where relevant.
Azure Arc
Features and Capabilities of SQL Managed Instance enabled by Azure Arc
...n/articles/azure-arc/data/managed-instance-features.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, there are no explicit Linux/macOS alternatives or examples, and Windows tools are presented as primary options. However, the page does not provide actual command examples, and the Azure Arc SQL Managed Instance is a cross-platform service.
Recommendations
- Add explicit mention of cross-platform management tools such as Azure Data Studio, which runs natively on Linux/macOS.
- Clarify which tools are available on Linux/macOS and which are Windows-only.
- Provide links or guidance for Linux/macOS users on managing SQL Managed Instance enabled by Azure Arc (e.g., using Azure CLI, Azure Data Studio, or VS Code).
- If PowerShell scripting is mentioned, also highlight Bash scripting or other cross-platform automation options.
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 examples immediately after Azure CLI, and sometimes with more detailed explanation. While Azure PowerShell is not strictly Windows-only, it is most commonly used on Windows, and the documentation does not mention Bash or Linux-specific shell examples. However, Azure CLI commands are cross-platform and the environment variable instructions use both export (Linux/macOS) and PowerShell syntax, showing some parity.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be run on Linux/macOS.
- Add Bash shell example blocks for environment variable setup (e.g., using export for Linux/macOS, as already shown, but clarify OS context).
- Mention that Azure PowerShell can be used on Linux/macOS, or provide Bash alternatives where appropriate.
- Consider adding a short section or callout about running these tasks on Linux/macOS, including any prerequisites or differences.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) and Windows NTP as the default, suggesting a Windows-centric perspective. Windows-related endpoints are mentioned alongside general endpoints, and Windows terminology appears before Linux equivalents (e.g., Windows NTP before mentioning alternatives). However, Linux-specific endpoints (e.g., packages.microsoft.com, linuxgeneva-microsoft.azurecr.io) and SSH are also included, indicating some Linux parity. No explicit Linux/PowerShell command examples are present, but the listing order and notes favor Windows tools and patterns.
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 or pool.ntp.org) where appropriate.
- Add explicit notes or examples for Linux management machines, including references to Linux tools and patterns.
- Ensure endpoint descriptions and notes are platform-neutral unless a service is truly Windows-only.
- Where Windows terminology is used (e.g., 'Windows NTP'), mention Linux equivalents in the same section and with equal prominence.