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 1476-1500 of 1657 flagged pages
Storage
Quickstart: Azure Blob Storage library - Java
...rticles/storage/blobs/storage-quickstart-blobs-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell, CMD) and Linux (Bash) examples for key setup steps, but Windows/PowerShell instructions and terminology are often presented first or with more detail. Some output examples use Windows-style paths (e.g., C:\QuickStarts\blob-quickstart), and sign-in instructions include PowerShell before Bash. However, Linux instructions are present for all major steps, and the tooling (Java, Maven, Azure CLI) is cross-platform.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Include Linux output examples alongside Windows output (e.g., show both C:\... and /home/... paths).
- Ensure all CLI instructions are equally detailed for both Bash and PowerShell, and clarify that all commands work on macOS as well.
- Explicitly mention macOS compatibility where relevant.
- Where possible, use neutral file paths in output samples (e.g., ./blob-quickstart) or show both styles.
Create Pull Request
Storage
Configure cross-tenant customer-managed keys for a new storage account
...stomer-managed-keys-configure-cross-tenant-new-account.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration steps for Azure Storage cross-tenant customer-managed keys using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which may suggest a Windows-first bias. However, both PowerShell and CLI are cross-platform tools, and no Windows-only tools or patterns are used. There are no missing Linux/macOS examples, and the CLI instructions are clear and complete.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Explicitly mention that both PowerShell and Azure CLI are cross-platform and can be used on Windows, Linux, and macOS.
- Add a note clarifying that the instructions are applicable regardless of OS, and link to installation guides for both PowerShell Core and Azure CLI on Linux/macOS.
- Consider including Bash or shell script snippets for common tasks, if relevant.
Storage
Check the Last Sync Time property for a storage account
...lob/main/articles/storage/common/last-sync-time-get.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for checking the Last Sync Time property. However, the PowerShell example is presented first, and PowerShell is a Windows-centric tool, which may subtly signal a Windows-first approach. No Linux/macOS-specific shell examples (e.g., Bash) or notes about cross-platform usage are provided, though Azure CLI is cross-platform.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding a Bash example or clarifying that the CLI example is suitable for Bash/zsh/fish shells.
- Add a note that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
Storage
Understand storage account migration from classic to Azure Resource Manager
...es/storage/common/classic-account-migration-process.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions migration via Azure portal, PowerShell, or Azure CLI, but consistently lists PowerShell before Azure CLI and links to PowerShell migration guides before CLI equivalents. This ordering and emphasis may subtly prioritize Windows/PowerShell workflows over Linux/macOS/Azure CLI approaches, though CLI options are present.
Recommendations
- Alternate the order of PowerShell and Azure CLI mentions, or list Azure CLI first in some sections to avoid implicit prioritization.
- Ensure that all migration steps and linked guides have equivalent Azure CLI examples and are referenced equally.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider adding a table or section summarizing both PowerShell and Azure CLI commands for each migration step.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity between Windows (PowerShell) and cross-platform (Azure CLI, Terraform, Bicep, Azure Developer CLI) methods for creating and managing Azure storage accounts. However, PowerShell examples and instructions are consistently presented before Azure CLI equivalents, and PowerShell is referenced as a primary deployment method in several places. This ordering and emphasis may subtly signal a preference for Windows tooling, even though Linux/macOS users are fully supported via CLI, Terraform, and other methods.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to better reflect cross-platform usage.
- Explicitly state that Azure CLI, Terraform, Bicep, and Azure Developer CLI are fully supported on Linux/macOS and Windows.
- Add brief notes in the PowerShell sections clarifying that PowerShell Core is available on Linux/macOS, or link to cross-platform installation guides.
- Ensure that images and screenshots (where relevant) show both Windows and Linux/macOS environments, or use neutral representations like Cloud Shell.
- Consider grouping PowerShell and CLI instructions under a 'Command-line' heading to emphasize parity.
Storage
Configure an expiration policy for shared access signatures (SAS)
.../main/articles/storage/common/sas-expiration-policy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides configuration instructions for SAS expiration policy using the Azure portal, PowerShell, and Azure CLI. PowerShell instructions are presented before Azure CLI, and screenshots/examples for PowerShell are included, which may be more familiar to Windows users. However, Azure CLI instructions are present and fully functional for Linux/macOS users, and no Windows-only tools or patterns are required for the core task.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS, and provide example shell commands (e.g., bash) where appropriate.
- Include screenshots or output examples for Azure CLI similar to those shown for PowerShell to improve parity.
- Consider adding a table summarizing which tools are available on which platforms.
Storage
Network Connections in Azure Storage Explorer
...in/articles/storage/common/storage-explorer-network.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally describes proxy configuration options in a cross-platform manner, referencing OS proxy settings and environment variables that are standard on both Windows and Linux/macOS. However, in the section 'Which proxy source should I choose?', the guidance recommends trying 'system proxy' first, which may implicitly favor Windows users due to the prevalence and ease of GUI-based proxy configuration on Windows. There are no explicit Linux/macOS examples, nor are Linux-specific proxy configuration tools (like setting environment variables in bash or configuring proxies via GNOME/KDE) mentioned.
Recommendations
- Add explicit examples for configuring proxy environment variables on Linux/macOS (e.g., setting HTTP_PROXY in bash/zsh).
- Clarify that 'system proxy' refers to OS-level settings on all platforms, and provide links or instructions for configuring system proxies on Linux and macOS (e.g., GNOME/KDE network settings, macOS System Preferences).
- Include notes or examples for common Linux/macOS proxy authentication scenarios.
- Ensure parity in troubleshooting steps for certificate issues, mentioning platform-specific certificate stores and import procedures.
Storage
Choose an Azure solution for data transfer
...torage/common/storage-choose-data-transfer-solution.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents Azure data transfer solutions in a cross-platform manner, mentioning tools and SDKs available for multiple operating systems. However, in the 'Next steps' section, the PowerShell quickstart is listed before the Azure CLI quickstart, which may subtly prioritize Windows users. Additionally, PowerShell is highlighted as a scriptable tool alongside AzCopy and Azure CLI, but no explicit Linux/macOS shell examples are given, and PowerShell is more closely associated with Windows environments.
Recommendations
- List Azure CLI quickstart before or alongside PowerShell quickstart to avoid Windows-first ordering.
- Explicitly mention that AzCopy and Azure CLI are cross-platform and provide links or examples for Linux/macOS usage.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, or provide Bash shell examples for parity.
- Ensure graphical tools (like Storage Explorer) are noted as cross-platform where applicable.
Storage
Replace Azure Blob Storage properties & metadata with AzCopy
...common/storage-use-azcopy-blobs-properties-metadata.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides AzCopy command examples that are cross-platform, but the tips about quoting path arguments mention Windows Command Shell (cmd.exe) first and provide guidance for Windows users before Linux/macOS users. All examples use single quotes, which are correct for Linux/macOS, but the documentation does not show explicit Linux/macOS command examples or mention Bash/Zsh shells by name.
Recommendations
- Explicitly mention Linux/macOS shells (e.g., Bash, Zsh) when describing quoting requirements.
- Provide example commands for both Windows (cmd.exe, using double quotes) and Linux/macOS (using single quotes), or clarify which shell each example is for.
- Consider showing both quoting styles side-by-side for clarity.
- Add a brief note confirming AzCopy is fully supported on Linux/macOS and link to installation instructions for those platforms.
Storage
Find errors & resume jobs with logs in AzCopy (Azure Storage)
...rticles/storage/common/storage-use-azcopy-configure.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates minor Windows bias in its log review section: the only example given for searching for errors in log files uses the PowerShell Select-String command, which is not available by default on Linux/macOS. No Linux/macOS equivalent (e.g., grep) is provided, even though the section is labeled '[Linux]'. Other sections correctly provide both Windows (PowerShell) and Linux (bash) environment variable examples, and general AzCopy commands are cross-platform.
Recommendations
- Provide a Linux/macOS-specific example for searching log files, such as: grep UPLOADFAILED ./04dc9ca9-158f-7945-5933-564021086c79.log
- Ensure that all code tabs labeled '[Linux]' use native Linux/macOS tools rather than PowerShell commands.
- Consider listing Linux/macOS examples first or side-by-side with Windows examples for parity.
Storage
Grant limited access to data with shared access signatures (SAS)
...b/main/articles/storage/common/storage-sas-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides both PowerShell and Azure CLI links for creating user delegation SAS, but PowerShell is listed first, which may subtly prioritize Windows tooling. There is a notable emphasis on PowerShell in the 'Get started with SAS' section, and a specific best practice note references AzCopy (a cross-platform tool, but historically Windows-centric) for date/time formatting. However, Linux/macOS equivalents (Azure CLI, SDKs for Python, Java, etc.) are also present and linked, and no critical steps are Windows-only.
Recommendations
- List Azure CLI examples before or alongside PowerShell to avoid implicit Windows prioritization.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users where relevant.
- In best practices, clarify that AzCopy is available on Linux/macOS and provide links to installation/use on those platforms.
- Where PowerShell is referenced, add a note or alternative example for Bash/Azure CLI usage.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides a broad overview of Azure Files, emphasizing cross-platform compatibility. However, there are subtle signs of Windows bias: PowerShell is mentioned as a primary scripting tool before Azure CLI, Windows-specific tools like Azure File Sync are highlighted, and Windows mounting instructions are listed before Linux/macOS in the 'Next steps' section. References to Windows-centric features and tools appear earlier or more prominently than their Linux equivalents.
Recommendations
- Mention Azure CLI before or alongside PowerShell when discussing scripting and tooling.
- Highlight Linux and macOS mounting instructions equally, and consider rotating the order in 'Next steps' or grouping by OS.
- When discussing Azure File Sync or other Windows-only tools, clarify their OS specificity and suggest Linux/macOS alternatives or note their absence.
- Add more explicit references to Linux/macOS tooling and workflows where possible, such as mentioning NFS and SMB mounting commands or utilities.
- Ensure that examples and case studies include Linux/macOS scenarios, not just Windows environments.
Storage
Authorize access to blobs using Microsoft Entra ID
...orage/blobs/authorize-access-azure-active-directory.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell before Azure CLI in several places and referencing PowerShell examples without equal emphasis on Linux/macOS usage. While Azure CLI is mentioned, there are no explicit Linux/macOS-specific instructions or examples, and PowerShell is referenced as a primary tool, which is more closely associated with Windows environments. No Linux/macOS terminal or shell examples are provided, and the documentation does not clarify cross-platform usage for command-line tools.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell, as Azure CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide sample commands for those platforms.
- Add notes or examples for Linux/macOS users, such as using Bash or zsh with Azure CLI.
- Clarify that PowerShell Core is available cross-platform, if relevant, and provide installation or usage guidance for non-Windows users.
- Where possible, include screenshots or walkthroughs using Linux/macOS terminals.
Storage
Best practices for monitoring Azure Blob Storage
...les/storage/blobs/blob-storage-monitoring-scenarios.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell example for decoding a SAS token signature and mentions 'any tool or SDK' for SHA-256 hashing, but only gives a detailed PowerShell command before the Linux equivalent. The Linux example is provided, but appears after the Windows/PowerShell example, indicating a slight 'Windows-first' bias. Most other monitoring and querying examples are platform-agnostic (Kusto, SQL, Azure Portal), but the explicit scripting example favors Windows/PowerShell.
Recommendations
- Present Linux/macOS and Windows/PowerShell examples side-by-side or in parallel, rather than listing Windows first.
- Include bash or Python examples for decoding SAS tokens before or alongside PowerShell examples.
- Clarify that all steps can be performed on Linux/macOS and Windows, and link to cross-platform tools where appropriate.
- Where possible, use platform-neutral language and examples for scripting and command-line operations.
Storage
Use Azure CLI to manage ACLs in Azure Data Lake Storage
...in/articles/storage/blobs/data-lake-storage-acl-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform, focusing on Azure CLI commands that work on Windows, Linux, and macOS. However, there is a minor Windows bias in the 'Ensure that you have the correct version of Azure CLI installed' section, where Windows PowerShell is mentioned as the example console application before any Linux/macOS alternatives. No Linux/macOS terminal examples or explicit mentions are provided, and screenshots do not show OS-specific shells.
Recommendations
- In the prerequisites and setup sections, mention Linux/macOS terminal applications (e.g., Bash, Terminal) alongside Windows PowerShell.
- Add a note clarifying that Azure CLI commands work identically on Windows, Linux, and macOS.
- Where console applications are referenced, use neutral phrasing such as 'open a terminal or command prompt on your operating system (e.g., PowerShell, Command Prompt, Bash, Terminal)'.
- Include screenshots or examples from Linux/macOS terminals where appropriate.
Storage
Access control lists in Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-access-control.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a balanced overview of POSIX-like ACLs in Azure Data Lake Storage, which is inherently cross-platform. However, there are signs of mild Windows bias: PowerShell is listed as a primary method for managing ACLs, and Windows-centric tools (Azure Storage Explorer, PowerShell) are mentioned before Linux-native equivalents. While Azure CLI is included and examples reference Linux concepts (umask, POSIX), there are no explicit Linux shell (e.g., Bash) or macOS Terminal examples for managing ACLs directly. The documentation does not mention Linux file utilities (setfacl, getfacl) or show how to interact with ADLS from a Linux shell, which could help Linux/macOS users.
Recommendations
- Add explicit Linux/macOS shell examples for managing ACLs (e.g., using Azure CLI in Bash, or REST API calls from curl).
- Mention Linux file utilities (setfacl, getfacl) in the context of POSIX ACLs, clarifying how Azure's implementation compares.
- Ensure that cross-platform tools (Azure CLI, REST API) are listed before or alongside Windows-specific tools (PowerShell, Storage Explorer).
- Clarify that Azure Storage Explorer is available on Linux/macOS, or provide alternatives if not.
- Add a section or note on best practices for Linux/macOS users managing ACLs.
Storage
Best practices for using Azure Data Lake Storage
...cles/storage/blobs/data-lake-storage-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples and tool recommendations for both Windows and cross-platform environments, but Windows-centric tools (Azure PowerShell, PowerShell) are frequently listed before their Linux/macOS equivalents (Azure CLI, REST). In several tables and sections, PowerShell is mentioned first, and there is a slight emphasis on Windows patterns. However, Linux-friendly tools (CLI, REST, AzCopy, DistCp, SDKs) are also consistently included, and no critical functionality is Windows-only.
Recommendations
- Alternate the order of tool listings so that Azure CLI and REST examples are shown before or alongside PowerShell, especially in tables and introductory text.
- Explicitly mention platform compatibility for each tool (e.g., 'Azure CLI: cross-platform', 'PowerShell: Windows/macOS/Linux').
- Add more Linux/macOS-specific usage notes or examples where appropriate, especially for ingestion and monitoring tasks.
- Ensure that screenshots and diagrams do not exclusively show Windows environments.
- Where possible, link to both PowerShell and CLI documentation for common tasks.
Storage
Encryption scopes for Blob storage
...in/articles/storage/blobs/encryption-scope-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, but in the section about Azure Key Vault soft-delete, the PowerShell example is listed before the CLI example, which is a minor instance of Windows-first bias. No other evidence of Windows bias, such as exclusive use of Windows/PowerShell tools or missing Linux/macOS examples, is present.
Recommendations
- List CLI examples before PowerShell examples, or present both together with equal prominence.
- Ensure that any future command-line instructions or tooling references include both PowerShell and CLI (az) examples, with clear notes on cross-platform compatibility.
Storage
Container-level WORM policies for immutable blob data
...orage/blobs/immutable-container-level-worm-policies.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides both PowerShell and Azure CLI examples for deleting containers with WORM policies, but PowerShell (a Windows-centric tool) is mentioned first and in more detail. The CLI example is present, but the explanation and ordering prioritize PowerShell, which may create a perception of Windows preference. No Linux/macOS-specific tools or patterns are missing, and the CLI example ensures Linux parity for the main operation.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) to reassure non-Windows users.
- Where PowerShell is referenced, clarify that Azure CLI is the recommended tool for Linux/macOS environments.
- Consider adding a short note or table summarizing which tools are available on which platforms.
Storage
Version-level WORM policies for immutable blob data
...storage/blobs/immutable-version-level-worm-policies.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references PowerShell commands (Remove-AzRmStorageContainer, Remove-AzStorageContainer) before mentioning Azure CLI equivalents for deleting containers with immutable policies. This ordering and explicit mention of PowerShell may create a perception of Windows-first bias, especially since PowerShell is traditionally associated with Windows, even though cross-platform versions exist. However, the Azure CLI example is present, and no critical steps are Windows-only.
Recommendations
- Present Azure CLI examples before or alongside PowerShell commands, as Azure CLI is natively cross-platform and preferred by many Linux/macOS users.
- Explicitly note that PowerShell Core is available cross-platform, or provide Bash examples where relevant.
- Ensure all command-line examples have both Azure CLI and PowerShell syntax, or link to equivalent documentation for both.
- Clarify that the Azure portal and REST API are platform-agnostic.
Storage
SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage
...age/blobs/secure-file-transfer-protocol-performance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for increasing SFTP message size, but Windows is mentioned first in the example list. The SFTP client recommendations (WinSCP, FileZilla) are cross-platform, but WinSCP (Windows-only) is described in detail, while FileZilla is only briefly mentioned. No Linux-specific SFTP client configuration is discussed beyond the OpenSSH command-line example.
Recommendations
- Alternate the order of Windows and Linux examples, or present them together to avoid implicit prioritization.
- Provide equivalent configuration details for a popular Linux SFTP client (e.g., FileZilla or lftp), such as how to set concurrent connections or adjust logging.
- Clarify that WinSCP is Windows-only and suggest Linux/macOS alternatives with similar configuration instructions.
- Expand the section on client configuration to include Linux/macOS GUI clients where relevant.
Storage
Quickstart: Azure Blob storage library v12 - JS Browser
...s/storage/blobs/quickstart-blobs-javascript-browser.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation occasionally lists Windows tools (cmd, PowerShell) before Linux equivalents (Bash) when describing how to open a console window for project setup. Visual Studio Code is recommended as the editor, which is cross-platform. All code examples and instructions are platform-neutral (JavaScript, npm, browser), and there are no Windows-only tools or PowerShell-specific commands. No Linux/macOS examples are missing, and no Windows-specific patterns are enforced.
Recommendations
- When mentioning console windows, list Bash (Linux/macOS) first or equally alongside cmd/PowerShell.
- Explicitly state that all steps can be performed on Linux/macOS, and mention alternative editors if desired.
- Add a note that Visual Studio Code and npm are available cross-platform.
- If possible, provide screenshots or brief notes for Linux/macOS users (e.g., opening a terminal, using VS Code).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity between Azure Portal, PowerShell, Azure CLI, and ARM template methods for enabling blob soft delete. However, there is a mild Windows bias: PowerShell is featured prominently and referenced before Azure CLI in several sections, and instructions for using Azure CLI locally mention 'Windows PowerShell' as the example console application, rather than a cross-platform shell like Bash or Zsh. There are no Linux-specific examples or explicit mentions of Linux/macOS shells, though the CLI commands themselves are cross-platform.
Recommendations
- When referencing Azure CLI usage, mention cross-platform shells (e.g., Bash, Zsh, Terminal) alongside Windows PowerShell.
- Provide example CLI commands with both Windows (backslash line continuation) and Linux/macOS (backslash or backtick) syntax, or clarify that CLI commands work on all platforms.
- Consider listing Azure CLI before PowerShell in sections, as CLI is cross-platform and PowerShell is more Windows-centric.
- Add a note clarifying that PowerShell commands can be run on Linux/macOS with PowerShell Core, if relevant.
Storage
SFTP support for Azure Blob Storage
...storage/blobs/secure-file-transfer-protocol-support.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and SFTP-focused, but in the 'Home directory' section, the only explicit SFTP command example references 'Open SSH' with a link to Windows Server OpenSSH documentation, and the code blocks are marked as 'powershell'. This subtly prioritizes Windows/PowerShell context, even though the SFTP commands themselves are cross-platform. No Linux/macOS-specific examples or references are provided, and the linked SSH documentation is Windows-centric.
Recommendations
- Provide explicit Linux/macOS SFTP usage examples or clarify that the SFTP commands are the same across platforms.
- Use neutral code block labeling (e.g., 'bash' or none) for SFTP command examples instead of 'powershell', since SFTP is not PowerShell-specific.
- When referencing OpenSSH, link to general OpenSSH documentation or include both Windows and Linux/macOS OpenSSH links.
- Add a note that SFTP clients are available on all major platforms, and that the commands shown work on Linux, macOS, and Windows.
Storage
Reacting to Azure Blob storage events
.../articles/storage/blobs/storage-blob-event-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists PowerShell as a primary tool for quickstart examples, placing it before Azure CLI. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its mention before CLI may suggest a Windows-first approach. However, Azure portal and CLI options are also provided, ensuring Linux/macOS users are not blocked.
Recommendations
- List Azure CLI before PowerShell in quickstart tables and sections, as CLI is natively cross-platform.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify when examples are Windows-specific.
- Provide Bash or shell script examples where relevant, especially in sections about event consumption.
- Ensure that all code samples and tool recommendations are clearly marked as cross-platform or platform-specific.