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 1001-1025 of 1657 flagged pages
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Links First
Missing Linux Example
Summary
The documentation exhibits a subtle Windows bias, primarily by referencing Windows-specific quick start guides and documentation links before or instead of Linux equivalents. Although the main migration example uses a Linux source host, there is a lack of parity in providing Linux-focused Azure VM documentation or explicit Linux command-line examples for Azure VM preparation. The 'Next steps' and 'Implementation guide' sections link to Windows-centric Azure documentation, and there is no mention of Linux-specific Azure VM setup or troubleshooting.
Recommendations
- Provide parallel links to both Windows and Linux Azure VM quick start guides in the 'Implementation guide' and 'Next steps' sections.
- Include explicit Linux command-line examples for common tasks (e.g., mounting disks, verifying device status) alongside any Windows or PowerShell equivalents.
- Reference Linux-specific Azure documentation (e.g., /azure/virtual-machines/linux/quick-create-portal) wherever Windows documentation is mentioned.
- Clarify in prerequisites and steps that both Windows and Linux hosts are supported, and provide OS-specific guidance where relevant.
- Ensure screenshots and instructions are balanced between Windows and Linux environments, or clearly indicate when instructions are OS-agnostic.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/solution-integration/validated-partners/primary-secondary-storage/nasuni-deployment-guide.md
...s/primary-secondary-storage/nasuni-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently uses Windows-centric terminology, UI screenshots, and workflow descriptions (e.g., 'Windows Azure Platform', Azure Portal GUI steps, and Windows-style screenshots). There are no CLI, PowerShell, or Linux shell examples, nor are there references to Linux tools or workflows. The guide assumes the use of the Azure Portal web interface, which is more common in Windows environments, and does not mention or provide parity for Linux-based approaches (such as Azure CLI or automation via shell scripts).
Recommendations
- Provide equivalent instructions for creating and managing Azure Storage accounts using Azure CLI and/or Azure PowerShell, with explicit Linux shell examples.
- Include screenshots or text-based examples for both Windows and Linux environments, or use neutral, cross-platform screenshots where possible.
- When referencing 'Windows Azure Platform', clarify that the steps are applicable to all platforms, or provide a Linux/Unix alternative where appropriate.
- Add a section or callouts for Linux administrators, including how to retrieve credentials and configure firewalls using CLI tools.
- Avoid using Windows-specific terminology (e.g., 'Windows Azure Platform') as the only option in dropdowns or examples; use 'Microsoft Azure' or 'Azure' unless the step is truly Windows-specific.
- Explicitly state that the Nasuni Edge Appliance can be deployed and managed from Linux environments, and provide links or references to relevant Linux documentation.
Storage
Migrate to Azure Files using Azure Storage Mover
.../articles/storage/files/migrate-files-storage-mover.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Windows-centric migration tools (Robocopy) and mentions Azure PowerShell before Azure CLI, which may imply a Windows-first approach. There are no explicit Linux-specific migration examples, commands, or troubleshooting steps, despite Storage Mover supporting SMB shares from Linux and NAS sources. The agent deployment instructions mention Hyper-V and VMware but do not clarify Linux VM support or provide Linux-specific agent installation steps.
Recommendations
- Add explicit Linux agent deployment instructions, including supported Linux distributions and installation commands.
- Provide Linux-oriented examples for agent registration (e.g., SSH commands on Linux terminals).
- Mention Azure CLI and PowerShell equally, or provide CLI-first instructions for cross-platform parity.
- Include troubleshooting tips or FAQs for common Linux/NAS migration scenarios.
- Clarify if the agent can run on Linux VMs and provide guidance for those environments.
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
Missing Linux Example
Summary
The documentation page provides a generally cross-platform approach for configuring a Site-to-Site VPN for Azure Files, with Azure Portal, PowerShell, and CLI instructions. However, there is a notable Windows bias in the 'Prerequisites' section, where Windows Server RRAS is mentioned as the only example of an on-premises VPN appliance, with no Linux alternatives suggested. Additionally, the example for retrieving the public IP address of the Azure VPN gateway is given only in PowerShell, with no CLI or Linux equivalent. While mounting instructions are linked for all major OSes, the initial guidance and examples tend to mention or prioritize Windows tools and patterns.
Recommendations
- In the 'Prerequisites' section, mention common Linux-based VPN appliances (e.g., strongSwan, OpenVPN, libreswan) as alternatives to Windows Server RRAS, and link to relevant configuration guides.
- When showing how to retrieve the public IP address of the Azure VPN gateway, provide both PowerShell and Azure CLI examples to ensure parity for Linux/macOS users.
- Where possible, avoid implying Windows Server is the default or only supported option for on-premises VPN appliances.
- Consider adding a brief note or table listing popular cross-platform VPN devices and linking to Azure's tested devices list, highlighting both Windows and Linux options.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides extensive PowerShell and Windows-specific guidance, especially for advanced SMB configuration (e.g., enabling SMB Multichannel on older OSes, setting encryption ciphers), but does not offer equivalent Linux/macOS client configuration examples. While Azure CLI examples are present (which are cross-platform), client-side instructions for Linux/macOS (such as how to configure SMB encryption or multichannel support) are missing. Windows terminology and tools (e.g., PowerShell, registry edits, Set-SmbClientConfiguration) are referenced exclusively or before any Linux alternatives.
Recommendations
- Add Linux and macOS client configuration examples for SMB Multichannel and SMB encryption settings, including how to check and enable these features using smb.conf or relevant tools.
- Where PowerShell or Windows registry edits are shown, provide analogous steps for Linux/macOS (or explicitly state if not supported).
- When referencing client-side configuration (e.g., setting encryption ciphers), include commands for Linux (e.g., using mount.cifs options or smb.conf parameters).
- Balance the order of examples so that Linux/macOS are not always listed after Windows, especially in sections not inherently Windows-specific.
- Clarify any features that are Windows-only, and explicitly note if equivalent Linux/macOS functionality is unavailable.
Storage
Improve SMB Azure File Share Performance
...cs/blob/main/articles/storage/files/smb-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Windows and Linux guidance for SMB Multichannel, including explicit Linux kernel and mount command examples. However, Windows tools (robocopy, diskspd.exe) and PowerShell commands are used exclusively for performance testing and configuration verification, with no Linux equivalents or parity in example tooling. Windows configuration and verification steps are described in greater detail and appear before Linux examples. Feature registration instructions are given only for Azure Portal and Azure PowerShell, with no mention of Azure CLI or ARM templates, which are cross-platform.
Recommendations
- Add Linux equivalents for performance testing, such as using fio or dd for load generation and performance measurement.
- Provide Linux commands for verifying SMB Multichannel configuration and status (e.g., using smbstatus, dmesg, or reviewing mount options).
- Include Azure CLI or ARM template instructions for feature registration, not just Azure PowerShell, to improve cross-platform accessibility.
- Balance the order of Windows and Linux sections/examples so Linux is not always presented after Windows.
- Reference Linux documentation for SMB Multichannel alongside Windows documentation in the 'Next steps' section.
Storage
Create multiple Azure Elastic SAN volumes in a batch
...storage/elastic-san/elastic-san-batch-create-sample.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides a PowerShell script for batch creation of Azure Elastic SAN volumes, with file path examples and scripting patterns typical of Windows environments. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI), nor mention of cross-platform alternatives. The use of Windows-style file paths and PowerShell-specific cmdlets further reinforces the Windows bias.
Recommendations
- Add equivalent Azure CLI or Bash script examples for batch volume creation.
- Include notes on how to run the process on Linux/macOS (e.g., file path formats, prerequisites).
- Clarify whether PowerShell Core (cross-platform) is supported, and provide guidance if so.
- Present examples for both Windows and Linux/macOS environments, or explicitly state platform requirements.
Storage
Limitations & known issues with SFTP in Azure Blob Storage
...ge/blobs/secure-file-transfer-protocol-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page mentions WinSCP (a Windows SFTP client) exclusively in the 'Client settings' section and provides configuration guidance only for it. There are no equivalent examples or recommendations for popular Linux/macOS SFTP clients (such as OpenSSH's sftp, FileZilla, or lftp). This creates a subtle Windows-first bias and may leave Linux/macOS users without clear guidance for optimal client configuration.
Recommendations
- Add configuration guidance for common Linux/macOS SFTP clients (e.g., OpenSSH's sftp, FileZilla, lftp), especially if there are known settings or behaviors that impact compatibility or performance.
- Where client-specific settings are discussed, present Windows and Linux/macOS clients in parallel or clarify if issues are unique to a particular client.
- Include troubleshooting tips or notes for Linux/macOS users if there are known issues or differences in behavior.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Storage Analytics logging demonstrates a moderate Windows bias. PowerShell is the only command-line example provided for filtering log blobs, with no equivalent Azure CLI, Bash, or Linux/macOS shell example. References to 'win32' and 'Windows_NT' in sample log entries and user agent strings further reinforce a Windows-centric perspective. While the page mentions enabling logging via Azure CLI, no CLI or Linux/macOS-specific instructions or examples are given, and PowerShell is prioritized in example code.
Recommendations
- Provide equivalent Azure CLI and Bash examples for listing and filtering log blobs, alongside PowerShell.
- Explicitly mention that the PowerShell example is for Windows, and offer cross-platform alternatives.
- Include sample log entries or user agent strings from Linux/macOS clients (e.g., azcopy on Linux, Azure Storage Explorer on macOS).
- Clarify that Storage Analytics logging is platform-agnostic and can be managed from any OS.
Storage
Call REST API operations with Shared Key authorization
.../main/articles/storage/common/storage-rest-api-auth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and C#. All code samples and instructions assume use of Visual Studio, with no mention of Linux/macOS alternatives (e.g., VS Code, JetBrains Rider, or CLI-based workflows). There are no examples in other languages or instructions for running the sample on Linux/macOS, despite REST APIs being cross-platform. The only tool mentioned for inspecting HTTP traffic is Fiddler, which is primarily Windows-focused.
Recommendations
- Add instructions for running the sample code on Linux/macOS, such as using .NET Core/SDK and VS Code or JetBrains Rider.
- Mention cross-platform alternatives to Visual Studio, and clarify that the sample can be built and run on Linux/macOS using the .NET CLI.
- Provide examples of inspecting HTTP traffic using cross-platform tools like Wireshark or mitmproxy, in addition to Fiddler.
- Include a note that the REST API can be called from any platform and provide sample code in a language commonly used on Linux/macOS (e.g., Python, JavaScript, or Bash with curl).
- Explicitly state that the sample is not Windows-only and provide parity guidance for non-Windows 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 command examples, and does not provide any Linux/macOS path examples (e.g., '/home/user/myTextFile.txt'). While there are tips about quoting differences between shells, all concrete examples use Windows paths, which may confuse or inconvenience Linux/macOS users.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., '/home/user/myTextFile.txt') alongside Windows examples.
- Explicitly mention that AzCopy works on Linux/macOS and clarify any platform-specific behaviors.
- Alternate the order of examples so that Linux/macOS examples are shown first in some sections.
- Add a short section or note about common Linux/macOS shell usage patterns with AzCopy.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides Azure CLI examples for managing block blobs, but several code samples use Windows-style file paths (e.g., C:\temp\), and instructions for creating required files reference Windows locations (e.g., C:\temp\bloblist.xml). There are no explicit Linux/macOS path examples, and the file path conventions may confuse or hinder Linux/macOS users. The documentation does not mention Linux/macOS equivalents or clarify cross-platform usage for file paths and locations.
Recommendations
- Provide Linux/macOS path examples alongside Windows paths (e.g., /tmp/downloads/).
- Clarify that file paths should be adapted to the user's OS and provide guidance for both Windows and Linux/macOS users.
- When referencing file creation (such as blob-list.xml), include instructions or examples for both Windows and Linux/macOS environments.
- Consider using environment variables or platform-agnostic paths in sample scripts.
- Add a note at the beginning of the article stating that examples use Windows paths by default and should be adapted for other platforms.
Storage
Use Azure CLI to manage data (Azure Data Lake Storage)
...rage/blobs/data-lake-storage-directory-file-acl-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily uses Windows-centric file paths (e.g., 'C:\myFolder\upload.txt') in its upload/download examples and refers to Windows PowerShell as the example local CLI environment. There are no explicit Linux/macOS shell examples, nor are Linux-style file paths (e.g., '/home/user/upload.txt') shown. This may cause confusion or friction for Linux/macOS users.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., '/home/user/upload.txt') for upload/download commands.
- Mention common Linux/macOS terminal applications (e.g., Bash, Terminal) alongside Windows PowerShell when describing how to run Azure CLI locally.
- Add notes clarifying that file path syntax should match the user's operating system.
- Consider alternating or combining Windows and Linux/macOS examples for file operations.
Storage
Known issues with Azure Data Lake Storage
...ticles/storage/blobs/data-lake-storage-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page for Azure Data Lake Storage known issues shows moderate Windows bias. PowerShell is mentioned as a primary tool for managing soft-deleted blobs and directories, with Azure CLI listed as an alternative but after PowerShell. Windows-specific tools such as AzCopy and Azure Storage Explorer are referenced without explicit mention of Linux/macOS alternatives or usage notes. Examples and tool recommendations tend to list Windows-centric options first, and there are no explicit Linux/macOS command-line examples or guidance for parity.
Recommendations
- Provide explicit Linux/macOS usage instructions for AzCopy, Azure CLI, and Azure Storage Explorer, including installation and command-line examples.
- List Azure CLI before or alongside PowerShell when presenting options for managing blobs and directories, as CLI is cross-platform.
- Add notes or links to documentation for using these tools on Linux/macOS, including any limitations or differences.
- Where possible, include screenshots or examples from Linux/macOS environments to demonstrate parity.
- Clarify that AzCopy and Azure Storage Explorer are cross-platform, and provide download links for all supported OSes.
Storage
Configure a lifecycle management policy
...storage/blobs/lifecycle-management-policy-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for configuring Azure Blob Storage lifecycle management policies using the Azure Portal, PowerShell, Azure CLI, and ARM templates. The PowerShell section is detailed and includes a full example, while the Azure CLI section is much briefer and lacks a full end-to-end example. The PowerShell example is presented before the Azure CLI example, which may indicate a Windows-first bias. There are no Linux-specific tools or shell examples (e.g., Bash scripting), and the CLI instructions are generic, not tailored for Linux/macOS environments.
Recommendations
- Provide a more detailed Azure CLI example, including how to construct the JSON policy file and use CLI commands in a Linux/macOS shell environment.
- Include Bash shell scripting examples for Linux/macOS users, showing how to automate policy creation and management.
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly mention that Azure CLI works on Linux/macOS and provide any OS-specific notes if relevant.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides platform-specific examples for Azure portal, PowerShell, Azure CLI, and .NET. PowerShell examples are given in detail and presented before Azure CLI, which may suggest a Windows-first approach. There is no explicit mention of Linux/macOS equivalents for PowerShell, nor any Bash or shell scripting examples. However, Azure CLI is cross-platform and its inclusion mitigates some bias, but the ordering and depth of PowerShell coverage may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash/shell scripting examples where relevant, especially for automation scenarios.
- Explicitly state platform compatibility for each tool (e.g., PowerShell Core vs. Windows PowerShell).
- Ensure parity in depth and detail between PowerShell and Azure CLI sections.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive PowerShell examples and references, including file paths and commands that are most familiar to Windows users. PowerShell is presented as a primary automation method alongside Azure CLI, and several examples use Windows-style file paths (e.g., C:\temp\json.txt). While Azure CLI is covered and is cross-platform, PowerShell examples and terminology may create friction for Linux/macOS users. Additionally, PowerShell is listed before Azure CLI in most sections, and some instructions (such as saving or reading JSON files) use Windows conventions.
Recommendations
- Add Bash shell examples for key tasks, especially for file handling (e.g., saving and reading JSON files) to demonstrate Linux/macOS parity.
- Use platform-neutral file paths in examples (e.g., /tmp/json.txt or ./policy.json), or provide both Windows and Linux/macOS variants.
- Clarify that PowerShell Core is available cross-platform, and link to installation instructions for Linux/macOS where relevant.
- Where PowerShell is referenced, note that Azure CLI is fully supported and may be preferable for Linux/macOS users.
- Consider alternating the order of PowerShell and Azure CLI examples, or default to CLI first in sections not inherently Windows-centric.
Storage
Quickstart: Azure Blob Storage library - C++
...articles/storage/blobs/quickstart-blobs-c-plus-plus.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, especially in the project setup and initial instructions. Visual Studio is presented as the default IDE, and the project creation steps are tailored for Windows users. The use of vcpkg is shown with the Windows executable (vcpkg.exe), and screenshots and instructions focus on Visual Studio dialogs for creating a Windows console app. Linux instructions are present for setting environment variables, but overall, Windows tools and patterns are introduced first and more prominently.
Recommendations
- Add explicit instructions and screenshots for setting up a C++ project on Linux/macOS using CMake or other common tools.
- Show vcpkg usage with cross-platform commands (e.g., ./vcpkg install ...) and clarify platform differences.
- Include guidance for using alternative IDEs (e.g., VS Code, CLion) or command-line workflows for non-Windows users.
- Present Linux/macOS environment variable setup instructions before or alongside Windows instructions.
- Avoid assuming Visual Studio as the default development environment; mention alternatives in the prerequisites and setup sections.
Storage
Host keys for SFTP support for Azure Blob Storage
...orage/blobs/secure-file-transfer-protocol-host-keys.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides examples for both Linux/macOS (known_hosts) and Windows (WinSCP registry key), but the Windows-specific client (WinSCP) and its registry storage are given a dedicated section, while no equivalent is given for Linux GUI SFTP clients. Windows-specific file paths (C:\Users\<user>/.ssh/known_hosts) are shown in error messages before the Linux/macOS equivalents. The registry key example is Windows-only, and the code sample uses a .NET library (SSH.NET), which is cross-platform but most commonly used on Windows.
Recommendations
- Add examples for popular Linux/macOS GUI SFTP clients (e.g., FileZilla, Cyberduck) and how they store host keys.
- When showing file paths, present Linux/macOS paths first or alongside Windows paths (e.g., ~/.ssh/known_hosts and C:\Users\<user>/.ssh/known_hosts).
- Clarify that the registry key example is specific to Windows and provide parity for Linux/macOS client configuration.
- Consider including a Python paramiko example, which is widely used on Linux/macOS.
- Explicitly mention that the known_hosts file location and format applies to Linux/macOS and Windows (with OpenSSH), and highlight differences if any.
Storage
Connect to Azure Blob Storage from an SFTP client
...blobs/secure-file-transfer-protocol-support-connect.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only a Windows PowerShell example for connecting to Azure Blob Storage via SFTP, referencing OpenSSH on Windows. There are no Linux/macOS command-line examples, and Windows tooling is presented first and exclusively, despite SFTP being a cross-platform protocol.
Recommendations
- Add equivalent Linux/macOS command-line examples (e.g., using sftp from a Bash shell).
- Present cross-platform connection instructions, or clarify that the example applies to all platforms.
- Mention that OpenSSH is available by default on most Linux/macOS systems, and provide installation guidance for those platforms if needed.
- Consider showing Linux/macOS examples before or alongside Windows examples to avoid implicit prioritization.
Storage
Tutorial - Simulate a failure in reading data from the primary region
...icles/storage/blobs/simulate-primary-region-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Windows and Linux command-line examples for static routing, ensuring parity for that method. However, the alternative method relies exclusively on Fiddler, a Windows-only GUI tool, with no mention of Linux/macOS equivalents or alternatives. Additionally, Fiddler is introduced before any Linux-compatible method for simulating failures using network tools.
Recommendations
- Include instructions for simulating HTTP failures using cross-platform tools such as mitmproxy or similar for Linux/macOS users.
- Explicitly mention that Fiddler is Windows-only and suggest alternatives for other platforms.
- Consider presenting Linux/macOS-compatible methods before or alongside Windows-specific tools to avoid Windows-first bias.
Storage
Example Azure role assignment conditions for Blob Storage
...n/articles/storage/blobs/storage-auth-abac-examples.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides detailed step-by-step examples for configuring Azure Blob Storage role assignment conditions using the Azure Portal and Azure PowerShell. However, there are no CLI (az CLI), Bash, or cross-platform scripting examples. All command-line automation is shown exclusively with Azure PowerShell, which is primarily a Windows-first tool, though it is available cross-platform. There are no explicit references to Windows-only tools, but the absence of az CLI or Bash examples creates friction for Linux/macOS users.
Recommendations
- Add equivalent examples using the Azure CLI (az role assignment) for all scenarios where PowerShell is shown.
- Where scripting is demonstrated, provide Bash or shell script equivalents alongside PowerShell.
- Clarify in the prerequisites or introduction that PowerShell examples are cross-platform, but also link to az CLI documentation for Linux/macOS users.
- For testing and automation, show both PowerShell and az CLI command sequences.
- Consider including a note or section for Linux/macOS users, highlighting any differences or preferred tools.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides enablement instructions for the Azure Blob Storage change feed using four methods: Portal, Azure CLI, PowerShell, and ARM template. The PowerShell section is notably detailed, including installation steps for PowerShellGet and Az.Storage, which are Windows-centric. The PowerShell instructions are given equal prominence to Azure CLI, but the CLI example is brief and does not mention Linux/macOS compatibility or potential differences. There is a subtle Windows-first bias in the enable/disable section, as PowerShell instructions are more verbose and detailed than the CLI, and there is no mention of Bash, Linux, or macOS-specific guidance. No Linux-specific tools or shell examples are provided, and the documentation does not clarify that Azure CLI is cross-platform.
Recommendations
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, and is recommended for cross-platform automation.
- Add Bash/Linux/macOS-specific notes or examples where relevant, especially for CLI usage.
- Clarify that PowerShell is available on Linux/macOS, or link to cross-platform PowerShell installation if PowerShell is recommended.
- Balance the detail level between PowerShell and CLI instructions, ensuring Linux/macOS users have equal guidance.
- Consider adding troubleshooting notes for Linux/macOS users if any known issues exist with Azure CLI or PowerShell modules.
Storage
Use blob index tags to manage and find data on Azure Blob Storage
...in/articles/storage/blobs/storage-blob-index-how-to.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure Portal, PowerShell, Azure CLI, and AzCopy. In the Azure CLI sections, it suggests opening a command console such as Windows PowerShell, and file paths in examples use Windows-style paths (e.g., C:\demo-file.txt). PowerShell examples are given equal prominence to Azure CLI, and Windows tools/terms (PowerShell, Windows file paths) are mentioned before or instead of Linux equivalents. There are no explicit Linux/macOS-specific instructions or examples, and the documentation does not mention Bash or Unix-style paths.
Recommendations
- In Azure CLI examples, use platform-agnostic language such as 'open a terminal or command prompt' instead of specifically mentioning 'Windows PowerShell'.
- Provide file path examples using both Windows (C:\demo-file.txt) and Unix-style (/home/user/demo-file.txt) formats, or use a placeholder like <path-to-file>.
- Explicitly state that Azure CLI and AzCopy commands work on Linux/macOS and provide any necessary notes for those platforms.
- Where PowerShell is mentioned, consider also mentioning Bash or shell equivalents for Linux/macOS users, or clarify that PowerShell Core is cross-platform.
- Add a note or section addressing any platform-specific considerations for Linux/macOS users.
Storage
Encrypt and decrypt blobs using Azure Key Vault
...orage/blobs/storage-encrypt-decrypt-blobs-key-vault.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and patterns (Visual Studio, PowerShell, setx for environment variables) are mentioned first or exclusively in several sections. PowerShell examples are provided alongside .NET CLI, but Linux-specific alternatives (such as Bash or Linux-native editors) are less emphasized. The prerequisites and project setup assume Visual Studio on Windows as the primary development environment, with only brief mention of Visual Studio Code. Some steps, such as setting environment variables, do provide Linux commands, but Windows instructions are listed first and in greater detail.
Recommendations
- Provide Linux/macOS examples and instructions alongside Windows ones, ensuring parity in detail and order.
- List cross-platform tools (e.g., Visual Studio Code, JetBrains Rider) before or alongside Windows-only tools like Visual Studio.
- Include Bash examples for package installation and project setup where PowerShell is used.
- Ensure that environment variable instructions for Linux/macOS are as detailed as those for Windows.
- Consider reordering sections so that cross-platform or Linux/macOS instructions are not always listed after Windows ones.