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 1376-1400 of 2334 flagged pages
Azure Arc
Configure OneLake Identity for Cloud subvolumes
.../container-storage/howto-configure-onelake-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing Power BI web links and portals, which are more commonly associated with Windows environments. There are no explicit Linux or cross-platform CLI examples, nor is there mention of Linux-specific tools or workflows. The configuration steps focus on GUI navigation and do not provide command-line alternatives that would be more familiar to Linux users.
Recommendations
- Provide equivalent Linux CLI examples (e.g., using Azure CLI, kubectl, or REST API) for configuring OneLake Identity and subvolumes.
- Include instructions for accessing and managing OneLake workspaces from Linux environments, avoiding reliance on Windows-centric portals.
- Mention cross-platform tools and patterns, such as scripting with Bash or using open-source clients, to ensure parity for Linux administrators.
- Add screenshots or walkthroughs for Linux-based workflows where applicable.
Create Pull Request
Azure Arc
Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools
...ate-sql-managed-instance-using-kubernetes-native-tools.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows mild Windows bias by presenting PowerShell as the first example for base64 encoding credentials, followed by Linux/macOS. Additionally, the example file path for kubectl uses a Windows-style path (C:\arc-data-services\sqlmi.yaml) rather than a Linux-style path, which may be less familiar to Linux users. However, Linux/macOS equivalents are provided, and most instructions are platform-neutral.
Recommendations
- Present Linux/macOS CLI examples before or alongside PowerShell examples, especially for common tasks like base64 encoding.
- Use platform-neutral file paths in examples (e.g., ./arc-data-services/sqlmi.yaml) or provide both Windows and Linux/macOS path formats.
- Explicitly state that instructions apply equally to Windows, Linux, and macOS, and avoid implying Windows is the default platform.
- Consider adding a table or section summarizing commands for all major platforms, ensuring parity and visibility.
Azure Arc
Delete resources from Azure Arc-enabled data services
...main/articles/azure-arc/data/delete-azure-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a GUI tool most commonly used on Windows) for resource deletion steps, and does not provide any Linux-specific examples or mention Linux-native tools. All command-line instructions use the Azure CLI, which is cross-platform, but there are no examples of using Linux shell commands (e.g., bash/kubectl) for resource deletion, nor is there any mention of Linux-specific workflows or considerations. The portal-based instructions are presented first, reinforcing a Windows-first approach.
Recommendations
- Include examples using Linux shell commands (e.g., bash, kubectl) for deleting resources from Kubernetes clusters.
- Explicitly mention that the Azure CLI commands work on both Windows and Linux, and provide sample commands for both environments.
- Add instructions for deleting resources using Linux-native tools and workflows, such as using kubectl to delete namespaces or deployments.
- Balance the ordering of examples so that Linux and Windows approaches are presented equally, or provide a dedicated section for Linux users.
- Reference Linux desktop environments and terminal usage where appropriate, not just the Azure portal.
Azure Arc
Connectivity modes and requirements
...docs/blob/main/articles/azure-arc/data/connectivity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page does not show overt Windows bias in terms of exclusive use of Windows tools or PowerShell, but there is a subtle bias in the ordering and emphasis: Azure portal, Azure CLI, and Azure Resource Manager APIs are mentioned first and most prominently, with Linux-native tools (kubectl, Helm, oc) listed later or as alternatives. There are no explicit Linux-specific examples or instructions, and no mention of Linux shell commands or workflows. The documentation assumes familiarity with Azure-centric tools, which are often more Windows-oriented, and does not provide parity for Linux users in terms of example commands or tool usage.
Recommendations
- Provide explicit Linux shell (bash) examples alongside Azure CLI and portal instructions.
- List Linux-native tools (kubectl, Helm, oc) before or alongside Azure tools when describing provisioning and management workflows.
- Include example workflows for Linux environments, such as using bash scripts or Linux authentication mechanisms.
- Clarify cross-platform compatibility for all tools mentioned (e.g., Azure Data Studio, Azure CLI) and note any OS-specific considerations.
- Add a section or callout for Linux administrators, summarizing key steps and tools relevant to Linux environments.
Azure Arc
Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc
...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by consistently presenting Windows-specific paths (e.g., C:\Backupfiles\) and examples first, without providing equivalent Linux examples (e.g., /home/user/Backupfiles/). The instructions and code samples for backing up databases and copying files into pods use Windows file system conventions and do not mention or illustrate how to perform these steps on Linux systems. Additionally, tool usage (Azure Data Studio, Azure Storage Explorer) is described generically, but examples and screenshots (where referenced) are likely Windows-centric.
Recommendations
- Provide parallel Linux examples for file paths and commands (e.g., show both C:\Backupfiles\test.bak and /home/user/Backupfiles/test.bak in backup and kubectl cp commands).
- Explicitly mention Linux compatibility for all tools and steps, including installation and usage notes for Azure Data Studio and Azure Storage Explorer on Linux.
- Add notes or sections clarifying any platform-specific differences, such as file permissions, path formats, or required dependencies on Linux.
- Where screenshots or UI instructions are given, include Linux screenshots or clarify any differences in UI/UX between platforms.
- Review and update all code samples to ensure Linux users can follow along without confusion or extra research.
Azure Arc
Disaster recovery - SQL Managed Instance enabled by Azure Arc - portal
...-arc/data/managed-instance-disaster-recovery-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web-based GUI) for configuring disaster recovery, without mentioning or providing examples for command-line or scripting approaches on either Windows or Linux. While the portal is cross-platform, the absence of Linux-specific considerations or CLI/script examples (which are often preferred in Linux environments) may implicitly favor Windows-style, GUI-centric workflows. Additionally, there are no references to Linux tools, shell commands, or patterns, and the only alternative mentioned is a separate CLI article, without summary or parity in this page.
Recommendations
- Add brief examples or links for both PowerShell and Bash/Azure CLI workflows directly in this article, or summarize their availability and parity.
- Explicitly state that the Azure portal is accessible from any OS/browser to clarify cross-platform compatibility.
- Include a comparison table or section highlighting GUI vs. CLI approaches, with notes on OS compatibility.
- If there are Linux-specific considerations (such as firewall rules, connectivity, or authentication differences), mention them.
- Ensure that references to related content (such as the CLI article) are clearly labeled as cross-platform and indicate which OSes are supported.
Azure Arc
Save costs with reserved capacity
.../articles/azure-arc/data/reserved-capacity-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of the Azure portal for instructions and references to PowerShell, with no Linux-specific examples or mention of Linux tools. The order of tool mentions places the Azure portal and PowerShell before Azure CLI and API, and there are no CLI command examples for Linux users. There is also a lack of explicit guidance for Linux administrators, which may hinder parity for cross-platform users.
Recommendations
- Include step-by-step examples using Azure CLI for all major actions (e.g., purchasing, managing, and viewing reservations), as CLI is cross-platform and widely used on Linux.
- Explicitly mention Linux compatibility for all management options, clarifying that Azure CLI and REST API can be used from Linux systems.
- Provide sample scripts or command lines for reservation management using Azure CLI and REST API, alongside PowerShell examples if present.
- Ensure that tool references (portal, PowerShell, CLI, API) are presented in a neutral order or grouped together, rather than prioritizing Windows-centric tools.
- Add a section or note for Linux users, highlighting best practices and available tooling for managing Azure Arc SQL Managed Instance reservations.
Azure Arc
Data collection and reporting | Azure Arc-enabled data services
...zure-arc/data/privacy-data-collection-and-reporting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the billing data section, where the only explicit operating system example given is Windows ("osType": "Windows"). There are no Linux or cross-platform examples for SQL Server inventory or billing data, nor are Linux-specific patterns or tools mentioned. The documentation does not provide parity in examples or guidance for Linux environments, despite Azure Arc-enabled data services supporting Linux-based clusters and SQL Server on Linux.
Recommendations
- Include explicit Linux examples in billing and inventory data sections, such as 'osType': 'Linux' and relevant Linux server properties.
- Add notes or examples for SQL Server running on Linux, including differences in data collection, reporting, and diagnostic data.
- Ensure that any references to operating system properties or host types mention both Windows and Linux, or clarify cross-platform applicability.
- Where tools or commands are referenced (e.g., kubectl), provide guidance for both Windows and Linux environments, including shell and scripting differences if relevant.
- Review all JSON examples to ensure they are not exclusively Windows-centric and provide Linux variants where appropriate.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but the Windows-specific tool (certutil) is mentioned separately and in detail, including extra steps for output cleanup. The Linux method is presented first, but the Windows method receives more explanation and troubleshooting. No PowerShell examples are present, and the majority of commands (openssl, kubectl, az CLI) are cross-platform. However, Windows users are given additional guidance, which may suggest a slight Windows bias in tooling support.
Recommendations
- Provide equivalent troubleshooting and cleanup steps for Linux base64 output, if needed, to match the detail given for Windows.
- Mention alternative Linux tools for base64 encoding/decoding (e.g., openssl base64, xxd) to match the Windows certutil coverage.
- Clarify that all CLI commands (az, kubectl, openssl) work on both Windows and Linux, and provide explicit cross-platform notes where relevant.
- If additional Windows-specific steps are given, ensure Linux/macOS equivalents are also described for parity.
- Consider grouping base64 encoding instructions together, with clear cross-platform alternatives, rather than separating Windows and Linux.
Azure Arc
Get logs to troubleshoot Azure Arc-enabled data services
...in/articles/azure-arc/data/troubleshooting-get-logs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a CLI example that uses a Windows-style path (C:\temp\logs) for the --target-folder parameter, but does not offer a Linux equivalent (such as /tmp/logs). No Linux/macOS-specific examples or notes are given, which may confuse non-Windows users. The documentation does not mention PowerShell or Windows-only tools, but the example pathing is Windows-centric.
Recommendations
- Add Linux/macOS path examples (e.g., /tmp/logs) alongside Windows paths for the --target-folder parameter.
- Explicitly state that the CLI commands work on both Windows and Linux/macOS, and clarify any OS-specific behaviors.
- Where file paths are referenced, provide both Windows and Linux/macOS formats, or use a generic placeholder (e.g., <desired folder>) with a note about OS differences.
- Consider including screenshots or output samples from both Windows and Linux environments to improve parity.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows/Azure bias by primarily using Azure Kubernetes Service (AKS) examples and storage classes, mentioning Azure-specific tools and patterns first and in greater detail than their AWS and GCP equivalents. There are no explicit PowerShell or Windows-only command examples, but the focus on Azure (Microsoft's cloud) and its storage classes, as well as references to Azure CLI, may disadvantage Linux-centric or non-Azure users. Linux-specific storage patterns (e.g., NFS, local volumes) are mentioned but not exemplified, and alternative cloud providers are covered only briefly and after Azure.
Recommendations
- Provide example storage class configurations for popular Linux distributions and on-premises Kubernetes clusters, not just AKS.
- Include explicit examples using Linux-native tools (e.g., shell scripts, kubectl from Linux terminals) alongside Azure CLI.
- Offer parity in detail and examples for AWS EKS and GCP GKE, including their storage class creation and management workflows.
- Add more guidance and examples for NFS and other Linux-centric storage solutions, including configuration steps.
- Avoid referencing Azure-specific features or templates before more general Kubernetes concepts, or provide equal coverage for other platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, but consistently lists Windows and PowerShell examples before Linux/macOS. This ordering may subtly prioritize Windows users. There is also a slight emphasis on Windows scripting (mentioning .cmd, .bat, .ps1) before Linux equivalents (.sh), and Windows Task Scheduler is mentioned before cron in automation suggestions. However, Linux examples are present and functional throughout.
Recommendations
- Alternate the order of platform examples, sometimes listing Linux/macOS first.
- Provide equal detail and prominence to Linux/macOS tools (e.g., mention cron before Windows Task Scheduler, or side-by-side).
- Include bash or shell script examples before or alongside Windows batch/PowerShell scripts.
- Consider grouping platform-specific instructions together or using tabs, rather than always listing Windows first.
- Explicitly state that all platforms are equally supported at the beginning of the documentation.
Azure Arc
Azure Arc-enabled data services validation
...lob/main/articles/azure-arc/data/validation-program.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias, primarily through the inclusion of Windows-centric partner solutions (e.g., Azure Stack HCI, AKS-HCI) and tools (Azure Data Studio, azdata CLI) that are most commonly used on Windows. Windows-based Kubernetes solutions are listed before Linux-based equivalents in some partner sections (e.g., Hitachi UCP with Microsoft AKS-HCI before Red Hat OpenShift). However, the page does include Linux-compatible distributions (Red Hat OpenShift, Kublr, VMware, Wind River) and does not provide command-line examples that are exclusive to Windows or PowerShell.
Recommendations
- Explicitly mention Linux compatibility for all listed tools (e.g., azdata CLI, Azure Data Studio) and provide installation links for both Windows and Linux.
- Ensure partner solutions are grouped or ordered in a way that does not prioritize Windows-based solutions over Linux-based ones.
- Add example workflows or validation steps using Linux-native tools and environments (e.g., bash, Linux package managers) alongside any Windows-specific instructions.
- Clarify platform support in the prerequisites section, including how to generate and use Kubernetes config files on both Windows and Linux.
- If possible, add references to Linux-specific distributions or community Kubernetes solutions to further balance the partner list.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Linux First
Summary
The documentation provides automation examples using Linux shell scripting and mentions Linux/Mac script extensions before Windows equivalents. Windows automation tools (Task Scheduler, .cmd/.bat/.ps1) are referenced, but only after Linux options. There are no PowerShell-specific examples or Windows-first command patterns. The primary command-line examples use Azure CLI, which is cross-platform. Overall, the page leans slightly toward Linux in example ordering and scripting, but does mention Windows tools for parity.
Recommendations
- Add explicit PowerShell script examples for automating uploads on Windows.
- Provide step-by-step instructions for using Windows Task Scheduler to run the upload script.
- Include notes on running Azure CLI commands in Windows environments (e.g., using Command Prompt, PowerShell).
- Ensure that both Linux and Windows automation options are presented with equal detail and prominence.
- Consider adding screenshots or walkthroughs for both Linux cron and Windows Task Scheduler setups.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively providing instructions and screenshots for the Azure portal and Azure Managed Grafana interfaces, without offering any Linux-native or cross-platform CLI examples (such as kubectl, bash, or Linux monitoring tools). The workflow assumes users interact primarily with Azure's graphical tools, which are most commonly accessed from Windows environments, and does not mention or prioritize Linux-native approaches for monitoring Edge RAG metrics.
Recommendations
- Add Linux-native examples for monitoring Edge RAG metrics, such as using kubectl, Prometheus, or bash scripts.
- Include CLI instructions (e.g., Azure CLI, kubectl) alongside or before GUI-based steps to ensure parity for Linux users.
- Reference open-source monitoring tools (e.g., Prometheus, Grafana on Linux) and provide setup instructions for non-Azure environments.
- Ensure screenshots and walkthroughs are not exclusively from Windows-based Azure portal interfaces; consider including examples from Linux terminals or web-based tools.
- Explicitly mention platform-agnostic steps and clarify any platform-specific requirements or limitations.
Azure Arc
Quickstart: Install Edge RAG on Azure Kubernetes Service
...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the 'Connect to the developer portal' section, where instructions for updating the hosts file are given only for Windows (using Notepad and the Windows file path). There are no equivalent instructions for Linux or macOS users. Additionally, the mention of 'Switch to PowerShell' in Azure Cloud Shell is presented before any mention of Bash, and all variable assignment and command continuation examples use PowerShell-style syntax (e.g., `$var = ...`, backticks for line continuation), which may not work in Bash shells commonly used on Linux/macOS.
Recommendations
- Add parallel instructions for updating the hosts file on Linux and macOS (e.g., using sudo and a text editor like nano or vim to edit /etc/hosts).
- Include Bash shell examples for variable assignment and command continuation, or clarify which shell is being used in each example.
- When referencing Azure Cloud Shell, mention Bash as an option and provide guidance for both PowerShell and Bash users.
- Ensure all file paths and tool usage are cross-platform, or provide platform-specific instructions where necessary.
Azure Arc
Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to query and analyze the installation status of databases such as SQL Server, PostgreSQL, or MySQL, so that I can ensure compliance and optimize resource allocation."
...ticles/azure-arc/includes/azure-arc-enabled-servers.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query, but PowerShell is always presented as a primary tab alongside CLI, and there is no mention of Linux-specific shell usage (e.g., Bash) or Linux-native tools. The PowerShell examples may imply a Windows-centric workflow, and there is no explicit guidance or parity for Linux users beyond the CLI, which is cross-platform but not highlighted as such.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell examples or notes for Linux users.
- Add a 'Bash' or 'Linux shell' tab alongside PowerShell to demonstrate usage in a Linux environment, including any differences in escaping or command syntax.
- Clarify that PowerShell is available cross-platform, but also mention that Linux users may prefer Bash or other shells.
- Where relevant, discuss any OS-specific considerations (e.g., agent installation, file paths, environment variables) for both Windows and Linux.
- Ensure that documentation language and examples do not assume a Windows-first audience, and highlight Linux parity where possible.
Azure Arc
Customer intent: "As a cloud administrator, I want to understand how to get the region segment of regional endpoints , so that I can configure Azure services in specific regions without errors."
...ob/main/articles/azure-arc/includes/arc-region-note.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions. However, the PowerShell example is given directly after the CLI example, and PowerShell is a Windows-centric tool, which may suggest a slight Windows bias. There are no Linux-specific shell examples (e.g., Bash, grep, jq), nor is there explicit mention of Linux tools or patterns.
Recommendations
- Add a Bash example using Azure CLI, such as `az account list-locations --query "[].name" -o tsv`.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- If PowerShell is mentioned, note that it is available cross-platform, but most Linux users prefer Bash.
- Consider listing the Azure CLI example first, as it is more universally applicable.
Azure Arc
Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/extensions-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While most troubleshooting steps use cross-platform tools like Azure CLI, kubectl, and helm, the only OS-specific troubleshooting guidance is for Linux (Oracle Linux/RHEL 9.x) in the AMA section. However, the documentation consistently refers to Azure CLI (which is available on Windows, macOS, and Linux) and does not provide any PowerShell or Windows-specific examples. The only notable Windows bias is the use of Azure CLI commands, which are often presented as the primary method for troubleshooting Azure resources, and the lack of explicit Linux shell examples (e.g., bash scripting for automation). There are no Linux-first troubleshooting flows, and Windows tools (Azure CLI, juju, etc.) are mentioned before any Linux-native alternatives.
Recommendations
- Add explicit Linux shell (bash) examples for common troubleshooting automation tasks, such as looping over resources or parsing output.
- Where Azure CLI is used, clarify that it is cross-platform and provide alternative commands for users who prefer native Linux tools (e.g., kubectl, jq, grep, awk).
- Include troubleshooting steps or examples for Linux-specific environments (such as SELinux, AppArmor, or systemd) where relevant.
- If PowerShell or Windows-specific tools are mentioned, ensure Linux equivalents are provided and presented with equal prominence.
- Consider adding a section or callout for Linux users highlighting any OS-specific considerations, especially for extension installation and resource management.
Azure Arc
Azure Resource Graph sample queries for Azure Arc-enabled Kubernetes
...rticles/azure-arc/kubernetes/resource-graph-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing ways to run queries, which can suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux examples or references to Linux-specific tools or shell environments. The mention of Azure PowerShell and the lack of Bash or Linux terminal examples may make the documentation less approachable for Linux users.
Recommendations
- List Azure CLI before Azure PowerShell when describing cross-platform options, as CLI is natively supported on both Windows and Linux.
- Include explicit examples of running queries in Bash or Linux terminal environments.
- Clarify that Azure CLI and Resource Graph Explorer are fully supported on Linux and macOS.
- Add a note or section highlighting cross-platform compatibility and usage for Linux users.
Azure Arc
Azure Arc resource bridge maintenance operations
...main/articles/azure-arc/resource-bridge/maintenance.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation does not provide explicit examples or instructions for Linux environments. All command-line instructions reference the Azure CLI, but there are no examples of Linux-specific shell usage, nor is there any mention of Linux tools or patterns. The appliance VM credential update references VMware and SCVMM, both of which are commonly managed from Windows environments. There is no mention of Linux-based management workflows, nor are Linux shell commands or PowerShell alternatives discussed.
Recommendations
- Include explicit Linux shell (bash) examples for CLI commands, demonstrating usage on Linux management machines.
- Clarify whether the Azure CLI commands are cross-platform and provide any Linux-specific prerequisites or troubleshooting steps.
- Mention Linux-compatible tools and workflows for managing the appliance VM, especially for credential updates and proxy configuration.
- Add guidance for Linux administrators, such as how to automate maintenance tasks using cron or shell scripts.
- Ensure parity in examples and instructions for both Windows and Linux environments, including any differences in file paths, environment variables, or authentication methods.
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Arc resource bridge system requirements demonstrates Windows bias by referencing Azure CLI installation with a direct link to the Windows installation page and specifying 32-bit/64-bit requirements without clarifying Linux or macOS equivalents. There are no explicit Linux or macOS management machine examples, nor are there instructions or links for installing Azure CLI on those platforms. All CLI usage examples and requirements are presented generically, but the installation guidance is Windows-centric.
Recommendations
- Provide explicit instructions and links for installing Azure CLI on Linux and macOS, alongside Windows.
- Clarify whether the 32-bit/64-bit requirements apply to Linux/macOS, or provide platform-specific guidance.
- Include example CLI commands run on Linux/macOS, or note any differences in usage or prerequisites.
- Ensure that references to management machine requirements mention support for Linux and macOS, not just Windows.
- Add parity in troubleshooting and credential update instructions for non-Windows platforms.
Azure Arc
Programmatically deploy and manage Azure Arc Extended Security Updates licenses
...les/azure-arc/servers/api-extended-security-updates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused exclusively on managing Extended Security Updates licenses for Windows Server 2012 and 2012 R2. All examples and API payloads reference Windows-specific targets, and there is no mention of Linux systems, Linux-specific license management, or examples for Linux servers. The customer intent and all command parameters are tailored to Windows environments, with no Linux parity or guidance.
Recommendations
- Add examples and instructions for managing ESU licenses for Linux servers, if supported.
- Clarify whether the APIs and Azure CLI commands can be used for Linux workloads, and provide Linux-specific parameter values or scenarios.
- Include Linux-specific documentation sections or cross-references if the feature is Windows-only, to help users understand platform limitations.
- If Linux is not supported, explicitly state this in the documentation to avoid confusion.
Azure Arc
Azure Resource Graph sample queries for Azure Arc
...blob/main/articles/azure-arc/resource-graph-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a primary method for running queries, which is a Windows-centric tool, and lists it before Azure CLI. There are no explicit examples or instructions for running queries on Linux systems, nor are Linux-specific tools or shell environments referenced. The documentation does not provide parity in guidance for Linux users.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide examples using bash or other common Linux shells.
- Include instructions or examples for running queries in Linux environments, such as using Azure CLI in bash.
- Avoid listing Windows-centric tools (like PowerShell) before cross-platform alternatives unless contextually justified.
- Reference Linux-native tools or environments where appropriate, and clarify platform compatibility for each method.
Azure Arc
Extensions security for Azure Arc-enabled servers
...main/articles/azure-arc/servers/security-extensions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides parity between Windows and Linux, but there is a consistent pattern of presenting Windows examples and commands before Linux equivalents. In example sections, Windows (PowerShell) commands are listed first, and Linux commands follow. There is also a slight emphasis on Windows-specific terminology (e.g., 'elevated command console') and references to Windows contexts (Local System) before Linux (root). However, Linux examples are present and not omitted.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Use neutral terminology when describing user contexts (e.g., 'administrator/root') rather than listing Windows first.
- Ensure that all example commands are provided for both platforms, and avoid giving the impression that Windows is the default or primary environment.
- Where possible, use platform-agnostic instructions before platform-specific details.