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 876-900 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-index-how-to.md
...in/articles/storage/blobs/storage-blob-index-how-to.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing Windows PowerShell as the default local shell for Azure CLI and PowerShell examples, using Windows file paths (e.g., C:\demo-file.txt), and omitting explicit Linux/macOS shell or file path examples. The instructions for running CLI commands locally mention Windows PowerShell but not Bash or other Unix shells, and there are no Linux-specific notes or parity in examples.
Recommendations
- When referencing local command consoles for Azure CLI, mention Bash (Linux/macOS) alongside Windows PowerShell. For example: 'open a command console such as Bash or Windows PowerShell.'
- Provide file path examples in both Windows (C:\demo-file.txt) and Linux/macOS (/home/user/demo-file.txt) formats for all relevant commands.
- Add explicit notes or examples for running commands in Bash or other Unix shells, especially where quoting or path syntax may differ.
- Avoid defaulting to Windows terminology (e.g., 'Windows PowerShell') when instructions are cross-platform; use neutral terms like 'command prompt' or 'terminal.'
- Where possible, include screenshots or references to Linux/macOS environments in addition to Windows.
- Audit for other subtle Windows-centric language or assumptions and revise for cross-platform inclusivity.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-pageblob-overview.md
...ticles/storage/blobs/storage-blob-pageblob-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing Windows-specific technologies (e.g., Hyper-V VHD format), linking to Windows documentation, and providing examples and migration guidance that assume a Windows or .NET development environment. There are no Linux-specific examples, tools, or migration patterns mentioned, and the only code samples are in C# using the .NET Storage Client Library, which is most commonly associated with Windows development.
Recommendations
- Provide equivalent Linux-focused examples, such as using Azure CLI, Python SDK, or REST API with curl.
- Include references to Linux disk formats (e.g., VHDX, raw) and migration scenarios from Linux-based on-premises environments.
- Balance references to Windows tools (like Hyper-V) with Linux virtualization solutions (e.g., KVM, QEMU).
- Add sample scripts and code snippets in languages and tools commonly used on Linux (e.g., Bash, Python, Azure CLI).
- Link to Linux-specific documentation for migration, backup, and restore processes.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-static-website-how-to.md
...es/storage/blobs/storage-blob-static-website-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is featured as a primary method for command-line interaction, with explicit instructions to 'open a Windows PowerShell command window' and examples using Windows-style paths (e.g., C:\temp\index.html). The CLI section references 'Windows PowerShell' as a console option, and there are no explicit Linux/macOS shell examples or mentions of Bash, zsh, or Linux file paths. Linux-specific considerations for file paths, shell environments, or installation methods are missing, and Windows tools and conventions are prioritized or exclusively mentioned.
Recommendations
- In CLI sections, refer to 'a terminal or command prompt' instead of specifically 'Windows PowerShell', and provide examples for both Windows and Linux/macOS shells.
- When giving file path examples, include both Windows (C:\path) and Linux (/home/user/path) formats.
- In PowerShell sections, clarify that PowerShell Core is cross-platform and can be used on Linux/macOS, or provide Bash equivalents where possible.
- Explicitly mention that Azure CLI and AzCopy are cross-platform, and provide installation and usage notes for Linux/macOS users.
- Add notes or tabs for Bash/Linux shell usage alongside PowerShell, especially for upload and configuration commands.
- Avoid language that assumes a Windows environment (e.g., 'Open a Windows PowerShell command window') or supplement with Linux/macOS alternatives.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-static-website-host.md
...cles/storage/blobs/storage-blob-static-website-host.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a bias toward Windows by exclusively using Visual Studio Code and its Azure Storage extension for deployment, without mentioning or providing alternatives for Linux users (such as CLI-based deployment). There are no examples using cross-platform command-line tools like Azure CLI or AzCopy, and the workflow assumes a GUI-based, Windows-centric development environment.
Recommendations
- Add instructions for deploying static website files using the Azure CLI (az storage blob upload-batch), which works on Linux, macOS, and Windows.
- Include examples using AzCopy, a cross-platform tool, for uploading website files.
- Explicitly mention that Visual Studio Code and its Azure Storage extension are available on Linux and macOS, or provide alternative editors and workflows.
- Provide a section or callout for Linux/macOS users, outlining equivalent steps using terminal commands.
- Ensure screenshots and instructions are not specific to Windows UI elements only.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-static-website.md
.../articles/storage/blobs/storage-blob-static-website.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the 'Uploading content' section, Windows-centric tools like Azure PowerShell, Azure Storage Explorer, Visual Studio Code extension, and Channel 9 (a Microsoft video platform) are listed alongside cross-platform tools, but PowerShell is mentioned before Linux-native options. There are no explicit Linux command-line examples or references to Linux-specific tools or workflows. The documentation does not provide parity in example commands or tool recommendations for Linux users.
Recommendations
- Add explicit Linux/Bash command-line examples for common tasks (e.g., using Azure CLI with Bash, uploading files via AzCopy on Linux).
- Ensure that cross-platform tools (e.g., Azure CLI, AzCopy) are listed before Windows-specific tools (e.g., PowerShell, Storage Explorer) to avoid the impression of Windows-first workflows.
- Include references to Linux-native editors (e.g., Vim, nano) or file upload methods (e.g., using curl or wget with SAS tokens) where appropriate.
- Provide example workflows or screenshots from Linux environments (e.g., terminal, file explorer) in addition to or instead of Windows-centric visuals.
- Clarify that all listed tools are cross-platform where applicable, and provide installation instructions for Linux where relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/versioning-enable.md
.../blob/main/articles/storage/blobs/versioning-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is given a dedicated section and detailed examples, and the PowerShell tab precedes the Azure CLI tab in all code example sections. There is no mention of Linux-specific shells, tools, or considerations, and the CLI examples use generic variable syntax but do not clarify cross-platform usage. The documentation assumes familiarity with PowerShell and Windows-centric tools, which may disadvantage Linux users.
Recommendations
- Add explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
- Clarify that Azure CLI commands work cross-platform and provide examples using Bash variable syntax (e.g., $VAR vs. <VAR>).
- Reorder code example tabs to alternate or randomize the order, or explicitly state that the order does not imply preference.
- Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI and SDKs.
- Avoid assuming PowerShell as the default scripting environment; mention alternatives where possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-custom-domain-name.md
...n/articles/storage/blobs/storage-custom-domain-name.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary scripting interface, with explicit PowerShell command examples provided in each procedural section. In tabbed command sections, PowerShell is always listed before Azure CLI. Additionally, the Azure CLI examples are incorrectly labeled as 'Run the following PowerShell command', which may confuse Linux/macOS users. There are no explicit Linux shell or Bash-specific instructions, and no mention of platform differences or considerations for non-Windows environments.
Recommendations
- Correct the labeling of Azure CLI sections to avoid referring to them as 'PowerShell commands'.
- Provide Bash shell examples or clarify that Azure CLI commands can be run in Bash, Cloud Shell, or other cross-platform environments.
- Consider alternating the order of PowerShell and Azure CLI tabs, or defaulting to Azure CLI, which is more cross-platform.
- Explicitly mention that Azure CLI commands are suitable for Linux, macOS, and Windows, and provide any necessary notes for Linux users (e.g., line continuation differences, authentication methods).
- Where PowerShell is referenced, clarify that it is available cross-platform, but also provide Bash or shell alternatives where appropriate.
- Audit for any other Windows-centric terminology or assumptions and ensure parity in instructions for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-java.md
...rticles/storage/blobs/storage-quickstart-blobs-java.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides both Windows (PowerShell/CMD) and Linux (Bash) examples for command-line instructions, but there are several instances where Windows-specific tools or patterns are mentioned first or exclusively. For example, PowerShell is listed before Bash, and Windows environment variable setup (setx) is described before Linux (export). Output paths and examples sometimes use Windows-style paths (e.g., C:\QuickStarts\blob-quickstart). Additionally, Azure PowerShell is given as a sign-in option alongside Azure CLI and VS Code, but Linux-native tools are not prioritized. There is a subtle preference for Windows-first presentation and tooling.
Recommendations
- Alternate the order of Windows and Linux examples so that neither is always presented first.
- Use platform-neutral language and file paths in output examples (e.g., use $HOME or ~/ instead of C:\ or ./).
- When listing sign-in options or tools, avoid listing Windows-specific tools (like PowerShell) before cross-platform ones (like Azure CLI or Bash).
- Ensure all instructions and code snippets are equally detailed for both Windows and Linux, and avoid assuming the user is on Windows.
- Where possible, provide a single, cross-platform command (e.g., Maven commands) without splitting into PowerShell/Bash unless there are real differences.
- Review screenshots and output logs to ensure they do not reinforce Windows as the default environment.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-create-geo-redundant-storage.md
.../storage/blobs/storage-create-geo-redundant-storage.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All concrete examples, tooling, and instructions are provided exclusively for .NET and Visual Studio (a Windows-centric IDE). There are no Linux or cross-platform instructions, nor are there any code samples or setup guidance for JavaScript or Python users. The workflow assumes the use of Visual Studio and Windows key commands, with no mention of alternatives for Linux or macOS users.
Recommendations
- Provide equivalent instructions for Linux and macOS users, including how to set up the development environment (e.g., using VS Code, JetBrains Rider, or command-line tools).
- Include .NET CLI commands for building and running the sample, which work cross-platform (e.g., 'dotnet build', 'dotnet run').
- Offer code samples and step-by-step instructions for JavaScript and Python as soon as possible, or at least provide links to equivalent samples.
- Avoid assuming Visual Studio as the only IDE; mention and support cross-platform editors.
- When referencing keyboard shortcuts or actions (e.g., 'Press F5'), provide alternatives for non-Windows platforms.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-performance-checklist.md
...rticles/storage/blobs/storage-performance-checklist.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-centric tools (e.g., WireShark, NetMon) for network diagnostics, and by not providing explicit Linux or cross-platform equivalents. While the document mentions AzCopy and Azure CLI (which are cross-platform), it does not offer Linux-specific guidance or examples for common tasks, nor does it mention Linux-native diagnostic tools. The order of tool mentions and examples tends to favor Windows or Microsoft-centric solutions, and there is a lack of parity in practical examples for Linux users.
Recommendations
- When mentioning diagnostic tools like WireShark and NetMon, explicitly include Linux-native alternatives such as tcpdump or iftop.
- Provide example commands for both Windows (PowerShell, CMD) and Linux (Bash) when discussing tools like AzCopy or Azure CLI.
- Where .NET configuration is discussed, offer parallel guidance for Java, Python, or other languages commonly used on Linux.
- Ensure that any references to client libraries, tools, or utilities clarify their cross-platform availability and provide installation/use instructions for Linux.
- Consider including a section or callouts specifically addressing performance and scalability considerations unique to Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-dotnet.md
...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio (a Windows-centric IDE) is presented as the first and primary option for project setup and package installation, with detailed step-by-step instructions and screenshots. While the .NET CLI is also documented and mentions Bash, the examples and instructions often reference Windows tools (cmd, PowerShell) before Linux equivalents. Visual Studio Code is mentioned, but only as an alternative. There are no explicit Linux-specific instructions, troubleshooting, or screenshots, and the documentation assumes familiarity with Windows development environments.
Recommendations
- Present .NET CLI instructions before or alongside Visual Studio instructions, emphasizing cross-platform compatibility.
- Include explicit Linux/macOS terminal examples and troubleshooting steps, such as using Bash/zsh and handling file permissions.
- Add screenshots or terminal output from Linux/macOS environments to balance the Visual Studio (Windows) screenshots.
- Mention Linux package managers or installation methods for .NET SDK where appropriate.
- Clarify that all code and commands work identically on Linux/macOS, and highlight any OS-specific differences if they exist.
- Provide guidance for common Linux editors (e.g., Vim, nano) in addition to Visual Studio Code.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-quickstart-blobs-python.md
...icles/storage/blobs/storage-quickstart-blobs-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In authentication instructions, PowerShell is mentioned as a primary console option alongside Bash, and PowerShell-specific sign-in steps are detailed. In environment variable setup, Windows (cmd) instructions are presented before Linux (bash). Visual Studio Code, a Microsoft tool, is emphasized for sign-in and development. While Linux is not omitted, Windows tools and patterns are often mentioned first or in more detail.
Recommendations
- Alternate the order of Windows and Linux instructions throughout the documentation, or present them side-by-side to avoid implying priority.
- Provide equal detail for both PowerShell/Windows and Bash/Linux workflows, including sign-in and environment variable setup.
- Explicitly mention Bash or other Linux shells as primary options, not just as alternatives.
- Include examples and screenshots from both Windows and Linux environments where appropriate.
- Reference cross-platform editors (e.g., VS Code, Vim, nano) equally, or clarify that instructions apply to all platforms.
- Where Azure CLI is used, clarify that it is fully supported on Linux, macOS, and Windows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-encrypt-decrypt-blobs-key-vault.md
...orage/blobs/storage-encrypt-decrypt-blobs-key-vault.md
High 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 (Visual Studio, PowerShell, setx) are mentioned first or exclusively in several sections. PowerShell is given its own tab for package installation and role assignment, and Visual Studio is the only full-featured IDE recommended. While some Linux equivalents are present (e.g., Bash for environment variables, Azure CLI), Linux-specific development environments and workflows are not equally emphasized. Some steps (like setting environment variables) provide more detail for Windows than Linux.
Recommendations
- Provide Linux-first or at least parallel Linux instructions for all steps, especially for environment setup and tooling.
- Include Linux-native development environment recommendations (e.g., JetBrains Rider, VS Code, or command-line editors) alongside Visual Studio.
- Balance PowerShell and Windows command examples with Bash and Linux shell equivalents throughout.
- Ensure all Azure CLI and PowerShell instructions are mirrored with clear Bash/Linux shell examples where applicable.
- Clarify that the tutorial is cross-platform and highlight any OS-specific caveats or differences.
- Add troubleshooting notes for common Linux/macOS issues (e.g., environment variable persistence, .NET SDK installation).
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2.md
...les/storage/blobs/upgrade-to-data-lake-storage-gen2.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-specific tools and patterns (such as 'PowerShell commands' and the 'Windows Azure Storage Blob driver') before or more prominently than their cross-platform or Linux equivalents. There is a lack of explicit Linux or bash/Unix shell examples, and the documentation does not mention Linux-native tools or workflows, even though Azure CLI and SDKs are cross-platform. The use of 'PowerShell commands' and 'Windows Azure Storage Blob driver' without parallel Linux/bash guidance or examples may alienate Linux users.
Recommendations
- Provide explicit Linux/bash command-line examples alongside or before PowerShell examples, especially for common tasks such as interacting with Data Lake Storage.
- Reference cross-platform tools (e.g., Azure CLI, AzCopy) with both Windows and Linux usage patterns, and clarify their availability on all major operating systems.
- Mention the Hadoop ABFS driver as the modern, cross-platform alternative to WASB, and clarify that it is not Windows-specific.
- Where documentation links to PowerShell-specific guides, also link to equivalent Azure CLI or SDK documentation for Linux/macOS users.
- Avoid using 'Windows Azure Storage Blob driver' as the primary terminology; instead, use 'WASB driver' and clarify its history and cross-platform support.
- Add a section or callout for Linux/macOS administrators, summarizing relevant tools, commands, and considerations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/authorization-resource-provider.md
...cles/storage/common/authorization-resource-provider.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Azure classic CLI) before or instead of cross-platform or Linux-native alternatives. There are no explicit Linux or Bash examples, and the code sample section omits command-line examples entirely. The mention of PowerShell and the Azure classic CLI (which is deprecated and Windows-focused) without equal emphasis on the cross-platform Azure CLI or Bash scripting further reinforces the bias.
Recommendations
- Explicitly mention and provide examples using the cross-platform Azure CLI (az), especially for role assignment and management tasks.
- List Azure CLI and Bash scripting options before or alongside PowerShell and Windows-specific tools.
- Add Linux/Bash command-line examples for common management operations, such as assigning roles or managing storage accounts.
- Avoid referencing deprecated or Windows-only tools like the Azure classic CLI; focus on supported, cross-platform tools.
- Ensure that all code samples and walkthroughs are available for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/account-encryption-key-create.md
...ticles/storage/common/account-encryption-key-create.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure portal, PowerShell, Azure CLI, and ARM templates. PowerShell is given a dedicated section and is listed before Azure CLI, which may indicate a Windows-first and PowerShell-heavy bias. PowerShell is a Windows-centric tool, and its prominence (including detailed instructions and examples) suggests a preference for Windows tooling. There are no explicit Linux-only examples or mentions of Linux-specific tools or shell environments (e.g., Bash), and the Azure CLI examples are generic without shell context. No Linux-specific guidance or parity notes are present.
Recommendations
- Reorder the command-line sections to present Azure CLI before PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell contexts (e.g., Bash).
- Add Bash shell examples or notes for Linux users, especially for multi-line commands (e.g., using \ for line continuation).
- Consider including a table or section summarizing cross-platform compatibility for each tool.
- If possible, provide links or references to Linux-specific installation or troubleshooting guides for Azure CLI.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/use-azurite-to-run-automated-tests.md
...es/storage/blobs/use-azurite-to-run-automated-tests.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific paths and patterns first (e.g., 'mkdir c:\azurite', 'azurite --location c:\azurite'), and does not provide equivalent Linux/macOS examples for directory creation or Azurite launch commands. The use of backslashes in paths and lack of explicit Linux instructions may confuse non-Windows users. Azure Storage Explorer, a GUI tool, is also emphasized without mention of CLI alternatives that may be preferred on Linux.
Recommendations
- Provide both Windows and Linux/macOS command examples side by side, especially for file paths and directory creation (e.g., 'mkdir ~/azurite' and '--location ~/azurite').
- Use platform-agnostic variables or explain path differences (e.g., use $HOME/azurite for Linux/macOS).
- Mention CLI alternatives to Azure Storage Explorer, such as Azure CLI or azcopy, for users who may not want to use a GUI tool.
- Explicitly state which commands are platform-specific and provide guidance for users on other operating systems.
- In the npm/Docker installation steps, clarify any OS-specific prerequisites or differences.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
...rage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell and Windows-specific instructions, referencing Windows PowerShell explicitly, and omitting Linux/macOS-specific guidance or examples. The Azure CLI section suggests using Windows PowerShell as a console, and there is no mention of Bash or Linux-native shells. No Linux/macOS-specific troubleshooting or command-line nuances are discussed.
Recommendations
- In the PowerShell section, clarify that Azure PowerShell is cross-platform and provide instructions for using it on Linux/macOS (e.g., via pwsh).
- Instruct users in the Azure CLI section to use Bash or their native shell on Linux/macOS, not just Windows PowerShell.
- Add explicit Linux/macOS examples or notes for command-line steps, including installation and environment differences.
- Avoid language like 'Open a Windows PowerShell command window'; instead, use 'Open a PowerShell terminal' and specify cross-platform compatibility.
- Where screenshots or UI elements are shown, note any OS-specific differences if relevant.
- Ensure that any references to scripting or automation mention Bash and other common Linux scripting environments alongside PowerShell.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/sas-expiration-policy.md
.../main/articles/storage/common/sas-expiration-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as a primary scripting example, and the PowerShell section appears before the Azure CLI section, which is more cross-platform. There are no explicit Linux shell or Bash examples, and no mention of Linux-specific considerations or tools. The CLI section is present, but the documentation does not clarify that PowerShell is Windows-centric or that Azure CLI is recommended for Linux/macOS users.
Recommendations
- Add explicit Bash/shell examples for configuring SAS expiration policies using Azure CLI, and clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Reorder the example sections so that Azure CLI (cross-platform) appears before PowerShell (Windows-centric), or at least clarify the platform applicability of each.
- Include a note in the PowerShell section indicating it is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Where screenshots or UI steps are shown, add clarifications if there are any differences in experience for Linux/macOS users (for example, in Azure Cloud Shell).
- Consider including a table summarizing which tools are available on which platforms, to help users choose the best option for their environment.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/classic-account-migrate.md
...ain/articles/storage/common/classic-account-migrate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page exhibits a strong bias toward Windows and PowerShell usage. All command-line examples are provided exclusively using PowerShell, with no Azure CLI, Bash, or Linux-native instructions. The PowerShell approach is described in detail, including installation steps and module management, while Linux or cross-platform alternatives are not mentioned. The structure consistently presents the Azure Portal and PowerShell as the only options, omitting Azure CLI or Bash scripting, which are more common on Linux and macOS. This can hinder Linux users or those preferring cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including listing, deleting, and migrating storage accounts.
- Provide Bash shell snippets where appropriate, especially for users on Linux or macOS.
- Mention Azure CLI as an equal alternative to PowerShell in all relevant sections, not just as a post-migration management tool.
- Include installation and usage instructions for Azure CLI alongside PowerShell module instructions.
- Reorder sections or provide tabs so that Azure CLI and PowerShell are presented with equal prominence.
- Explicitly state that all steps can be performed on Linux, macOS, and Windows, and clarify any OS-specific requirements.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/customer-managed-keys-configure-cross-tenant-new-account.md
...stomer-managed-keys-configure-cross-tenant-new-account.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as a primary scripting example, and the PowerShell section precedes the Azure CLI section. There are no explicit Linux shell or Bash examples, and the CLI example, while cross-platform, is presented after PowerShell. The documentation references Windows-centric tools (PowerShell) and patterns, which may make Linux users feel secondary.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific variable syntax where appropriate.
- Add Bash shell script examples or notes for Linux users, especially for environment variable usage and command chaining.
- Clarify that PowerShell is available cross-platform, but also provide guidance for users who may not have PowerShell installed.
- Balance the order and prominence of examples so that Linux and Windows users are equally supported.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/manage-storage-analytics-logs.md
...ticles/storage/common/manage-storage-analytics-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell instructions (which are Windows-centric), referencing 'Open a Windows PowerShell command window', and using Windows-style file paths (e.g., 'C:\Logs\Storage') in examples. There are no equivalent CLI or Bash/Linux shell examples, nor are cross-platform tools like Azure CLI or Bash scripts presented alongside PowerShell. The documentation also refers to tools and workflows (like PowerShell and Windows file paths) that are specific to Windows environments, without mentioning or providing parity for Linux or macOS users.
Recommendations
- Add Azure CLI examples for all operations currently shown only in PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Replace or supplement Windows file paths (e.g., 'C:\Logs\Storage') with POSIX-style paths (e.g., '/home/user/Logs/Storage') or note both formats.
- Explicitly mention that PowerShell Core is cross-platform, and provide guidance for running scripts on Linux/macOS if PowerShell is retained.
- Include Bash or shell script examples where appropriate, especially for automation tasks.
- Ensure that references to 'open a Windows PowerShell command window' are generalized to 'open a terminal' or provide OS-specific instructions.
- Highlight cross-platform tools (like AzCopy and Azure Storage Explorer) and provide usage notes for Linux/macOS where relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-explorers.md
...blob/main/articles/storage/common/storage-explorers.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page lists Microsoft client tools for Azure Storage, but it demonstrates a Windows bias by listing a Windows-only tool (Visual Studio Cloud Explorer) without Linux or macOS equivalents, and by not providing Linux-specific examples or highlighting cross-platform parity. The order of presentation also places Windows-centric tools before cross-platform options.
Recommendations
- Include Linux/macOS equivalents or alternatives for Windows-only tools, or explicitly state when a tool is Windows-only.
- Provide more examples or discussion of Linux-compatible tools, such as command-line utilities (e.g., Azure CLI, AzCopy) that work across platforms.
- Reorder the table or discussion to highlight cross-platform tools (such as Azure Storage Explorer) before Windows-only tools.
- Add a section or table column clarifying platform limitations and suggesting alternatives for non-Windows users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-upgrade.md
...ain/articles/storage/common/storage-account-upgrade.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell as a primary upgrade method, listing it before Azure CLI, and providing detailed PowerShell instructions. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux or macOS users. While Azure CLI is included, there are no explicit Linux/macOS-specific instructions or examples, and the CLI installation link is generic. No Linux shell (bash) examples or references to Linux-native tools are present.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Add explicit Linux/macOS installation notes or links for Azure CLI, and clarify that PowerShell Core is available cross-platform if relevant.
- Include bash/zsh shell command examples for common Linux environments, especially for scripting or automation.
- Avoid implying PowerShell is the default or preferred method; instead, emphasize cross-platform tools like Azure CLI.
- Where possible, mention that all operations can be performed from Linux/macOS as well as Windows, and provide troubleshooting tips for non-Windows environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-analytics-logging.md
...n/articles/storage/common/storage-analytics-logging.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell code examples for interacting with Storage Analytics logs, referencing Windows-specific tools (such as Microsoft Azure Storage Explorer with 'win32' and 'Windows_NT' user agents in log samples), and omitting equivalent Linux/Unix shell or CLI examples. Additionally, PowerShell is mentioned before Azure CLI when describing how to enable logging, and there is no demonstration of using Linux-native tools or cross-platform scripting.
Recommendations
- Provide equivalent Azure CLI examples (with Bash syntax) alongside or before PowerShell snippets for all operations, especially for listing and filtering blobs.
- Include sample log entries generated from Linux or macOS clients (e.g., with user agents showing 'linux' or 'darwin'), or clarify that the logs are platform-agnostic.
- Reference cross-platform tools (such as AzCopy, Azure CLI, or REST API) equally or before Windows-specific tools.
- Explicitly state that all operations can be performed from Linux, macOS, or Windows, and provide links or examples for each.
- Where PowerShell is used, add a corresponding Bash or shell script example to ensure Linux users are not excluded.