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 501-525 of 2334 flagged pages
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/how-to-stage.md
...icles/azure-arc/workload-orchestration/how-to-stage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring cross-platform coverage. However, there are signs of Windows bias: PowerShell examples are given equal prominence to Bash, even for tasks that are not Windows-specific (e.g., Docker, kubectl, az CLI, which are cross-platform). Some PowerShell examples use Windows-specific patterns (e.g., Out-File, [Convert]::ToBase64String), and the instructions for editing files mention UTF-8 BOM encoding, which is primarily a Windows concern. There are no Linux-specific troubleshooting notes, and some PowerShell commands (e.g., armclient) are Windows-centric without Linux equivalents. The documentation does not provide explicit Linux-only examples or address Linux-specific edge cases.
Recommendations
- Add explicit notes or troubleshooting sections for Linux users, such as handling file permissions, line endings, or common issues with az CLI, Docker, or kubectl on Linux.
- Where PowerShell is used for file manipulation or encoding, provide equivalent Bash/Linux commands (e.g., for base64 encoding, file writing, or JSON formatting).
- Clarify that PowerShell examples are intended for Windows users, and Bash for Linux/macOS, to avoid confusion.
- If referencing tools like armclient, mention Linux alternatives or note cross-platform compatibility.
- Include Linux-specific tips for editing files (e.g., using vim, nano, or sed for encoding changes) and troubleshooting UTF-8/BOM issues.
- Consider providing a 'Linux Quick Start' or 'Linux-specific considerations' section for users deploying on Linux edge clusters.
Create Pull Request
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/whats-new.md
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias: Windows-specific features (e.g., customizing Windows VM guest OS settings, Windows Server Management, Extended Security Updates for Windows Server) are highlighted, and Windows tools (PowerShell, System Center Configuration Manager, Group Policy) are mentioned explicitly. Linux is referenced only once (Arc agent installation via SSH), and there are no Linux-specific management tools or examples provided. Windows tools are listed before Linux equivalents, and some features appear exclusive to Windows environments.
Recommendations
- Include equivalent Linux management examples and tools (e.g., shell scripts, Linux configuration management tools like Chef/Puppet/SaltStack).
- Provide parity in feature descriptions, such as guest OS customization for Linux VMs.
- List Linux and cross-platform tools alongside Windows tools, not after or instead of them.
- Add explicit Linux-focused sections or callouts where Windows-specific features are described.
- Ensure that SDK and CLI examples include both Windows and Linux usage scenarios.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/onboarding-scripts.md
...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All script examples use PowerShell (.ps1 files) and instruct users to open a PowerShell terminal. Prerequisites rely on Windows-specific tools like winget, and there are no Bash or Linux shell equivalents provided. No mention is made of how to run these scripts or set up the environment on Linux or macOS, nor are cross-platform alternatives discussed.
Recommendations
- Provide Bash shell script equivalents (.sh) for infra and cm onboarding, or document how to run the PowerShell scripts on Linux/macOS using pwsh (PowerShell Core).
- Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or direct downloads), not just winget.
- Add explicit notes about cross-platform compatibility of the onboarding scripts, and clarify any Windows-only limitations.
- Present Linux/macOS examples alongside Windows/PowerShell examples, or at least mention them in parallel.
- Consider reordering sections or examples so that Windows and Linux instructions are presented together, rather than Windows-first.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/migration-script.md
...s/azure-arc/workload-orchestration/migration-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell migration script example, referencing a .ps1 file (PowerShell script), and instructing users to run the script in PowerShell. There are no Linux shell (bash/sh) equivalents or instructions for running the migration on Linux or macOS systems. The documentation assumes the use of Windows tools and does not mention cross-platform alternatives.
Recommendations
- Provide a bash or shell script alternative for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core on non-Windows platforms.
- Explicitly mention cross-platform compatibility of the migration script, including any prerequisites for running PowerShell scripts on Linux/macOS.
- Include example commands for Linux/macOS environments, such as using pwsh (PowerShell Core) or bash.
- Clarify whether the migration process is supported on Linux/macOS and provide troubleshooting steps for those platforms.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/backup-controller-database.md
.../articles/azure-arc/data/backup-controller-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing command-line examples using PowerShell syntax and conventions (e.g., using double quotes for parameters, explicit mention of PowerShell blocks), without offering equivalent Linux shell (bash) examples. The SQL Server connectivity and restore commands are shown only in PowerShell context, and there is no mention of Linux-specific tools or patterns, despite the fact that Kubernetes and SQL Server on Linux are common in Azure Arc deployments. This may make the instructions less accessible to Linux users.
Recommendations
- Provide equivalent bash shell examples for all PowerShell commands, especially for connecting to the SQL Server pod and running sqlcmd.
- Clarify that the commands work on both Windows and Linux, and note any platform-specific differences (e.g., quoting, path separators).
- Avoid labeling command blocks as 'powershell' unless they are truly PowerShell-specific; use 'console' or 'bash' where appropriate.
- Mention Linux tools (such as base64 decoding with 'base64 -d') alongside generic instructions.
- Add a note or section explicitly addressing Linux users and their workflow.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/single-node-edge-essentials.md
...tainer-storage/includes/single-node-edge-essentials.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation, while focused on Linux preparation, repeatedly uses Windows-centric tools and patterns. For example, it instructs users to open configuration files in Notepad (a Windows application), and uses the Invoke-AksEdgeNodeCommand cmdlet, which is a PowerShell/Windows-specific command, to interact with Linux nodes. There is no mention of Linux-native alternatives (e.g., nano, vi, direct SSH, or bash commands), and Windows/PowerShell tools are presented as the default method for managing Linux systems.
Recommendations
- Provide Linux-native command-line alternatives for all management steps, such as using SSH and bash commands directly instead of PowerShell cmdlets.
- Replace references to Notepad with Linux text editors like nano, vi, or vim, or suggest cross-platform editors.
- Clarify when Windows tools are required and offer equivalent Linux workflows, ensuring users on Linux-only environments can follow the documentation.
- Reorder examples so that Linux-native approaches are presented first or in parallel with Windows/PowerShell methods.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/choose-service.md
...nt-docs/blob/main/articles/azure-arc/choose-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific tools and terminology (e.g., SCVMM, Windows Server, SQL Server, Azure VMware Solution) are mentioned frequently and often before Linux equivalents. PowerShell is referenced as a primary automation tool, with no explicit Linux shell or scripting examples. Extended Security Updates are discussed only for Windows Server and SQL Server. There is a lack of Linux-specific examples, recommendations, or tooling throughout the document, and most onboarding and integration instructions reference Windows-centric workflows.
Recommendations
- Include Linux-specific onboarding and management examples, such as shell scripts or Ansible playbooks, alongside PowerShell.
- Highlight Linux management scenarios and capabilities (e.g., patching, monitoring, security) with equal detail as Windows.
- Mention Linux distributions and their support explicitly in tables and feature lists.
- Provide links to Linux-focused documentation and onboarding guides.
- Balance references to Windows tools (SCVMM, PowerShell) with Linux equivalents (e.g., libvirt, cloud-init, bash scripting).
- Discuss security and update management for Linux systems, not just Windows Extended Security Updates.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/multi-node-edge-essentials.md
...ntainer-storage/includes/multi-node-edge-essentials.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell-based examples (Invoke-AksEdgeNodeCommand) for configuring Linux nodes. It uses Windows-centric tooling to execute Linux commands, without showing direct Linux shell commands or instructions for users working natively on Linux. There are no bash or shell script examples, and the workflow assumes a Windows management environment.
Recommendations
- Provide direct Linux shell command examples alongside PowerShell examples, so users managing Linux nodes natively can follow the instructions.
- Include instructions for running these commands locally on Linux (e.g., using bash or SSH), not just via Windows-based tools.
- Clarify when Windows tools are required and offer Linux-native alternatives for each step.
- Consider reordering examples so that Linux-native instructions appear first, or at least in parallel with Windows/PowerShell methods.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/automated-integration-testing.md
...ticles/azure-arc/data/automated-integration-testing.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific issues (CRLF vs LF line endings) are discussed in detail, with screenshots and instructions for VSCode, but no equivalent Linux/Mac guidance is provided. Azure CLI examples are shown in PowerShell terminals, and screenshots are Windows-centric. There is no mention of Linux tools for line ending conversion, nor are Linux/Mac terminal screenshots or instructions included. The order of presentation often assumes a Windows environment first, with Linux compatibility as an afterthought.
Recommendations
- Provide explicit instructions and examples for Linux and Mac users, including terminal screenshots and tooling (e.g., using 'dos2unix' for line ending conversion).
- Include guidance for Linux/Mac users on editing files, such as using 'nano', 'vim', or 'sed' to ensure LF line endings.
- Balance screenshots between Windows and Linux/Mac environments to ensure parity.
- When discussing Azure CLI usage, show examples in both PowerShell (Windows) and Bash (Linux/Mac) terminals.
- Avoid assuming Windows as the default environment; structure instructions to address both platforms equally or in parallel.
- Mention cross-platform editors and tools (e.g., VSCode, nano, vim) and how to check/convert line endings in each.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-data-controller-direct-prerequisites.md
...rc/data/create-data-controller-direct-prerequisites.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and there are no Linux shell-specific examples (e.g., bash scripts). The installation instructions for Azure CLI and Helm are platform-neutral, but the presence of PowerShell commands and lack of Linux-specific alternatives or notes may suggest a Windows bias. The document does not mention Linux-specific tools or patterns, nor does it provide troubleshooting or environment setup guidance for Linux users.
Recommendations
- Add explicit bash/Linux shell examples for all commands, especially for connecting clusters and verifying pods.
- Clarify that Azure CLI and Helm are cross-platform and provide installation instructions for both Windows and Linux.
- If PowerShell is included, also include equivalent bash scripts or Linux command-line alternatives.
- Add troubleshooting notes or environment setup guidance for Linux users (e.g., common issues with az CLI on Linux, permissions, etc.).
- Order examples with platform-neutral or Linux-first commands before Windows/PowerShell examples to avoid implicit prioritization.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/active-directory-prerequisites.md
...icles/azure-arc/data/active-directory-prerequisites.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All examples and instructions for Active Directory object creation and management are provided using Windows tools (Active Directory Users and Computers GUI, PowerShell). The only automation example is in PowerShell, and there is no mention of Linux-compatible methods (such as using Samba, ldapadd, or other CLI tools). The prerequisite steps assume a Windows-based domain controller and link to a Windows Server-specific guide. No Linux or cross-platform alternatives are discussed.
Recommendations
- Add instructions for managing Active Directory objects using cross-platform tools (e.g., ldapadd, ldapmodify, Samba's net utility) that can be run from Linux.
- Include examples for creating OUs and users using Linux CLI tools or scripts.
- Reference guides for setting up Active Directory-compatible services on Linux (such as Samba AD DC) where appropriate.
- Clarify whether a Windows Server domain controller is strictly required, or if Linux-based AD-compatible controllers are supported.
- Provide parity in screenshots and step-by-step instructions for Linux environments where possible.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows file paths in command outputs, omitting Linux-specific examples or notes, and implicitly assuming a Windows environment for users. All examples and outputs use Windows conventions (e.g., backslashes in file paths), and there is no mention of Linux or macOS equivalents, nor guidance for users on those platforms.
Recommendations
- Provide example outputs and instructions for both Windows and Linux/macOS environments, especially for file paths (e.g., ~/.kube/config for Linux/macOS).
- Explicitly mention that the Azure CLI, kubectl, and Azure Data Studio are cross-platform, and provide installation or usage notes for Linux/macOS users.
- Where command outputs differ by OS (such as file paths), show both variants or clarify with a note.
- Ensure that screenshots and UI references are not specific to Windows unless unavoidable, and add clarifying notes for Linux/macOS users as needed.
- Add a section or callout for Linux/macOS users highlighting any differences or additional steps required.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance-cli.md
...ta/deploy-active-directory-sql-managed-instance-cli.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive focus on Active Directory (AD) integration, which is a Windows-centric technology. All examples and instructions assume AD as the identity provider, with no mention of Linux-native alternatives (such as LDAP or Kerberos realms not backed by AD). The documentation does not provide guidance for Linux-based identity management or integration patterns, nor does it offer parity for Linux environments that do not use AD. The terminology and prerequisites are oriented toward Windows tools and infrastructure, and there are no Linux-first or cross-platform authentication examples.
Recommendations
- Include examples and guidance for integrating SQL Managed Instance with Linux-native identity providers (e.g., OpenLDAP, MIT Kerberos).
- Add documentation sections that explain how to deploy and manage SQL Managed Instance in environments without Active Directory, highlighting Linux authentication options.
- Clarify prerequisites to indicate whether AD is mandatory or if alternatives are supported, and provide links to relevant Linux documentation if available.
- Balance terminology and instructions to reference both Windows and Linux tools where applicable, or explicitly state platform limitations.
- If AD is the only supported option, clearly state this limitation and provide rationale, while suggesting workarounds or future roadmap for Linux parity.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/configure-transparent-data-encryption-manually.md
...data/configure-transparent-data-encryption-manually.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Path Examples
Summary
The documentation shows mild Windows bias by presenting Windows-specific instructions and examples before Linux equivalents in each tabbed section. Windows command-line tools and path conventions (e.g., 'type', '$HOME\sqlcerts\...') are used, and Windows-specific issues (such as kubectl cp path problems) are highlighted in notes. Linux instructions are present and correct, but are consistently listed after Windows, and Windows pathing is used in examples more prominently.
Recommendations
- Alternate the order of Windows and Linux tabs so Linux is sometimes presented first.
- Provide a general note at the top clarifying cross-platform support and parity, rather than only warning about Windows-specific issues.
- Use neutral path examples (e.g., $HOME/sqlcerts/servercert.crt) in generic instructions, and only show platform-specific paths in their respective tabs.
- Where possible, use platform-agnostic commands or highlight when commands work identically on both platforms.
- Explicitly mention PowerShell only if it is required, and provide Bash equivalents if scripting is discussed.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance.md
...c/data/deploy-active-directory-sql-managed-instance.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-centric tools and patterns are referenced first or exclusively in several key steps, such as using 'Active Directory Users and Computers' for account creation and 'setspn' for SPN registration, both of which are Windows-only utilities. The process for generating keytab files does mention Linux tools and scripts, but Windows tools (like 'ktpass' and a PowerShell script) are listed alongside or before Linux equivalents. There is no explicit Linux example for creating the Active Directory account or registering SPNs, and the documentation assumes access to a Windows domain controller for these steps.
Recommendations
- Provide explicit Linux-based alternatives for all steps, especially for creating Active Directory accounts and registering SPNs (e.g., using 'adutil' or 'ldapadd' for account creation, and 'adutil spn' for SPN registration).
- List Linux tools and scripts before or alongside Windows tools, rather than after.
- Include example commands for Linux environments where possible, not just for keytab generation but also for other Active Directory interactions.
- Clarify which steps require Windows-only tools and suggest cross-platform or open-source alternatives where feasible.
- Add a section or note on how to perform prerequisite steps (such as account and SPN creation) from a Linux or non-Windows environment, referencing official Microsoft documentation for 'adutil' and other relevant tools.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connect-managed-instance.md
...in/articles/azure-arc/data/connect-managed-instance.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools (SQL Server Management Studio, Azure Data Studio) and workflows, mentioning them before Linux alternatives. There is a lack of explicit Linux client examples and no mention of Linux-native SQL tools (e.g., DBeaver, SquirrelSQL, or command-line utilities beyond sqlcmd). The special instructions for Azure VM networking and NSG configuration are presented using Azure CLI, which is cross-platform, but the overall workflow assumes familiarity with Windows environments and tools. Linux connection patterns and troubleshooting are not covered.
Recommendations
- Include explicit examples for connecting from Linux-based SQL clients (e.g., DBeaver, SquirrelSQL, isql).
- Provide step-by-step instructions for Linux users, including installation and usage of sqlcmd on Linux.
- Mention Linux-native alternatives to SQL Server Management Studio and Azure Data Studio.
- Add troubleshooting tips for Linux networking and firewall configuration, such as using iptables or ufw.
- Ensure that all connection examples are shown for both Windows and Linux environments, with clear distinctions where necessary.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-system-managed-keytab-active-directory-connector.md
...eploy-system-managed-keytab-active-directory-connector.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' for identifying the primary domain controller) without offering Linux alternatives. Windows terminology and patterns (NetBIOS, pre-Windows 2000 name) are used throughout, and Windows-based methods are presented first or exclusively. There are no examples or guidance for performing equivalent tasks on Linux systems, such as querying AD domain controllers or managing service accounts.
Recommendations
- Provide Linux-based alternatives for Active Directory domain controller discovery, such as using 'ldapsearch' or 'adcli' commands.
- Include examples and instructions for querying and managing AD from Linux environments, especially for administrators who may not have access to Windows machines.
- Balance terminology by referencing both Windows and Linux tools and patterns where applicable.
- Add notes or links to cross-platform tools for AD management (e.g., Samba, Kerberos utilities) to improve accessibility for Linux users.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-high-availability.md
...s/azure-arc/data/managed-instance-high-availability.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-centric tools such as SQL Server Management Studio (SSMS) for connecting and managing SQL Managed Instances, without mentioning Linux-native alternatives. Examples and instructions for connecting to the SQL instance and verifying high availability status are provided using SSMS, a Windows-only tool, and no Linux equivalents (such as Azure Data Studio or sqlcmd) are suggested. The documentation also refers to connecting from SSMS before mentioning any cross-platform options, and does not provide explicit examples for Linux users. There are no PowerShell-heavy examples, but the overall pattern favors Windows tooling and omits Linux-native workflows.
Recommendations
- Include instructions and examples for connecting to SQL Managed Instance using cross-platform tools such as Azure Data Studio and sqlcmd.
- Explicitly mention Linux-compatible alternatives wherever SSMS is referenced, and provide equivalent command-line examples.
- Add a section or note highlighting how Linux users can perform all management and monitoring tasks without requiring Windows-only tools.
- Ensure that examples and tool recommendations are presented in a platform-neutral order, or with Linux-first parity.
- Where file paths or commands are given, clarify any platform-specific differences (e.g., path separators, file locations) for Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/resize-persistent-volume-claim.md
...icles/azure-arc/data/resize-persistent-volume-claim.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the PVC patching step, where the example uses a PowerShell variable assignment syntax ($newsize='...') to construct the JSON patch. This approach is specific to PowerShell and Windows environments, and no equivalent Linux shell (bash) example is provided. The rest of the commands use kubectl, which is cross-platform, but the patching step may confuse Linux users or those using bash, as the variable assignment and quoting are not portable.
Recommendations
- Provide a Linux/bash-compatible example for the PVC patching step, e.g., using bash variable assignment and proper quoting.
- Clarify that the $newsize variable assignment is for PowerShell, and offer alternative syntax for bash/zsh users.
- Review all command examples to ensure they are platform-neutral or offer both Windows and Linux variants where necessary.
- Add a note or table summarizing command differences between Windows (PowerShell) and Linux (bash) environments for common tasks.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-customer-managed-keytab.md
...icles/azure-arc/data/rotate-customer-managed-keytab.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits Windows bias by referencing Windows-specific tools (ktpass.exe), providing PowerShell scripts, and detailing password reset steps using Windows GUI tools (Server Manager, Active Directory Users and Computers). While a bash script is mentioned, the Windows approach (PowerShell/ktpass.exe) is listed alongside and Windows GUI instructions are given for password changes, with no Linux or cross-platform alternatives for domain management. There is no mention of Linux-based Active Directory management or equivalent CLI tools for password resets.
Recommendations
- Provide explicit Linux-based instructions for resetting Active Directory passwords, such as using 'samba-tool' or 'ldapmodify' on Linux domain controllers.
- List Linux/bash examples before or alongside Windows/PowerShell examples to avoid Windows-first ordering.
- Mention Linux equivalents for Windows tools like 'ktpass.exe', such as 'ktutil' or 'adutil', and clarify their usage.
- Include screenshots or CLI output for Linux-based management tools where Windows GUI screenshots are used.
- Clarify which steps are platform-specific and offer parity for both Windows and Linux environments.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-features.md
...n/articles/azure-arc/data/managed-instance-features.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows Authentication
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (SSMS, SQL Server Data Tools, SQL Server Profiler, PowerShell scripting) and features (Windows Authentication) without mentioning Linux equivalents or alternatives. PowerShell scripting is highlighted as a manageability feature, and Windows Authentication is listed as supported, while there is no mention of Linux authentication mechanisms or scripting environments (e.g., Bash). There are no examples or guidance for Linux users, and the order of tool presentation favors Windows-centric utilities.
Recommendations
- Include examples and guidance for Linux environments, such as Bash scripting, and reference Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux).
- Clarify authentication options for Linux users, such as Kerberos or Microsoft Entra ID, and document any limitations or alternatives to Windows Authentication.
- Present cross-platform tools first (e.g., Azure Data Studio, Azure CLI) before Windows-only tools to avoid implicit prioritization.
- Explicitly state platform compatibility for each tool and feature, and provide links to Linux installation and usage guides where available.
- Add notes or sections highlighting differences and best practices for managing SQL Managed Instance enabled by Azure Arc on Linux.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/privacy-data-collection-and-reporting.md
...zure-arc/data/privacy-data-collection-and-reporting.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows is explicitly referenced in billing data examples (osType: Windows), and the example host is 'Hyper-V', a Windows virtualization technology. There are no Linux-specific examples, nor is Linux mentioned as an alternative in scenarios where OS type is relevant. The documentation also references SQL Server, which is traditionally Windows-centric, without clarifying Linux support or providing parity examples. No Linux tools, patterns, or OS-specific guidance are provided, and Windows appears as the default or only context in examples.
Recommendations
- Provide explicit Linux examples alongside Windows examples, especially in billing data and resource inventory sections (e.g., osType: Linux, manufacturer: Dell, model: PowerEdge, etc.).
- Clarify that Azure Arc-enabled data services support both Windows and Linux hosts, and describe any differences in data collection or reporting.
- Include Linux-relevant tools and patterns (e.g., mention systemd, journalctl, or Linux VM types) where applicable.
- Ensure that examples and sample JSON documents alternate or include both Windows and Linux scenarios.
- Add a section or note on cross-platform support and any OS-specific considerations for data collection and reporting.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-logs.md
...-docs/blob/main/articles/azure-arc/data/upload-logs.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Linux Parity Good
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and macOS/Linux, with Windows examples consistently presented first. Windows-specific tools (SET, Task Scheduler, .cmd/.bat/.ps1 scripts) are mentioned alongside Linux equivalents. However, Linux and macOS are well-represented, with shell script automation, use of cron, and explicit export commands. The overall parity is good, but the ordering and some tool mentions show a subtle Windows bias.
Recommendations
- Alternate the order of platform examples, sometimes listing Linux/macOS first to avoid implicit prioritization of Windows.
- Provide more detailed Linux automation examples (e.g., sample cron job entries) alongside Windows Task Scheduler instructions.
- Where possible, use platform-neutral language and tools first (e.g., 'export' for environment variables, then show platform-specific alternatives).
- Include explicit notes that all steps are equally supported on Linux/macOS and Windows, to reinforce parity.
- Consider grouping automation script examples by platform, rather than listing Windows formats first.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics.md
...cs/blob/main/articles/azure-arc/data/upload-metrics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are consistently provided and often appear before Linux/macOS equivalents. Windows-specific tools and patterns (e.g., PowerShell environment variables, Windows Task Scheduler) are mentioned explicitly. In some sections, the Windows tab is marked as 'N/A', implying missing or incomplete Windows-specific guidance, while Linux/macOS instructions are more detailed. Automation examples focus on Linux shell scripting, with only brief mentions of Windows automation tools, and no concrete Windows script examples are given.
Recommendations
- Provide concrete Windows automation script examples (e.g., .bat, .cmd, or PowerShell .ps1) alongside Linux shell scripts.
- Ensure all CLI examples are available for both Windows and Linux/macOS, with clear instructions for each platform.
- Mention Windows Task Scheduler and provide step-by-step guidance or examples for scheduling uploads on Windows, not just Linux cron/βwatchβ.
- Avoid marking Windows tabs as 'N/A' unless functionality is truly unavailable; otherwise, supply equivalent commands or note platform limitations.
- Present platform examples in parallel, rather than always listing PowerShell/Windows first, to avoid implicit prioritization.
Azure Arc
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows and PowerShell examples are given explicit tabs and are often listed before Linux/macOS equivalents. Windows-specific notes (such as quoting conventions) are called out, and PowerShell environment variable syntax is included as a separate tab. The 'Related content' section links to a PowerShell-specific guide for service principals, rather than a cross-platform or CLI-focused resource. However, Linux/macOS examples are present and reasonably complete.
Recommendations
- Ensure Linux/macOS examples are given equal prominence, possibly listing Linux/macOS first or side-by-side with Windows.
- Provide links to cross-platform Azure CLI documentation in 'Related content', not just PowerShell guides.
- Clarify that all CLI commands work equally on Linux/macOS/Windows, and avoid implying Windows is the default platform.
- Where quoting or syntax differences exist, explain them in a neutral way without prioritizing Windows.
- Consider merging PowerShell and Windows tabs if the commands are identical, or clarify when PowerShell is required versus standard CLI.