Storage
688
Total Pages
395
Linux-Friendly Pages
293
Pages with Bias
42.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1657 issues found
Showing 226-250 of 1657 flagged pages
Storage
Quickstart: Azure Blob storage library - TypeScript
...ge/blobs/storage-quickstart-blobs-nodejs-typescript.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. Windows tools (cmd, PowerShell, Visual Studio Code) are mentioned first or exclusively in several places, such as project setup and authentication. PowerShell is given its own authentication tab, while Linux equivalents are less emphasized or appear after Windows instructions. The use of Visual Studio Code is presented as the default editor, which is more common on Windows. However, Linux commands and instructions are present, and Bash is mentioned alongside Windows consoles.
Recommendations
- Present Linux and Windows instructions side-by-side or in parallel, rather than listing Windows first.
- Include Linux-native editors (e.g., Vim, nano) as alternatives to Visual Studio Code in setup steps.
- Provide Bash and Linux terminal examples with equal prominence to cmd/PowerShell.
- Add explicit instructions for MacOS where relevant.
- Ensure authentication instructions (Azure CLI, PowerShell) are clearly labeled for each OS, and avoid giving Windows tools priority.
- Consider a table or tabbed layout for OS-specific commands to avoid implicit prioritization.
Create Pull Request
Storage
Prevent authorization with Shared Key
...les/storage/common/shared-key-authorization-prevent.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows-centric tools and workflows first or exclusively. PowerShell is given its own example tab, and instructions reference the Azure portal (a GUI primarily used on Windows) and Azure PowerShell before Azure CLI. Screenshots and step-by-step instructions are tailored to the Azure portal, which is most commonly accessed from Windows environments. There are no explicit Linux shell or scripting examples, nor is there mention of Linux-specific tooling or workflows.
Recommendations
- Add explicit Linux shell (bash) examples for key operations, such as using Azure CLI from a Linux terminal.
- Include notes or screenshots demonstrating the same procedures on Linux systems, especially for Azure CLI usage.
- Clarify that Azure CLI commands work cross-platform and provide guidance for Linux package installation and environment setup.
- Consider adding a section or tab for Linux users, outlining any differences or considerations when managing Azure Storage from Linux.
- Balance the order of presentation so that Azure CLI (cross-platform) is listed before PowerShell, or present both together to avoid implying Windows-first workflows.
Storage
Determine which encryption key model is in use for the storage account
...les/storage/common/storage-encryption-key-model-get.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions for checking the encryption key model using the Azure portal (web UI), PowerShell (Windows-centric), and Azure CLI. PowerShell is featured as a primary scripting example, which is typically associated with Windows environments. There are no examples using Bash, Linux shell scripting, or other Linux-native tools. The CLI example is generic but does not explicitly show Linux-specific usage or mention Linux environments. The ordering places PowerShell before Azure CLI, which may imply a Windows-first approach.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI usage, including sample commands and output parsing.
- Include notes or sections clarifying cross-platform compatibility of Azure CLI and how to run it on Linux/macOS.
- Consider reordering examples to present Azure CLI before PowerShell, as CLI is cross-platform and more widely used in Linux environments.
- If relevant, mention or provide examples using other Linux-native tools (e.g., REST API via curl, jq for JSON parsing).
- Clearly state that PowerShell examples are primarily for Windows users, and provide parity for Linux/macOS users.
Storage
Create a virtual network rule for Azure Storage
...ge/common/storage-network-security-virtual-networks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page presents PowerShell examples and instructions before Azure CLI, which is more cross-platform. PowerShell is primarily associated with Windows, and its prominence may signal a Windows-first bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-specific considerations or tools. The CLI section is present and accurate, but PowerShell is given precedence and more detailed context, reinforcing a Windows-centric approach.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux users.
- Include Bash shell scripting examples for common tasks, especially for steps involving environment variables or command chaining.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused (though available cross-platform).
- Add notes or links for Linux users regarding installation and authentication steps for Azure CLI.
- Ensure parity in detail and explanation between PowerShell and CLI sections, so Linux users do not feel secondary.
Storage
Best practices for using Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-centric tools (PowerShell, Azure Storage Explorer) are listed before or more prominently than Linux equivalents; PowerShell is frequently referenced for tasks like ingestion and monitoring, with no equivalent Bash or Linux shell examples; Azure CLI is mentioned but not prioritized; and there are no explicit Linux-specific examples or guidance, such as Bash scripts or Linux-native tools. The documentation assumes familiarity with Windows tooling and patterns, potentially making it less accessible for Linux users.
Recommendations
- Provide Linux/Bash shell examples alongside or before PowerShell examples for common operations.
- Explicitly mention cross-platform compatibility for tools like AzCopy and Azure CLI, and provide usage examples on Linux.
- Include references to Linux-native tools (e.g., curl, wget, shell scripts) for REST API interactions.
- Add guidance for using Azure Data Lake Storage from Linux environments, including authentication and automation patterns.
- Ensure that tables and lists of tools do not prioritize Windows tools over cross-platform or Linux-native options.
- Where PowerShell is referenced, also provide Bash/CLI equivalents to ensure parity.
Storage
Version-level WORM policies for immutable blob data
...storage/blobs/immutable-version-level-worm-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) as primary examples for control and data plane operations. Windows-centric tools and patterns (PowerShell) are mentioned before their Linux equivalents (Azure CLI), and no explicit Linux shell or cross-platform examples are provided. The CLI example is given after the PowerShell example, and there is no mention of Bash, scripting, or Linux-specific usage patterns.
Recommendations
- Provide Linux shell (Bash) examples alongside PowerShell commands for all operations.
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Explicitly mention that Azure CLI is available on Windows, Linux, and macOS, and provide usage context for non-Windows environments.
- Include notes or examples for scripting these operations in Bash or other Linux-native shells.
- Avoid using Windows-specific terminology (e.g., PowerShell) as the default or primary example; balance with cross-platform tools.
Storage
Known issues with Azure Data Lake Storage
...ticles/storage/blobs/data-lake-storage-known-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned as a primary tool for managing soft-deleted blobs and directories, and Windows-specific tools such as AzCopy and Azure Storage Explorer are referenced without explicit mention of Linux alternatives or usage patterns. The WASB (Windows Azure Storage Blob) driver is discussed before its Hadoop/Linux equivalent (ABFS), and PowerShell is listed before Azure CLI in some instructions. There are no explicit Linux command-line examples, nor is there guidance for Linux users on using these tools.
Recommendations
- Provide explicit Linux command-line examples alongside PowerShell, especially for tasks such as restoring soft-deleted blobs.
- Clarify cross-platform availability of tools like AzCopy and Azure Storage Explorer, and provide installation/use instructions for Linux.
- Mention Azure CLI before or alongside PowerShell in instructions, as CLI is cross-platform.
- When discussing drivers, introduce ABFS (the Hadoop/Linux driver) before WASB, or present both together with platform context.
- Add notes or sections for Linux users where workflows or tool usage may differ.
Storage
Filter data by using Azure Data Lake Storage query acceleration
...e/blobs/data-lake-storage-query-acceleration-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page provides PowerShell examples and instructions for installing the Az PowerShell module, which are specific to Windows environments. PowerShell is presented as the only command-line scripting example, with no equivalent Bash, shell, or Linux CLI examples. The installation and usage instructions for PowerShell appear before other language SDKs, and there is no mention of cross-platform command-line tools like Azure CLI or Bash scripts. This creates a bias toward Windows users and environments.
Recommendations
- Add Azure CLI examples alongside PowerShell, demonstrating equivalent operations for Linux/macOS users.
- Include Bash or shell script examples where appropriate, especially for command-line tasks.
- Clarify that PowerShell Core is cross-platform, but also provide explicit Linux/macOS instructions for installing and using Azure SDKs.
- Reorder sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell.
- Explicitly mention Linux/macOS prerequisites and environment setup steps, including package managers (apt, yum, brew) for SDK installation.
Storage
Configure a lifecycle management policy
...storage/blobs/lifecycle-management-policy-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and command breakdowns, while the Azure CLI section is less comprehensive and lacks step-by-step guidance. PowerShell is presented before Azure CLI in both main sections, and Windows-centric tools (PowerShell) are described in greater detail. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or workflows.
Recommendations
- Provide equally detailed Azure CLI examples, including step-by-step instructions and sample JSON policy files.
- Add Bash shell examples for Linux users, demonstrating how to use Azure CLI from a Linux environment.
- Include notes or sections on using the documentation from Linux/macOS systems, such as differences in command syntax or environment setup.
- Ensure that CLI examples are presented before or alongside PowerShell to avoid Windows-first ordering.
- Reference cross-platform scripting options (e.g., Python SDK, REST API via curl) to further improve parity.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a Windows bias by presenting Windows instructions and PowerShell examples before their Linux equivalents, and by using Windows-specific tools (PowerShell scripts) for key operations. The Linux instructions use a Python script, but the overall structure and example ordering favor Windows and PowerShell, which may make Linux users feel secondary.
Recommendations
- Alternate the order of Windows and Linux instructions in each section, or present them side-by-side to avoid implicit prioritization.
- Provide equal detail and clarity for both Windows and Linux instructions, ensuring parity in parameters and example usage.
- Mention cross-platform tools (such as Azure CLI) first, as they work on both Windows and Linux.
- Consider providing Bash script examples for Linux users in addition to Python, to match the PowerShell script for Windows.
- Explicitly state that both Windows and Linux are supported and encourage users to choose the method that fits their environment.
Storage
How to use managed identities with Azure File Sync
...cles/storage/file-sync/file-sync-managed-identities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell and Windows-centric tools (Az.StorageSync PowerShell module), with no mention of Linux shell equivalents or cross-platform CLI options. The prerequisites and configuration steps assume the use of Windows servers or Azure Arc-enabled servers, and do not provide guidance for Linux-based environments. The documentation also references Windows VM pivots and does not mention Linux VMs or agents, further reinforcing the Windows-first approach.
Recommendations
- Provide Azure CLI examples alongside PowerShell for all command-line instructions, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention support for Linux-based registered servers, including steps for enabling managed identities on Linux VMs and Azure Arc-enabled Linux servers.
- Reference Linux-specific documentation pivots (e.g., how to configure managed identities on Linux VMs) and link to relevant guides.
- Clarify whether the Azure File Sync agent is available for Linux, and if not, state this limitation clearly.
- Where possible, use generic terminology (e.g., 'command line' instead of 'PowerShell window') and avoid assuming a Windows environment by default.
Storage
How to install the Azure File Sync agent silently
...orage/file-sync/file-sync-agent-silent-installation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and examples for installing the Azure File Sync agent on Windows, using Windows-specific tools (msiexec), Windows file paths, and Windows conventions (elevated command prompt, .msi packages, %SYSTEMDRIVE%). There are no references to Linux equivalents, nor any mention of Linux support or alternative installation methods for non-Windows platforms.
Recommendations
- Clarify platform support: Explicitly state whether Azure File Sync agent is Windows-only or if Linux is supported.
- If Linux is supported, provide equivalent silent installation instructions for Linux, including relevant commands (e.g., using .deb/.rpm packages, shell scripts, or package managers like apt/yum).
- Include Linux-specific examples for custom configuration, such as environment variables, file paths, and proxy settings.
- If Linux is not supported, add a note at the top of the documentation to inform users that the instructions are specific to Windows.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows Server as the supported platform for Azure File Sync, with all steps and examples (such as Robocopy usage and DFS-N) tailored to Windows environments. There are no Linux equivalents or cross-platform guidance provided, and Windows tools are mentioned without alternatives.
Recommendations
- Explicitly state platform limitations if Azure File Sync is Windows-only, or clarify if Linux support is planned.
- If Linux support exists or is planned, provide equivalent instructions for deploying, registering, and migrating Azure File Sync endpoints on Linux servers.
- Offer Linux-native file copy commands (e.g., rsync) as alternatives to Robocopy, with example syntax.
- Mention Linux-compatible namespace redirection solutions if available, or clarify DFS-N is Windows-only.
- Add a section comparing platform support and guiding users on cross-platform migration strategies if relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Azure File Sync demonstrates a strong Windows bias. All examples, deployment scenarios, and operational instructions reference Windows Server exclusively, with no mention of Linux or cross-platform alternatives. The service is described as transforming Windows Server into a cache, and all recovery, backup, and migration steps assume the use of Windows tools and environments. There are no Linux or non-Windows examples, nor is there guidance for integrating with Linux file servers.
Recommendations
- Add explicit statements about Azure File Sync compatibility (or lack thereof) with Linux servers, and clarify any platform limitations.
- If Linux support exists or is planned, provide equivalent examples and operational guidance for Linux environments.
- Include information on how Linux clients can access Azure Files (e.g., via SMB, NFS), and clarify whether Azure File Sync can be used in mixed OS environments.
- If Azure File Sync is Windows-only, suggest alternative solutions for Linux users and link to relevant documentation.
- Ensure parity in backup, recovery, and migration instructions for Linux-based file servers where possible.
Storage
Known issues with NFS 3.0 in Azure Blob Storage
...age/blobs/network-file-system-protocol-known-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by mentioning PowerShell and Azure CLI as the only methods for enabling static websites, without providing Linux-specific examples or alternatives. The workaround for Windows NFS clients is described before any Linux client guidance, and the use of Windows tools (PowerShell) is referenced without equivalent Linux command examples. There is a lack of explicit Linux command-line examples for common administrative tasks.
Recommendations
- Provide explicit Linux shell (bash) examples for enabling static websites and other administrative tasks, alongside PowerShell and Azure CLI instructions.
- Mention Linux client usage and commands before or alongside Windows workarounds, especially since NFS is more commonly used in Linux environments.
- Include references to common Linux tools and patterns (e.g., mount, exportfs, setfacl) where relevant, and ensure parity in troubleshooting and configuration guidance.
- Clarify that Azure CLI is cross-platform and provide usage examples in both Windows (PowerShell) and Linux (bash) contexts.
Storage
Migrate Files Between SMB Azure file shares
...articles/storage/files/migrate-files-between-shares.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively recommending Robocopy, a Windows-only tool, for migrating files between SMB Azure file shares. All instructions assume a Windows environment, including deploying a Windows VM and using Windows command prompt syntax. There are no examples or guidance for performing similar migrations from Linux systems, nor are Linux-native tools (such as rsync or smbclient) mentioned.
Recommendations
- Add equivalent migration instructions for Linux environments, including mounting SMB shares and using tools like rsync or smbclient.
- Include Linux command-line examples alongside Windows/Robocopy examples.
- Clarify platform requirements up front and provide links to Linux migration documentation if available.
- Mention cross-platform tools (e.g., AzCopy) where appropriate and provide usage examples for both Windows and Linux.
Storage
Enable AD DS Authentication for Azure Files
...s/storage/files/storage-files-identity-ad-ds-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments, with all examples and instructions using Windows PowerShell, Windows-specific modules, and Windows AD tools. There are no Linux or cross-platform instructions, nor any mention of how to perform these steps from a Linux system or using non-Windows tools. The documentation assumes the administrator is working from a domain-joined Windows machine and does not provide parity for Linux users.
Recommendations
- Add instructions or guidance for performing AD DS authentication enablement from Linux systems, if supported.
- Provide examples using Azure CLI or REST API where possible, which are cross-platform.
- Explicitly state platform requirements and limitations at the beginning of the document.
- If Linux is not supported for these operations, clarify this and suggest alternatives or workarounds.
- Include troubleshooting and verification steps that can be performed from Linux clients, such as mounting Azure Files with AD DS credentials from Linux (if supported).
Storage
Migrate to Azure Files Using RoboCopy
...cles/storage/files/storage-files-migration-robocopy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page is heavily biased towards Windows environments. It exclusively uses RoboCopy, a Windows-specific tool, for migration and provides only Windows-based instructions and examples. The migration route assumes a Windows machine as the intermediary, and all mounting and troubleshooting steps are tailored for Windows Server and PowerShell. Although Linux is mentioned as a possible source, there are no Linux-specific migration instructions, examples, or alternative tools provided.
Recommendations
- Provide equivalent Linux migration instructions, such as using smbclient, rsync, or other Linux-compatible SMB tools.
- Include Linux command-line examples for mounting Azure file shares and performing file migrations.
- Discuss Linux-specific considerations, such as file permissions, character encoding, and performance tuning.
- Mention cross-platform tools (e.g., AzCopy, if/when feature parity is achieved) and clarify their suitability for Linux environments.
- Add troubleshooting and optimization tips relevant to Linux servers and NAS devices.
- Reorganize the documentation to present both Windows and Linux migration routes equally, rather than focusing on Windows first.
Storage
Use Managed Identities with Azure Files (preview)
...ain/articles/storage/files/files-managed-identities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only CLI tool used for all resource creation and configuration examples, with no equivalent Azure CLI or Bash examples for Linux users. Windows tools and modules (e.g., AzFilesSmbMIClient, PowerShellGet) are described in detail before Linux alternatives, and the instructions for preparing the environment and troubleshooting are more comprehensive for Windows. Linux instructions are present but less detailed, and some steps (such as storage account creation/configuration) lack Linux-native command examples.
Recommendations
- Provide Azure CLI or Bash examples alongside PowerShell for resource creation and configuration steps, especially for storage account and file share setup.
- Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting and environment preparation.
- Present Windows and Linux examples in parallel, rather than Windows-first, to avoid implicit prioritization.
- Mention and link to Linux equivalents for all Windows tools and modules where possible.
- Clarify any limitations or differences in parity between Windows and Linux up front, and provide workarounds or alternatives for Linux users.
Storage
Migrate to SMB Azure file shares using Azure Storage Mover
.../articles/storage/files/migrate-files-storage-mover.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-centric tools (Robocopy), mentioning Windows Server and Windows migration patterns before Linux equivalents, and lacking explicit Linux migration examples or instructions. The agent deployment instructions mention VMware and Hyper-V (common in Windows environments) but do not discuss Linux-native virtualization or agent installation on Linux systems. There are no Linux-specific examples or troubleshooting guidance.
Recommendations
- Include explicit Linux migration examples, such as mounting SMB shares from Linux and agent installation steps on popular Linux distributions.
- Mention Linux-native virtualization options (e.g., KVM, VirtualBox) for agent deployment.
- Provide troubleshooting tips for common Linux SMB issues and permissions.
- Reference Linux tools or commands (e.g., smbclient, rsync with SMB) as alternatives to Robocopy, and compare their use cases.
- Ensure that instructions and examples are presented in a platform-neutral way, or provide parallel guidance for both Windows and Linux environments.
Storage
Configure cloud trust between AD DS and Microsoft Entra ID
...iles/storage-files-identity-auth-hybrid-cloud-trust.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All prerequisites, examples, and configuration steps assume Windows clients and Windows Server-based Active Directory. PowerShell is the only scripting environment provided for administrative tasks, and Windows-specific tools (such as Windows File Explorer, Group Policy, and dsregcmd.exe) are referenced exclusively. There are no examples or guidance for Linux clients, Samba, or cross-platform scenarios, nor is there mention of Linux equivalents for key tasks such as configuring Kerberos, mounting SMB shares, or managing permissions.
Recommendations
- Add explicit guidance and examples for Linux clients, including prerequisites for Linux-based access to Azure Files over SMB with Entra Kerberos.
- Provide Linux equivalents for key administrative tasks, such as using Samba tools (e.g., smbclient, mount.cifs) and configuring Kerberos (krb5.conf, kinit).
- Include instructions for managing directory and file-level permissions on Linux, such as using setfacl or getfacl, and clarify how NTFS ACLs interact with POSIX permissions.
- Offer cross-platform PowerShell alternatives, such as Bash scripts or Python, for managing Azure resources and Kerberos trust objects.
- Mention any limitations or differences in support for Linux clients, and provide troubleshooting steps for common Linux-specific issues.
- Reorder examples so that Linux and Windows are presented with equal prominence, or provide parallel sections for each platform.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits Windows bias primarily through the use of Windows-centric tools and examples. PowerShell is presented first and in more detail than Azure CLI, and Windows-specific technologies (such as Azure File Sync with Windows file servers) are referenced as the main solution for geo-redundancy for SSD file shares. There is no mention of Linux file server equivalents or cross-platform sync solutions, and the scripting examples and guidance favor Windows patterns and tools.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Include Linux/NFS file server scenarios and guidance for geo-redundancy and disaster recovery, not just Windows File Sync.
- Reference cross-platform tools (e.g., rsync, robocopy, AzCopy from Linux) and provide example scripts for Linux environments.
- Clarify that Azure File Sync is Windows-only and suggest alternative sync or backup strategies for Linux users.
- Ensure parity in troubleshooting, failover, and monitoring instructions for both Windows and Linux clients.
- Explicitly mention support and limitations for Linux/NFS in all relevant sections, not just in feature tables.
Storage
Microsoft Entra Kerberos Authentication for Azure Files
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-hybrid-identities-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Microsoft Entra Kerberos Authentication for Azure Files is heavily Windows-centric. All operating system prerequisites, configuration steps, and client instructions are exclusively for Windows (including Windows 10/11 and Windows Server). Examples and tooling focus on Windows-specific technologies such as PowerShell, Windows File Explorer, Windows registry, Group Policy, Intune Policy CSP, and Windows command-line utilities (e.g., ksetup, reg add). There are no examples, instructions, or references for Linux or macOS clients, nor any mention of cross-platform SMB access or Kerberos configuration outside the Windows ecosystem.
Recommendations
- Add explicit guidance for Linux and macOS clients, including supported scenarios, prerequisites, and limitations for Entra Kerberos authentication.
- Provide Linux/macOS-specific instructions for mounting Azure Files SMB shares using Kerberos, including sample commands (e.g., using mount.cifs, smbclient, or relevant Kerberos configuration steps).
- Document how to obtain domain information (domain name, GUID) and configure Kerberos on non-Windows systems.
- Clarify whether Entra Kerberos authentication is supported or unsupported for non-Windows clients, and if unsupported, state this clearly.
- If support is planned or available, include troubleshooting and debugging steps for Linux/macOS clients.
- Balance examples and tooling references by including cross-platform alternatives where possible, or explicitly noting Windows-only features.
Storage
Configure DNS forwarding for Azure Files
...articles/storage/files/storage-files-networking-dns.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All configuration and verification steps are presented exclusively using PowerShell commands and Windows DNS Server tools (e.g., Add-DnsServerConditionalForwarderZone, Resolve-DnsName, Test-NetConnection). There are no examples or guidance for Linux-based DNS servers (such as BIND or dnsmasq), nor are Linux command-line tools (e.g., dig, host, systemd-resolve) mentioned. The prerequisites specifically call out Azure PowerShell, and the instructions assume a Windows Server DNS environment, even though a note claims the steps are possible with any DNS server.
Recommendations
- Add equivalent Linux/BIND examples for conditional forwarding (e.g., configuration snippets for named.conf).
- Include Linux command-line tools for DNS cache clearing and resolution testing (e.g., systemd-resolve --flush-caches, dig, host).
- Explicitly mention how to configure DNS forwarding on popular Linux DNS servers (BIND, dnsmasq, Unbound) and provide sample configuration files.
- Balance PowerShell examples with bash/shell commands where applicable.
- Clarify prerequisites to include Linux environments and tools, not just Azure PowerShell.
- Provide troubleshooting steps relevant to Linux-based DNS servers.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page exhibits moderate Windows bias. PowerShell examples are given in detail and presented before Azure CLI examples, and there is a strong emphasis on PowerShell cmdlets (Get-AzMetricDefinition, Get-AzMetric) which are primarily used on Windows. The .NET SDK examples further reinforce a Windows-centric approach. While Azure CLI examples are included, there are no Linux-specific shell examples (e.g., Bash scripts, curl, jq), and no mention of Linux-native tools or workflows. The documentation does not provide parity for Linux users in terms of example diversity or tool recommendations.
Recommendations
- Add Bash shell examples using Azure CLI, demonstrating usage in typical Linux environments.
- Include references to Linux-native tools (e.g., curl, jq, grep) for interacting with Azure APIs and parsing results.
- Present Azure CLI examples before PowerShell examples to avoid implicit prioritization of Windows tools.
- Explicitly state that Azure CLI works cross-platform and highlight Linux usage scenarios.
- Consider adding Python SDK examples, which are popular in Linux environments.
- Review reusable content includes for any implicit Windows bias and update to ensure Linux parity.