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 1351-1375 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-monitor-cloud-tiering.md
...s/storage/file-sync/file-sync-monitor-cloud-tiering.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively describes monitoring Azure File Sync Cloud Tiering using the Azure portal and Azure Monitor, but all references to the 'server endpoint' implicitly assume a Windows Server environment, as Azure File Sync is only supported on Windows. There are no examples, instructions, or mentions of Linux-based monitoring, nor are Linux tools or patterns referenced. The documentation does not clarify platform limitations or provide guidance for Linux users.
Recommendations
- Explicitly state that Azure File Sync is only supported on Windows Server, and clarify that monitoring instructions are Windows-specific.
- If Linux support is planned, provide equivalent instructions and examples for Linux environments.
- Offer guidance for cross-platform monitoring, such as using Azure Monitor APIs or CLI tools that work on Linux.
- Include a section addressing platform limitations and alternative solutions for Linux users.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-shared-volumes.md
...cles/storage/elastic-san/elastic-san-shared-volumes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page mentions Windows Server Failover Cluster (WSFC) before Pacemaker when discussing cluster managers, suggesting a Windows-first bias. There are no concrete examples, scripts, or tool references for either Windows or Linux, but the ordering and lack of Linux-specific guidance or examples (such as Pacemaker configuration or Linux SCSI PR tooling) indicate missing Linux parity.
Recommendations
- Provide equal prominence to Linux cluster managers (e.g., mention Pacemaker before or alongside WSFC).
- Add concrete examples or references for configuring SCSI-3 Persistent Reservations with Pacemaker on Linux.
- Include Linux-specific tooling or commands for managing SCSI PR (e.g., sg_persist, scsi-reserve).
- Ensure that any scripts or automation guidance covers both Windows (PowerShell) and Linux (bash, systemd).
- Add troubleshooting and operational notes for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-delete.md
...ain/articles/storage/elastic-san/elastic-san-delete.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by presenting Windows instructions and PowerShell examples before Linux and Azure CLI equivalents. The disconnect instructions start with Windows/PowerShell, and the deletion commands consistently list PowerShell before CLI, which is more commonly used on Linux/macOS. There is no evidence of missing Linux examples, but the ordering and emphasis favor Windows tools and patterns.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI instructions so that neither is consistently prioritized.
- Explicitly state that both PowerShell and CLI are cross-platform, and clarify usage scenarios for each.
- Consider grouping instructions by platform (Windows, Linux/macOS) rather than by tool, or provide a neutral introduction before listing platform-specific steps.
- Ensure parity in detail and clarity between Windows and Linux instructions, including troubleshooting notes if applicable.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-data-protection-overview.md
...ticles/storage/files/files-data-protection-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. In the backup and restore section, Azure PowerShell is listed before Azure CLI, and the only specific non-portal tool called out in the summary is PowerShell, which is primarily a Windows-centric tool. There is no explicit mention of Linux-specific tools or patterns, and the documentation does not provide parity examples or guidance for Linux administrators beyond referencing Azure CLI and REST API (which are cross-platform but not Linux-specific). Azure File Sync is also a Windows-only solution, but this limitation is not clarified for Linux users.
Recommendations
- Explicitly mention Linux compatibility for Azure CLI and REST API, and provide Linux-specific usage examples or links.
- Clarify that Azure File Sync is a Windows-only solution and suggest alternatives or workarounds for Linux environments.
- Balance the order of tool presentation (e.g., alternate listing Azure CLI before PowerShell, or present them together) to avoid implicit prioritization of Windows tools.
- Include a section or callout for Linux administrators, outlining recommended backup and restore workflows and tools for Linux-based file servers.
- Where possible, provide parity in screenshots, code samples, and step-by-step instructions for both Windows and Linux platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-identity-auth-linux-kerberos-enable.md
...s/storage-files-identity-auth-linux-kerberos-enable.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally Linux-focused and provides detailed, step-by-step instructions for configuring Kerberos authentication for Linux clients with Azure Files. However, there is evidence of Windows bias in two areas: (1) the use of Windows-centric terminology and tools (such as NT ACLs, references to updating ACLs through Windows, and reliance on Active Directory Domain Services), and (2) the documentation recommends updating file share ACLs via Windows tools, noting that Linux tools for NT ACLs are minimal. Additionally, Windows AD DS is mentioned before Microsoft Entra Domain Services, and the overall access control model is described in terms of Windows concepts.
Recommendations
- Expand documentation of Linux-native tools for managing NT ACLs, such as setfacl or samba-tool, and provide examples where possible.
- Include guidance or references for cross-platform ACL management, highlighting any available Linux utilities or third-party solutions.
- Clarify or balance terminology to avoid implying that Windows is the only or primary platform for managing access controls, especially in sections relevant to Linux administrators.
- Where Windows AD DS is mentioned, ensure that equivalent Linux or open-source alternatives (such as Samba AD DC) are referenced, if supported.
- Provide more context or caveats about limitations of Linux tools, and suggest workarounds or roadmap for improved Linux parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/virtual-desktop-workloads.md
...in/articles/storage/files/virtual-desktop-workloads.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is heavily focused on Windows-centric technologies and patterns, such as FSLogix, roaming user profiles, folder redirection, and App Attach, all of which are specific to Windows virtual desktop environments. There are no examples, guidance, or mentions of Linux-based virtual desktop workloads, nor are Linux authentication or file access patterns discussed. All technical recommendations, terminology, and examples assume Windows clients and Windows VDI scenarios, with no parity for Linux environments.
Recommendations
- Add explicit guidance for Linux-based virtual desktop workloads, including supported authentication mechanisms and file access patterns for Linux clients.
- Include examples of mounting Azure Files SMB shares from Linux session hosts, using Linux tools (e.g., mount.cifs) and configuration steps.
- Discuss limitations or considerations for Linux VDI solutions (e.g., Citrix/VMWare Horizon with Linux desktops) when using Azure Files.
- Clarify which features (such as FSLogix, App Attach) are Windows-only and suggest alternatives or workarounds for Linux environments.
- Provide parity in recommendations and sizing guidance for Linux workloads, including performance and scale considerations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-java.md
...icles/storage/queues/storage-quickstart-queues-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias by mentioning Windows-specific consoles (cmd, PowerShell) before Bash when introducing command-line instructions. The sample Maven output uses a Windows file path (C:\quickstarts\queues\queues-quickstart), and references to Visual Studio are present when discussing environment variables. However, Bash examples are provided alongside PowerShell, and most instructions are cross-platform.
Recommendations
- List Bash (Linux/macOS) and PowerShell/cmd (Windows) consoles in parallel, or mention Bash first to avoid Windows-first ordering.
- Provide sample output using both Windows and Linux/macOS file paths, or use a generic path format.
- Avoid referencing Visual Studio in environment variable instructions, or add equivalent notes for Linux/macOS shells (e.g., 'If the environment variable is created after the application is launched in a console or IDE, restart your shell or IDE to reload environment variables.').
- Explicitly state cross-platform compatibility in setup and execution steps.
- Consider adding troubleshooting notes for common Linux/macOS issues (e.g., permissions, environment variable persistence).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/veeam/veeam-solution-guide.md
...rchive-disaster-recovery/veeam/veeam-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Data Protection with Veeam demonstrates a Windows bias by consistently referencing Windows-centric technologies (such as Hyper-V and Microsoft 365) and omitting explicit Linux-focused examples or instructions. There are no Linux-specific deployment, configuration, or usage examples, and the documentation does not mention Linux agents, CLI commands, or integration patterns. Windows/Hyper-V and Microsoft services are discussed first and in detail, while Linux workloads and tools are not addressed.
Recommendations
- Add explicit examples and instructions for protecting Linux workloads (e.g., Linux VMs, file servers, and applications) with Veeam and Azure Blob Storage.
- Include references to Veeam Agent for Linux and provide links to relevant documentation.
- Provide CLI or shell script examples for Linux environments, not just GUI or Windows-centric workflows.
- Mention Linux-specific considerations for backup, restore, and repository configuration.
- Ensure parity in describing both Windows and Linux deployment scenarios, including hybrid environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/queues/storage-quickstart-queues-nodejs.md
...les/storage/queues/storage-quickstart-queues-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias in its setup instructions. Specifically, when instructing users to open a console window, it lists 'cmd, PowerShell, or Bash', placing Windows tools first and mentioning Bash only last. Additionally, the example for opening the project in a code editor uses 'code .', which is cross-platform but most commonly associated with Windows usage patterns. No explicit Linux examples, Linux-specific tools, or Linux-first instructions are provided, and there is no mention of platform-specific caveats or parity. All other instructions and code samples are platform-neutral JavaScript/Node.js.
Recommendations
- List Bash (or terminal) before Windows-specific tools (cmd, PowerShell) when mentioning console windows, or mention all platforms equally.
- Explicitly state that all commands work on Linux, macOS, and Windows, and provide any necessary caveats for platform differences (e.g., environment variable setup).
- Include a note or section on running the quickstart on Linux/macOS, such as setting environment variables (export vs. set), and using editors like nano, vim, or VS Code on those platforms.
- Where possible, provide parallel instructions for Linux/macOS users (e.g., opening the project in a terminal-based editor, or using 'export' to set environment variables).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/backup-archive-disaster-recovery/commvault/commvault-solution-guide.md
...isaster-recovery/commvault/commvault-solution-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for the Azure Portal GUI, which is most commonly used on Windows environments. There are no examples or guidance for Linux users, such as using Azure CLI, PowerShell Core (cross-platform), or REST API commands. The operational and implementation steps assume GUI access and do not mention Linux-native tools or workflows, nor do they provide parity for command-line or automation scenarios common in Linux environments.
Recommendations
- Add Linux-specific instructions for creating and managing Azure Storage accounts, such as using the Azure CLI (az storage account create, az storage container create, etc.).
- Include sample scripts or commands for integrating Commvault with Azure Blob storage from Linux environments.
- Provide guidance on using REST APIs or SDKs (Python, Bash) for storage management and backup operations.
- Mention cross-platform tools (e.g., PowerShell Core, Azure CLI) and clarify their usage on Linux and macOS.
- Add screenshots or terminal output examples for Linux workflows alongside GUI instructions.
- Reference Linux-compatible monitoring and alerting solutions (e.g., using Azure CLI, open-source tools) for operational guidance.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/data-management/cirrus-data-migration-guide.md
...artners/data-management/cirrus-data-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Links Priority
Summary
The documentation demonstrates a subtle Windows bias by prioritizing Windows-specific resources and links before Linux equivalents. For example, the quick start guide and 'next steps' sections link to Windows virtual machine documentation first, with no direct mention or links to Linux VM documentation. However, the main migration example uses a Linux host, and command-line instructions (e.g., curl, iostat) are Linux-oriented, with no exclusive use of Windows tools or PowerShell. There are no explicit Windows-only commands or tools, but the structure and resource linking suggest a Windows-first approach.
Recommendations
- Provide parallel links and references for both Windows and Linux virtual machine documentation in prerequisite and next steps sections.
- Explicitly mention that the migration process is applicable to both Windows and Linux hosts, and provide examples or notes for both where relevant.
- Include Windows-specific command-line or PowerShell examples alongside Linux commands (e.g., show how to monitor IO on Windows, such as using Resource Monitor or perfmon, in addition to iostat for Linux).
- Balance screenshots and walkthroughs to show both Windows and Linux environments if the product supports both equally.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-cli.md
...zure-docs/blob/main/articles/storage/blobs/blob-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\temp\) in all code samples, even though the examples are written in Bash and intended for cross-platform use. There are no Linux or macOS-specific path examples, nor is there any mention of Linux file system conventions. Additionally, instructions for creating or referencing files (such as the XML file for blob tags) assume a Windows directory structure and do not provide Linux alternatives.
Recommendations
- Provide both Windows and Linux/macOS path examples in all code samples, e.g., use C:\temp\ for Windows and /tmp/ or ~/temp/ for Linux/macOS.
- Explicitly mention that the Bash scripts are cross-platform and note any platform-specific considerations (such as path separators).
- When referencing files to be created locally (e.g., blob-list.xml), include instructions for both Windows and Linux/macOS environments.
- Add a note at the beginning of the article clarifying that examples are intended to work on all platforms, and highlight any differences users should be aware of.
- Where applicable, show how to run the Azure CLI commands in PowerShell, Bash (Linux/macOS), and Windows Command Prompt, or at least provide links to platform-specific guidance.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-lease.md
...articles/storage/blobs/storage-blob-container-lease.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is focused exclusively on .NET and C#, which are commonly associated with Windows development. All code examples are in C#, and there is no mention of Linux-specific tools, patterns, or alternative SDKs (such as Python, Java, or CLI usage on Linux). There are no instructions or examples for setting up or running the code on Linux, nor any discussion of cross-platform considerations. The page implicitly assumes a Windows/.NET development environment.
Recommendations
- Add explicit instructions for running .NET code and setting up the environment on Linux, including installation of the .NET SDK on Linux distributions.
- Provide code examples or links for other languages/platforms commonly used on Linux (e.g., Python, Java, Node.js).
- Include guidance for using Azure CLI or REST API directly from Linux shells (bash), demonstrating lease management operations.
- Mention cross-platform compatibility of the Azure Storage .NET SDK and clarify any OS-specific considerations.
- Add troubleshooting or FAQ sections for Linux users (e.g., common permission or environment issues).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-container-properties-metadata.md
...ge/blobs/storage-blob-container-properties-metadata.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides .NET/C# examples and setup instructions, which are most commonly associated with Windows environments. There are no Linux-specific instructions, examples, or mentions of cross-platform considerations (such as Mono or .NET Core on Linux). The setup and code snippets assume a Windows-centric development workflow, and do not address Linux users or alternative tooling.
Recommendations
- Add explicit instructions for setting up the .NET client library on Linux, including installation of .NET SDK and any platform-specific dependencies.
- Include code examples and console output that demonstrate usage on Linux (e.g., bash shell, Linux terminal).
- Mention cross-platform compatibility of the .NET client library, clarifying that the examples work on Linux and macOS as well as Windows.
- Reference Linux-friendly editors (such as VS Code) and command-line tools in the setup section.
- Provide troubleshooting tips or notes for common Linux-specific issues (such as file permissions or environment variables).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-storage-estimate-costs.md
.../articles/storage/blobs/blob-storage-estimate-costs.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page consistently references AzCopy as the canonical tool for data transfer and cost estimation, but does not mention or provide examples for Linux-native alternatives (such as Azure CLI, REST API via curl, or third-party tools). There are no command-line examples or usage patterns shown for Linux environments, and the documentation does not address cross-platform usage or parity, implicitly favoring Windows tooling and workflows.
Recommendations
- Include examples using Azure CLI and REST API (e.g., with curl) for cost estimation and data operations, showing commands that work natively on Linux and macOS.
- Explicitly mention that AzCopy is cross-platform and provide installation and usage instructions for Linux and macOS, not just Windows.
- Add references to other popular Linux tools (such as rclone) that can interact with Azure Blob Storage, and discuss their cost implications.
- Ensure that any sample scripts or automation patterns are shown in both PowerShell and Bash (or POSIX shell) formats.
- Add a section or note clarifying platform compatibility for all recommended utilities and workflows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-containers-list.md
...articles/storage/blobs/storage-blob-containers-list.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exclusively provides .NET (C#) examples and setup instructions, which are most commonly associated with Windows environments. There is no mention of Linux-specific setup, usage patterns, or alternative code examples (e.g., for .NET on Linux, Bash, or cross-platform CLI usage). The documentation implicitly assumes a Windows-first perspective by not acknowledging Linux or cross-platform development scenarios.
Recommendations
- Add explicit instructions or notes for running .NET code and setting up the environment on Linux (e.g., using .NET Core on Ubuntu).
- Include code examples or CLI commands that demonstrate listing blob containers using Bash or Azure CLI, which are commonly used on Linux.
- Reference cross-platform compatibility of the .NET client library and provide troubleshooting tips for Linux users.
- Mention any platform-specific considerations (such as authentication or environment variables) for Linux.
- Ensure that examples and setup steps do not assume Windows-only tools or patterns (e.g., Visual Studio, PowerShell) and provide alternatives for Linux (e.g., VS Code, Bash).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-scale-targets.md
.../articles/storage/files/storage-files-scale-targets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in the Azure File Sync sections. It explicitly states that the Azure File Sync agent runs on Windows Server, with all performance guidance and examples referencing Windows Server only. There are no mentions of Linux support, tools, or equivalent sync solutions for Linux clients. The rest of the documentation is protocol-agnostic (SMB/NFS) and does not show overt platform bias, but the File Sync section is Windows-centric.
Recommendations
- Clearly state platform support for Azure File Sync at the beginning of the relevant section. If Linux is not supported, make this explicit; if partial support exists, document it.
- If there are Linux-compatible alternatives for file synchronization with Azure Files (such as rsync, Azure CLI, or third-party tools), mention and link to them.
- Provide performance guidance and examples for Linux clients accessing Azure Files via SMB or NFS, including any relevant tuning or limitations.
- Where possible, use cross-platform terminology and avoid assuming Windows-only deployments, especially in general Azure Files sections.
- Add a comparison table or section outlining feature parity and differences between Windows and Linux clients for Azure Files and Azure File Sync.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-resource-instances.md
.../common/storage-network-security-resource-instances.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples before Azure CLI examples, potentially favoring Windows users. The PowerShell section is more extensive, with multiple scenarios and commands, while the Azure CLI section is briefer. There are no explicit Linux-specific examples or mentions of Linux tooling, but Azure CLI is cross-platform and included. No Linux shell or scripting examples are provided, and PowerShell is presented as the primary scripting interface.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Ensure parity in the depth and breadth of examples for both PowerShell and Azure CLI, covering all scenarios equally.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell commands (e.g., bash) where appropriate.
- Consider adding a short section or note for Linux users, highlighting any OS-specific considerations or best practices.
- Avoid implying PowerShell is the default or preferred scripting environment unless there is a technical reason.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-ip-address-range.md
...ge/common/storage-network-security-ip-address-range.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions for both PowerShell and Azure CLI, but the PowerShell (Windows-centric) section is presented before the Azure CLI (cross-platform) section. There are no Linux-specific examples or mentions of Linux tools, and the PowerShell section is more prominent, which may suggest a Windows-first bias.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide installation instructions for Linux.
- Consider adding Bash or shell script examples for common Linux workflows, or at least acknowledge Linux usage scenarios.
- Balance the prominence of PowerShell and CLI sections, or combine them under a 'Command-line' heading with clear OS applicability notes.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-abfs-driver.md
...rticles/storage/blobs/data-lake-storage-abfs-driver.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation refers to the driver as the 'Windows Azure Storage Blob driver' (WASB) and discusses it as the prior capability before ABFS. The term 'Windows' is used in the context of Azure Storage Blob, which may suggest a Windows-centric origin or association. However, the technical content, examples, and configuration instructions are platform-neutral and use standard Hadoop tools and configuration files, with no exclusive focus on Windows or PowerShell. Linux/Unix examples are present (e.g., bash commands), and there is no omission of Linux equivalents.
Recommendations
- Clarify that the 'Windows Azure Storage Blob driver' (WASB) is not Windows-specific, or consider using the acronym 'WASB' primarily to avoid confusion.
- Add a note early in the documentation to emphasize that ABFS and WASB are cross-platform and supported on both Linux and Windows Hadoop distributions.
- Ensure that all examples and configuration instructions remain platform-neutral, and explicitly mention cross-platform compatibility where relevant.
- If mentioning management tools like Ambari, clarify their cross-platform nature or provide Linux-specific alternatives if any exist.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/data-lake-storage-use-hdfs-data-lake-storage.md
.../blobs/data-lake-storage-use-hdfs-data-lake-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits some Windows bias, primarily by presenting PowerShell code for SSH access as the only explicit example, even though the context is a Linux-based HDInsight cluster. The SSH example is labeled as 'sample PowerShell code,' which may confuse Linux users, and no native Linux shell example is provided. However, the rest of the HDFS CLI commands are platform-agnostic and do not show further Windows bias.
Recommendations
- Provide Linux shell (bash) examples for SSH access alongside or instead of PowerShell, since HDInsight clusters are Linux-based.
- Clarify that SSH commands are the same on Linux/macOS terminals and Windows (when using WSL or OpenSSH), or provide separate tabs/examples for each platform.
- Avoid labeling SSH command blocks as 'PowerShell' when the commands are cross-platform.
- Review other sections for similar platform-specific language or examples and ensure parity for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/blob-upload-function-trigger-javascript.md
...orage/blobs/blob-upload-function-trigger-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation heavily emphasizes Visual Studio Code and Azure Portal workflows, which are cross-platform, but all step-by-step UI instructions and screenshots are tailored to GUI tools rather than command-line environments. There are no explicit Windows-only tools (like PowerShell or Command Prompt), but the absence of Linux-specific command-line or file management examples (e.g., using Bash, Linux file explorers, or Linux-native editors) means Linux users are left to adapt instructions themselves. The CLI examples are platform-neutral (Azure CLI), but the primary guidance and troubleshooting focus on GUI workflows, which may be more familiar to Windows users.
Recommendations
- Add explicit Linux (and macOS) command-line examples for uploading files to Blob Storage, such as using 'az storage blob upload' or 'curl' with SAS tokens.
- Include instructions for managing files and environment variables using Bash or other Linux-native tools.
- Where UI screenshots are shown, clarify that the steps are identical on all platforms, or provide alternative screenshots for Linux/macOS if there are differences.
- Mention that Visual Studio Code is cross-platform, but also suggest alternative editors or workflows for users who prefer terminal-based development.
- Add troubleshooting tips for common Linux/macOS issues, such as file permissions or environment variable configuration.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-user-delegation-sas-create-dotnet.md
...lobs/storage-blob-user-delegation-sas-create-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation is focused exclusively on .NET usage for creating a user delegation SAS, with all code samples in C#. There are no references to platform-specific tools, but the .NET ecosystem and C# code examples are typically associated with Windows development. There are no Linux or cross-platform command-line examples (such as Bash, Azure CLI, or PowerShell), nor is there any mention of Linux-specific considerations or parity.
Recommendations
- Include equivalent examples using Azure CLI and/or PowerShell, which are cross-platform and can be run on both Windows and Linux.
- Add a section or note clarifying that the .NET SDK and code samples are cross-platform and can be run on Linux, macOS, and Windows, possibly with links to .NET installation instructions for Linux.
- Provide sample scripts or instructions for creating a user delegation SAS using REST API calls via curl or similar Linux-native tools.
- Explicitly mention any platform-specific requirements or differences, if any, to help Linux users understand how to adapt the instructions.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-sas-overview.md
...b/main/articles/storage/common/storage-sas-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias, primarily by listing PowerShell as the first example under 'Get started with SAS' for user delegation SAS, and by including a PowerShell-specific guide that is not matched by a Bash or Linux shell equivalent. While Azure CLI is mentioned (which is cross-platform), the explicit highlighting of PowerShell and its placement before other language examples suggests a preference for Windows tooling. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific tools or workflows.
Recommendations
- Add Bash or Linux shell examples for creating SAS tokens, especially for common scenarios.
- Ensure that Azure CLI examples are clearly marked as cross-platform and, where possible, provide explicit Linux usage notes.
- Balance the order of example links so that PowerShell is not always listed first; consider rotating or grouping by platform-neutral and platform-specific tools.
- If PowerShell is included, also include equivalent Bash or shell scripts for parity.
- Explicitly mention that Azure CLI and SDKs are available on Linux and macOS as well as Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-disaster-recovery-guidance.md
...s/storage/common/storage-disaster-recovery-guidance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-centric tools such as Azure PowerShell and AzCopy for data copying and backup operations, but does not provide explicit Linux or cross-platform command-line examples or mention Linux-native alternatives. There are no CLI (az), Bash, or Linux shell script examples, and PowerShell is referenced without clarifying its cross-platform availability or providing parity with Linux usage patterns.
Recommendations
- Include Azure CLI (az) examples alongside or before PowerShell examples for all operations, as Azure CLI is cross-platform and widely used on Linux.
- When referencing AzCopy, clarify that it is available for Windows, Linux, and macOS, and provide example commands for both Windows (CMD/PowerShell) and Linux (Bash).
- Avoid referencing 'Azure PowerShell' as the only scripting interface; always mention Azure CLI as an alternative.
- Where scripting or automation is discussed, provide both PowerShell and Bash script snippets.
- Explicitly state the cross-platform nature of tools where applicable, and avoid implying that Windows tools are the default or only option.
- Add a section or callout for Linux users, summarizing recommended tools and patterns for disaster recovery operations.