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 1251-1275 of 1657 flagged pages
Storage
Authorize access for AzCopy with a user identity
...e/common/storage-use-azcopy-authorize-user-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for environment variable setup, but Windows/Powershell syntax is consistently presented alongside or immediately after Linux, sometimes with more detail. The Azure PowerShell section is included as a distinct authorization method, but there is no equivalent section for Linux-native shells or tools (e.g., Bash, zsh) outside of Azure CLI. The documentation references Windows-specific concepts (e.g., 'command prompt', Powershell) and does not provide parity for Linux-specific workflows beyond basic environment variable usage.
Recommendations
- Ensure Linux examples are presented first or with equal prominence to Windows examples.
- Add explicit Bash/zsh shell examples for all commands, not just environment variable setup.
- Include a section for Linux-native authorization workflows, such as using GNOME Keyring or other secret stores.
- Clarify cross-platform support for AzCopy secret stores and provide troubleshooting for Linux users.
- Balance the coverage of Azure PowerShell with equivalent Linux-native tools or workflows.
- Avoid Windows-centric terminology (e.g., 'command prompt', 'press ENTER') and use platform-neutral language.
Create Pull Request
Storage
Synchronize with Azure Blob storage by using AzCopy v10
...storage/common/storage-use-azcopy-blobs-synchronize.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 paths (e.g., 'C:\myDirectory') in all examples and syntax sections, without providing equivalent Linux/macOS examples (e.g., '/home/user/myDirectory'). The guidance on quoting paths prioritizes Windows Command Shell (cmd.exe) considerations, mentioning Linux shells only in passing. No Linux-specific examples, notes, or troubleshooting tips are provided, and the documentation assumes a Windows environment for local file system operations.
Recommendations
- Provide parallel examples using Linux/macOS-style paths (e.g., '/home/user/myDirectory') alongside Windows examples.
- Explicitly mention and show command usage in Bash or other common Linux shells, including quoting conventions and environment differences.
- Add troubleshooting notes or tips relevant to Linux/macOS users, such as file permissions or case sensitivity.
- Clarify that AzCopy is cross-platform and highlight any platform-specific considerations.
- Ensure that all examples and syntax sections are inclusive of both Windows and Linux/macOS users.
Storage
Upload files to Azure Blob storage by using AzCopy v10
...cles/storage/common/storage-use-azcopy-blobs-upload.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-style file paths (e.g., 'C:\myDirectory\myTextFile.txt') in all examples and does not provide any Linux or macOS equivalents (e.g., '/home/user/myTextFile.txt'). The guidance on quoting paths is present, but all actual command examples are Windows-centric, which may confuse or exclude users on Linux or macOS platforms.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., '/home/user/myTextFile.txt') alongside Windows examples.
- Explicitly mention and demonstrate the use of forward slashes and typical Linux directory structures in command examples.
- Clarify shell-specific quoting requirements for Bash, Zsh, and other common Linux/macOS shells.
- Consider alternating or grouping examples by platform to ensure parity and inclusivity.
- Add a section or note specifically addressing cross-platform usage, with tips for adapting commands to different operating systems.
Storage
Copy from Google Cloud Storage to Azure Storage with AzCopy
...cles/storage/common/storage-use-azcopy-google-cloud.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Windows-specific instructions (such as setting environment variables) are listed first in tables, and there is a tip about quoting that prioritizes Windows Command Shell (cmd.exe) over other shells. There is no Powershell-heavy content, and Linux/macOS examples are present and correct. However, Windows tools and patterns are mentioned before their Linux equivalents in several places.
Recommendations
- Alternate the order of operating systems in tables and examples, sometimes listing Linux/macOS first.
- Provide explicit examples for Linux shells (e.g., bash, zsh) alongside Windows cmd.exe, and clarify quoting requirements for common Linux shells.
- Add a note or section that highlights cross-platform usage and parity, ensuring that Linux/macOS users feel equally supported.
- Where possible, use neutral language and ordering (e.g., 'On Linux/macOS, use export; on Windows, use set') rather than always listing Windows first.
- Consider including troubleshooting tips or common issues for Linux/macOS users, not just Windows.
Storage
Configure private endpoints for Azure Elastic SAN
...elastic-san/elastic-san-configure-private-endpoints.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for configuring private endpoints, but the PowerShell example is presented before the CLI example, which may suggest a Windows-first bias. The PowerShell example is detailed and extensive, reinforcing the perception that Windows tools are prioritized. There are no Linux-specific shell examples (e.g., bash), and no mention of Linux-specific tools or patterns for private endpoint configuration. However, Azure CLI is cross-platform and included, which helps mitigate bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add bash-specific scripting examples or notes for Linux users where appropriate.
- Include troubleshooting or environment setup notes for Linux users (e.g., package installation, permissions).
- Ensure parity in detail and explanation between PowerShell and CLI sections.
Storage
Connect Azure Elastic SAN to Azure Kubernetes over iSCSI
...rticles/storage/elastic-san/elastic-san-connect-aks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists both Azure PowerShell and Azure CLI as prerequisites, but mentions PowerShell first and provides the PowerShell example before the Azure CLI example for retrieving volume information. No Linux-specific tools or patterns are mentioned, and the CLI example is present but not prioritized. There are no explicit Windows-only tools, but the ordering and emphasis suggest a mild Windows bias.
Recommendations
- List Azure CLI before Azure PowerShell in prerequisites and examples, as CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, macOS, and Linux to avoid implying platform exclusivity.
- Provide examples of retrieving volume information using Azure CLI first, and consider adding bash scripting examples for Linux users.
- Add a note or section highlighting Linux compatibility and any OS-specific considerations for iSCSI setup.
- Ensure future documentation alternates or balances the order of Windows and Linux tooling to avoid implicit bias.
Storage
Use clustered applications on Azure Elastic SAN
...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) first when listing cluster managers, with Pacemaker (the main Linux alternative) only mentioned secondarily. There are no platform-specific examples, scripts, or tooling references for either Windows or Linux, but the ordering and lack of explicit Linux guidance suggest a mild Windows bias. No PowerShell commands or Windows-only tools are referenced, but the documentation does not provide parity in terms of example usage or setup for Linux environments.
Recommendations
- Provide explicit examples or guidance for both Windows (WSFC) and Linux (Pacemaker) cluster manager setups.
- Ensure that Linux tools, commands, or configuration steps are included and given equal prominence to Windows equivalents.
- Consider alternating the order of mentioning cluster managers, or grouping them together without prioritization.
- Add sample scripts or walkthroughs for attaching Elastic SAN volumes in both Windows and Linux environments.
- Reference relevant Linux documentation or resources for SCSI-3 Persistent Reservation management.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its examples and patterns. In the 'Work with Azure Files using System.IO' section, all code examples use Windows-style paths (e.g., Z:\file-share) and reference mounted SMB shares on Windows, with no equivalent Linux examples (such as mounting via NFS or using Linux path conventions). The first and only code samples for file share access and manipulation are Windows-centric, and Linux mounting is only mentioned in passing, not demonstrated. There are no Linux-specific code snippets or instructions for working with mounted shares using Linux paths.
Recommendations
- Provide parallel Linux examples for mounting Azure Files shares, including sample mount commands and code using Linux path conventions (e.g., '/mnt/file-share').
- Include code samples that demonstrate using System.IO with Linux-mounted shares, showing how to enumerate directories, write files, and manage ACLs using Linux paths.
- When presenting examples, alternate or equally present Windows and Linux scenarios, rather than defaulting to Windows first.
- Add guidance or troubleshooting notes for common Linux-specific issues (e.g., permissions, NFS quirks) when working with Azure Files.
- Explicitly state cross-platform compatibility and highlight any differences in behavior or APIs between Windows and Linux.
Storage
Configure a Site-to-Site VPN for Azure Files
...icles/storage/files/storage-files-configure-s2s-vpn.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits Windows bias primarily by mentioning Windows Server Routing and Remote Access (RRAS) as the only example of an on-premises VPN appliance, with no equivalent Linux example or guidance. Windows tooling is referenced first and exclusively in the prerequisites, potentially leading users to assume Windows is the preferred or only supported platform for on-premises VPN appliances. However, the rest of the documentation provides parity between Azure Portal, PowerShell, and CLI instructions, and links are provided for mounting Azure Files on Windows, macOS, and Linux.
Recommendations
- Explicitly mention and provide examples of popular Linux-based VPN appliances (e.g., StrongSwan, OpenVPN, Libreswan) in the prerequisites section.
- Include links or references to official guides for configuring Linux-based VPN appliances with Azure VPN Gateway.
- Add a short note clarifying that both Windows and Linux appliances are supported and provide a pointer to the Azure-tested device list for cross-platform options.
- Where Windows RRAS is mentioned, offer a Linux alternative in the same paragraph or immediately after.
- Ensure that any screenshots or step-by-step instructions for configuring the on-premises appliance are available for both Windows and Linux platforms.
Storage
Use Kerberos authentication for Linux clients with Azure Files
...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 enabling Kerberos authentication for Linux clients with Azure Files. However, there is evidence of Windows bias in two areas: (1) Windows-centric terminology and tooling are used throughout (e.g., references to NT ACLs, 'update ACLs through Windows', and reliance on Samba/Winbind to interact with Windows-style domains); (2) Windows tools and patterns are mentioned as the primary or only way to manage certain aspects (such as updating NT ACLs), with Linux alternatives described as 'minimal' or absent.
Recommendations
- Provide guidance or examples for managing NT ACLs directly from Linux, if possible, or reference open-source tools that can do so.
- Clarify which features or limitations are inherent to Azure Files versus those that are due to Windows-centric design, and suggest workarounds or alternatives for Linux users.
- Where Windows tools or patterns are referenced, offer Linux-native equivalents or explicitly state when no parity exists.
- Expand documentation on Linux tools for ACL management, even if limited, and link to relevant community resources.
- Consider adding a comparison table of Windows vs. Linux management capabilities for Azure Files to set expectations for cross-platform administrators.
Storage
Assign an Azure role for access to queue data
...ticles/storage/queues/assign-azure-role-data-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for both PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is presented before Azure CLI, and the PowerShell section is more detailed. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. The Azure CLI example is cross-platform, but the ordering and depth favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Add explicit Bash shell examples or clarify that Azure CLI commands work natively on Linux/macOS.
- Balance the level of detail between PowerShell and Azure CLI sections, ensuring Linux users have equally comprehensive guidance.
- Mention that PowerShell Core is available cross-platform, but clarify that Azure CLI is the recommended tool for Linux environments.
Storage
Introduction to Azure Queue Storage
...articles/storage/queues/storage-queues-introduction.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where quickstart links for .NET, Java, Python, and Node.js all specify tabs or environment variable instructions for Windows, but do not mention Linux or cross-platform equivalents. For Java, a 'powershell' tab is referenced, which is a Windows-centric tool. There is no explicit mention of Linux tools, shell environments, or parity in examples for non-Windows users.
Recommendations
- Add Linux-specific tabs or instructions for environment variable setup and authentication in all quickstart guides.
- Ensure that examples for command-line usage include both Windows (PowerShell, CMD) and Linux (bash, sh) equivalents.
- Avoid referencing Windows tools (like PowerShell) exclusively; provide cross-platform alternatives (e.g., Azure CLI usage in bash).
- Explicitly mention cross-platform support and provide links or sections for Linux/macOS users in the 'Next steps' area.
Storage
Quickstart: Azure Queue Storage client library for JavaScript
...les/storage/queues/storage-quickstart-queues-nodejs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias in the 'Setting up' section, where Windows-specific consoles (cmd, PowerShell) are mentioned before Bash, and Visual Studio Code is referenced as the editor to open the project, which is more commonly associated with Windows workflows. No Linux-specific tools or patterns are highlighted, and there are no explicit Linux examples or instructions. However, most commands and instructions are cross-platform, and there is no exclusive use of Windows-only tools or PowerShell scripts.
Recommendations
- List Bash (Linux/macOS) before cmd/PowerShell when mentioning console options, or explicitly state that all commands work in Bash, cmd, and PowerShell.
- Include a note or section on using alternative editors (e.g., Vim, nano, Emacs) for Linux users, or clarify that Visual Studio Code is available cross-platform.
- Add explicit confirmation that all setup and run instructions work on Linux/macOS, and mention any platform-specific considerations if relevant.
- Where environment variables are discussed, provide both Windows (set) and Linux/macOS (export) syntax for setting them.
- Consider including screenshots or terminal output examples from Linux/macOS environments to reinforce cross-platform parity.
Storage
Quickstart: Azure Queue Storage client library for Java
...icles/storage/queues/storage-quickstart-queues-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits mild Windows bias, primarily in the project creation section. It lists 'cmd, PowerShell, or Bash' as console options, but presents the PowerShell example before Bash. The sample output uses a Windows-style path (C:\quickstarts\queues\queues-quickstart), and references to Visual Studio and environment variable handling are Windows-centric. However, Bash examples are provided, and most instructions are cross-platform.
Recommendations
- Present Bash examples before PowerShell, or side-by-side, to avoid Windows-first ordering.
- Include Linux-style sample output paths (e.g., /home/user/quickstarts/queues/queues-quickstart) alongside Windows paths.
- Clarify environment variable instructions for both Windows (cmd/PowerShell) and Linux/macOS (Bash/zsh), especially regarding session reloads.
- Replace or supplement references to Visual Studio with cross-platform IDEs (e.g., IntelliJ IDEA, VS Code) or generic instructions.
- Explicitly state that all commands and code are cross-platform unless noted, and provide troubleshooting tips for Linux/macOS users where behavior may differ.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses heavily on Veeam solutions for Azure, with repeated references to Microsoft-centric environments (Azure, Microsoft 365, Entra ID, Hyper-V). There is a notable absence of Linux-specific examples, tools, or deployment instructions. Windows technologies (Hyper-V, Azure, Microsoft 365) are mentioned explicitly and frequently, while Linux workloads, agents, or integration patterns are not discussed. No PowerShell-specific bias is present, but the lack of Linux parity is evident.
Recommendations
- Add explicit examples and instructions for backing up and restoring Linux workloads (e.g., Linux VMs, physical Linux servers) using Veeam with Azure Blob Storage.
- Include references to Veeam Agent for Linux and provide links to its documentation.
- Present Linux deployment and configuration steps alongside Windows/Hyper-V examples, ensuring parity in guidance.
- Mention Linux-specific considerations for Azure Blob Storage integration, such as authentication, repository setup, and restore workflows.
- Highlight cross-platform support in use cases and solution overviews, making it clear that Veeam supports both Windows and Linux environments equally.
Storage
Migrate your block data to Azure with Cirrus Data
...artners/data-management/cirrus-data-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing Windows resources before Linux equivalents, such as linking to the Windows VM quick start guide and overview in both the implementation steps and 'Next steps' section. There are no explicit PowerShell or Windows-only command examples, but Linux is only mentioned in passing and lacks detailed, step-by-step examples or links to Linux-specific guides. The only command-line example given is 'iostat', which is Linux/Unix-centric, but overall, the documentation assumes familiarity with Windows patterns and does not provide Linux parity in guidance or references.
Recommendations
- Include links to both Windows and Linux VM quick start guides and overviews in implementation and next steps sections.
- Provide explicit step-by-step examples for both Windows and Linux hosts, including installation, migration, and verification commands.
- Mention and demonstrate relevant Linux tools (e.g., lsblk, df, mount) alongside any Windows tools (e.g., Disk Management, PowerShell) where applicable.
- Clarify OS-specific prerequisites and steps, ensuring that Linux users have equal guidance for licensing, disk management, and agent installation.
- Balance screenshots and portal instructions with CLI examples for both platforms.
Storage
Migrate data to Azure with Atempo Miria
...d-partners/data-management/atempo-quick-start-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing migration examples and configuration steps exclusively for Windows file servers (SMB/CIFS shares), with no mention or guidance for Linux-based sources (e.g., NFS shares). The Data Mover example and screenshots reference Windows platforms, and there are no Linux-specific instructions or parity in migration scenarios.
Recommendations
- Add equivalent migration examples for Linux file servers, such as NFS shares, including step-by-step instructions and screenshots.
- Explicitly mention support for Linux Data Movers and provide configuration guidance for Linux environments.
- Ensure that references to platform-specific options (e.g., protocol selection, Data Mover pool) include both Windows and Linux choices.
- Balance the documentation by presenting Windows and Linux migration scenarios side-by-side, or in separate sections, to improve parity and inclusivity.
Storage
Get started with Storage Explorer
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows is listed first in the prerequisites section, and the legacy Azure Storage Emulator is mentioned as a supported emulator, but it is only available for Windows. The Linux sections are present and reasonably detailed, but Windows-specific tools and installation patterns (such as the .NET runtime and Storage Emulator) are highlighted before their cross-platform or Linux equivalents.
Recommendations
- Rotate the order of OS sections or present all platforms together to avoid Windows-first perception.
- Emphasize cross-platform tools (e.g., Azurite) before Windows-only tools like Azure Storage Emulator.
- Provide parity in troubleshooting and dependency documentation for all platforms, not just Windows.
- Explicitly mention Linux alternatives or equivalents where Windows-specific tools are referenced.
- Clarify support status for less-tested Linux distributions (like SLES) and offer guidance or community resources.
Storage
Assign an Azure role for access to table data
...ticles/storage/tables/assign-azure-role-data-access.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page presents both PowerShell and Azure CLI examples for assigning Azure roles, but PowerShell is listed first and described in greater detail, which may indicate a subtle Windows-first and PowerShell-heavy bias. There are no explicit Linux-only examples, nor are Linux-specific tools or shell patterns mentioned. The CLI example is generic and does not highlight Linux usage or shell differences.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide sample commands in bash/zsh syntax (e.g., using single quotes, environment variables, etc.).
- Include notes or examples for Linux users, such as how to install and use Azure CLI on Linux, and clarify any differences in command usage or authentication.
- Consider adding a section or tab for Linux shell scripting or automation, demonstrating role assignment in bash scripts.
- Ensure parity in detail and explanation between PowerShell and CLI sections, so Linux users do not feel secondary.
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 for managing Azure Storage resource instance network rules, with PowerShell presented before Azure CLI. This ordering and emphasis may favor Windows users, as PowerShell is primarily associated with Windows environments, while Azure CLI is cross-platform. No Linux-specific tools or shell examples are provided, and there is no mention of Bash or Linux-specific usage patterns.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and widely used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample Bash usage where appropriate.
- Add notes or examples for scripting these operations in Bash or other Linux-native shells.
- Consider including links or references to Linux-specific guidance for Azure Storage management.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-blobs-properties-metadata.md
...common/storage-use-azcopy-blobs-properties-metadata.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Shell Tip
Summary
The documentation provides AzCopy command examples that are generally cross-platform, but repeatedly highlights Windows Command Shell (cmd.exe) usage in tips, specifying double quotes for Windows and single quotes for other shells. This places Windows-specific guidance before Linux/macOS equivalents, and does not provide explicit Linux/macOS command-line examples or shell-specific notes beyond quoting. No PowerShell-specific examples or Windows-only tools are present, but the documentation does subtly prioritize Windows shell patterns.
Recommendations
- Provide explicit Linux/macOS shell examples alongside Windows examples, showing both quoting conventions and any relevant differences in command usage.
- Rephrase tips to mention Linux/macOS first or equally, e.g., 'Use single quotes in Linux/macOS shells and double quotes in Windows Command Shell (cmd.exe)'.
- Add a section clarifying cross-platform usage, including any environment-specific considerations (such as escaping, permissions, or installation differences).
- Include a table or sidebar summarizing quoting and syntax differences between Windows, Linux, and macOS shells.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-service-encryption.md
.../articles/storage/common/storage-service-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing BitLocker encryption as an analogy for Azure Storage encryption and linking to the Windows-specific Cryptography API: Next Generation (CNG) documentation. These references assume familiarity with Windows tools and concepts, and do not provide equivalent Linux analogies or resources. No command-line examples are given, so there is no explicit PowerShell or CLI bias, but the conceptual framing is Windows-centric.
Recommendations
- Provide Linux-equivalent analogies for encryption, such as referencing LUKS/dm-crypt for disk encryption.
- Include links to cross-platform or Linux cryptography documentation (e.g., OpenSSL, Linux kernel cryptography modules) alongside or instead of Windows CNG.
- Balance conceptual explanations by mentioning both Windows and Linux approaches to encryption where analogies are used.
- Ensure future documentation examples and references are platform-neutral or include both Windows and Linux perspectives.
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 demonstrates a mild Windows bias by listing PowerShell as the first example for creating a user delegation SAS, ahead of Azure CLI and SDKs for other languages. PowerShell is a Windows-centric tool, and its prioritization may suggest a preference for Windows environments. However, the page does provide Azure CLI and cross-platform SDK examples, and does not exclusively mention Windows tools or patterns elsewhere.
Recommendations
- Alternate the order of example links so that cross-platform tools (e.g., Azure CLI) are listed before or alongside PowerShell.
- Explicitly mention that Azure CLI and SDKs are cross-platform and suitable for Linux and macOS users.
- Add Bash shell examples where appropriate, especially for common SAS creation tasks.
- Ensure that references to PowerShell are balanced with equivalent Linux/macOS-friendly tooling throughout the documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-optimize.md
...articles/storage/common/storage-use-azcopy-optimize.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity but demonstrates mild Windows bias by referencing Windows Command Shell (cmd.exe) quoting conventions before Linux, and by providing Windows PowerShell syntax for environment variable setting before or alongside Linux equivalents. The tip about quoting prioritizes Windows-specific behavior, and Windows examples are given equal prominence to Linux, rather than Linux-first (which is more common in cloud-native documentation). There are no missing Linux examples, and Linux-specific optimization (concurrent scanning) is mentioned, but Windows tools and patterns are still foregrounded.
Recommendations
- Present Linux examples before Windows examples, as Linux is more common in cloud and server environments.
- In tips and notes, mention Linux conventions first, then Windows conventions.
- Consider using generic shell syntax (e.g., POSIX-compliant) as the default, with Windows-specific instructions in a separate note or tab.
- Expand Linux-specific optimization sections, such as concurrent scanning, and clarify if similar options exist for Windows.
- Ensure parity in troubleshooting and advanced usage examples for both platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-s3.md
.../main/articles/storage/common/storage-use-azcopy-s3.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows-specific credential setting commands first and providing both PowerShell and Command Prompt examples, while Linux and macOS are grouped together with a single export command. Additionally, there are several notes and tips specifically addressing Windows shell quoting conventions, with Windows (cmd.exe) called out separately. However, the AzCopy command examples themselves are cross-platform and do not use Windows-specific syntax.
Recommendations
- Present Linux, macOS, and Windows credential setting commands in parallel order or rotate which OS is listed first to avoid Windows-first bias.
- Provide more detailed shell-specific guidance for Linux and macOS (e.g., bash vs. zsh differences if relevant), not just for Windows.
- Include explicit examples of running AzCopy commands in Linux/macOS terminals, possibly with screenshots or shell prompt indications.
- Balance tips and notes about quoting and shell behavior by including Linux/macOS-specific advice where relevant, not just Windows cmd.exe.
- Consider adding troubleshooting or environment setup notes for Linux/macOS users, such as permissions, path setup, or package manager installation instructions.