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 901-925 of 1657 flagged pages
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-choose-data-transfer-solution.md
...torage/common/storage-choose-data-transfer-solution.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Scripted/programmatic transfer options list Azure PowerShell before Azure CLI, and the 'Next steps' section links to a PowerShell quickstart before the equivalent Azure CLI quickstart. There are no explicit Linux- or Unix-specific examples or mentions, and the scripting focus leans toward Windows-native tooling (PowerShell) rather than cross-platform-first approaches. No Linux command-line or shell examples are provided, and there is no mention of Linux-specific tools or patterns.
Recommendations
- List Azure CLI examples and quickstarts before or alongside PowerShell to emphasize cross-platform parity.
- Include explicit Linux/macOS command-line examples (e.g., bash scripts using AzCopy or Azure CLI).
- Add references to Linux/Unix tools or workflows where appropriate, such as rsync or shell scripting for data transfer.
- Clarify that AzCopy and Azure CLI are cross-platform and provide installation/use instructions for Linux/macOS.
- Balance the order of scripting tool mentions (PowerShell and CLI) to avoid implying Windows is the default or preferred environment.
Create Pull Request
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-encryption-key-model-get.md
...les/storage/common/storage-encryption-key-model-get.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation presents three methods: Azure Portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given a dedicated section before Azure CLI, and no explicit Linux shell or Bash example is provided. The CLI example is generic, but the lack of explicit Bash/Linux context or mention of Linux tools may disadvantage Linux users. There is also no mention of cross-platform scripting considerations.
Recommendations
- Add explicit Bash/Linux shell examples alongside or before PowerShell, especially for the Azure CLI section.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide example outputs or notes for each platform.
- Consider reordering the sections to present the Azure CLI method before PowerShell, as CLI is cross-platform.
- Include a note or section on using the Azure CLI in Bash or other common Linux shells.
- If PowerShell is included, mention that PowerShell Core is available cross-platform, or provide equivalent Bash commands where possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-migration-overview.md
.../articles/storage/common/storage-migration-overview.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 prioritizing Windows-native tools (robocopy, xcopy, Azure File Sync) and migration scenarios from Windows file servers. Powershell/Windows tools are mentioned before Linux equivalents, and Linux-specific tools or workflows are underrepresented or missing. There are no explicit Linux/NFS migration examples or Linux-native tool recommendations, despite mentioning rsync in passing.
Recommendations
- Provide balanced examples for both Windows and Linux environments, including explicit Linux/NFS migration scenarios.
- List Linux-native tools (e.g., rsync, scp, tar, lftp) alongside Windows tools, and give equal detail and prominence.
- Include guidance for migrating from Linux file servers (e.g., NFS exports) to Azure Files or Blob Storage.
- Mention and link to Linux-specific Azure migration agents or scripts, if available.
- Avoid recommending Windows tools (robocopy, xcopy, Azure File Sync) as defaults; instead, present options for both OSes in parallel.
- Add sample command lines or scripts for both Windows and Linux migration workflows.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-ref-azcopy-configuration-settings.md
...ge/common/storage-ref-azcopy-configuration-settings.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 listing Windows and PowerShell commands before Linux/macOS equivalents, providing more detailed proxy bypass instructions for Windows (with no Linux/macOS equivalents), and referencing Windows-specific behaviors (e.g., automatic proxy detection, Windows Event Logger, and Syslog). Some environment variable descriptions are tailored to Windows, and Linux-specific guidance is minimal or absent.
Recommendations
- Present Linux/macOS and Windows command examples in parallel, or alternate the order to avoid always listing Windows first.
- Provide equally detailed instructions for Linux/macOS users, especially for proxy bypass scenarios (e.g., how to explicitly disable proxy on Linux/macOS).
- Clarify platform-specific behaviors for all OSes, not just Windows (e.g., explain logging destinations on Linux/macOS as well as Windows).
- Avoid referencing Windows-specific tools or behaviors without mentioning Linux/macOS equivalents (e.g., mention Syslog and Event Logger together, or explain alternatives).
- Where environment variable effects differ by OS, clearly state the behavior for each supported platform.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-account-create.md
...main/articles/storage/common/storage-account-create.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is consistently presented as a primary automation method alongside Azure CLI, and instructions for deploying Bicep and ARM templates often default to PowerShell examples before CLI. The use of PowerShell-specific terminology and commands (e.g., 'Install-Module', 'New-AzResourceGroup', 'Remove-AzStorageAccount') is prevalent, and the documentation refers to the Azure PowerShell module as a standard tool. While Azure CLI (which is cross-platform) is well represented, there is little explicit mention of Linux or macOS environments, and no examples using native Linux shell scripting or tools outside of Azure CLI. The documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Explicitly mention Linux and macOS compatibility for Azure CLI and Azure Developer CLI, and provide guidance for users on those platforms.
- When presenting PowerShell and CLI examples, alternate the order or clarify that both are equally supported, rather than defaulting to PowerShell first.
- Where PowerShell is referenced for deploying Bicep or ARM templates, provide Bash shell equivalents (using az CLI) as the primary or co-equal example.
- Avoid language that assumes PowerShell is the default automation tool; instead, refer to both PowerShell and Bash/CLI as valid options.
- Add notes or callouts for Linux users regarding prerequisites (e.g., installation of Azure CLI on Linux, use of Bash scripting, etc.).
- Consider including a section or appendix with Linux/Bash-specific tips for automation and troubleshooting.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-sas-overview.md
...b/main/articles/storage/common/storage-sas-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Get started with SAS' section, PowerShell is listed as the first method for creating a user delegation SAS, and there is no mention of Bash or Linux shell scripting. While Azure CLI is included, it is listed after PowerShell. There are no explicit Linux-specific examples or references to Linux-native tools, and the only command-line examples referenced are PowerShell and Azure CLI, both of which are often associated with Windows environments. There are no explicit examples or guidance for Linux users or for using Bash scripts.
Recommendations
- Add Linux/Bash-specific examples for generating SAS tokens, especially in the 'Get started with SAS' section.
- List Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more commonly used on Linux.
- Include references to Linux-native tools (such as Bash scripting or curl) where appropriate.
- Ensure parity by providing explicit instructions or links for both Windows and Linux users in all example sections.
- Consider adding a short section or note highlighting that all operations can be performed on Linux, and provide links to relevant Linux documentation.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-large-dataset-moderate-high-network.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-large-dataset-moderate-high-network.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools (e.g., Robocopy) for data transfer, omitting Linux equivalents or cross-platform alternatives. The mention of Robocopy as the example tool for copying data to Data Box devices is Windows-centric, with no mention of rsync, cp, or other Linux/Unix tools. Additionally, there are no command-line examples or setup instructions for Linux users, and the ordering of tools (e.g., AzCopy, Azure PowerShell) tends to prioritize Windows-native or Windows-friendly options.
Recommendations
- When mentioning Robocopy for Data Box transfers, also mention Linux/Unix equivalents such as rsync or cp, and provide example commands.
- Explicitly state that AzCopy, Azure CLI, and REST APIs are cross-platform, and provide example usage for both Windows and Linux environments.
- Avoid listing Windows tools or patterns first unless they are the only supported option; otherwise, present cross-platform tools first or in parallel.
- Include a section or table row for Linux/macOS compatibility and recommended tools for each transfer method.
- Where PowerShell is mentioned, also mention Bash or shell scripting alternatives for Linux users.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page lists Azure PowerShell as a primary scripting/programmatic tool for data transfer, which is traditionally Windows-centric, and mentions it before Azure CLI (which is more cross-platform). There are no explicit Linux shell or bash script examples, nor are Linux-native tools or patterns discussed. While AzCopy and Azure CLI are cross-platform, the lack of Linux-specific guidance or examples, and the prioritization of PowerShell, indicate a mild Windows bias.
Recommendations
- Include explicit Linux/bash shell examples for scripting data transfers, such as AzCopy and Azure CLI commands in bash.
- Mention Azure CLI before or alongside PowerShell to emphasize cross-platform parity.
- Clarify that Azure PowerShell is available on Linux and macOS (if true), or otherwise recommend Azure CLI for Linux users.
- Add a section or examples specifically for Linux users, highlighting common workflows and tools.
- If possible, provide sample scripts for both PowerShell and bash to demonstrate parity.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-azure-active-directory.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-authorize-azure-active-directory.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation generally uses cross-platform (bash) examples for environment variable setting and AzCopy usage, which is good for Linux parity. However, there are several areas of Windows bias: (1) PowerShell is used exclusively for secure variable entry (e.g., prompting for secrets), with no Linux shell equivalent shown; (2) Windows tools and patterns are referenced, such as exporting certificates from the Windows certificate store and referencing the Export-PfxCertificate PowerShell cmdlet, with no Linux alternatives or guidance; (3) When discussing certificate handling, the documentation assumes a Windows-centric workflow (certificate store, PFX export), and Linux users are not given parallel instructions. These biases may make the documentation less approachable for Linux users.
Recommendations
- For every PowerShell example (such as using Read-Host to securely prompt for secrets), provide an equivalent Linux shell example (e.g., using 'read -s' in bash).
- When referencing Windows certificate store and Export-PfxCertificate, also provide instructions for exporting certificates on Linux (e.g., using openssl to convert/export certificates).
- Explicitly mention Linux and macOS workflows wherever Windows-specific tools or patterns are discussed, ensuring parity in guidance.
- Where screenshots or UI instructions are given (such as Azure portal steps), clarify that these are OS-agnostic or provide notes if any steps differ by OS.
- Consider adding a short section or callout at the top clarifying that all AzCopy commands are cross-platform, and note any OS-specific caveats.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-rest-api-auth.md
.../main/articles/storage/common/storage-rest-api-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by focusing exclusively on C# code intended for use with Visual Studio (a Windows-centric IDE), referencing only Windows tools like Fiddler for network inspection, and omitting any Linux-specific instructions, tools, or code examples. There are no alternative examples for Linux environments, nor are cross-platform development environments or tools mentioned.
Recommendations
- Provide equivalent code samples in a cross-platform language (e.g., Python, JavaScript) and show how to run them on Linux.
- Include instructions for setting up the development environment on Linux (e.g., using VS Code, Mono, or .NET Core CLI).
- Mention and provide examples for Linux-compatible network inspection tools (e.g., tcpdump, Wireshark, mitmproxy) alongside Fiddler.
- Explicitly state that the REST API can be called from any OS and provide at least one non-Windows workflow.
- Add notes or sections for Linux/macOS users, including any differences in environment setup or execution.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-migrate-on-premises-data.md
.../common/storage-use-azcopy-migrate-on-premises-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently mentioning Windows tools and workflows first (such as Schtasks), providing more detailed explanations for Windows commands, and referencing Windows command-line environments (cmd/PowerShell) more prominently. While Linux equivalents (cron, crontab) are included, they are often mentioned after the Windows approach or with less detail.
Recommendations
- Alternate the order of Windows and Linux instructions throughout the document to avoid always listing Windows first.
- Provide equally detailed explanations and context for Linux commands (e.g., crontab) as are given for Windows tools (e.g., Schtasks).
- Include explicit PowerShell and Bash script examples side-by-side where relevant, rather than focusing on Windows batch files.
- Ensure that screenshots, sample paths, and command-line prompts are balanced between Windows and Linux environments.
- Where possible, use neutral language that does not assume the user is on Windows (e.g., 'Open a terminal or command prompt' instead of just 'Open a command prompt').
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-configure.md
...rticles/storage/common/storage-use-azcopy-configure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows examples (including PowerShell and Command Prompt) are consistently listed before Linux/macOS equivalents, and Windows-specific environment variable syntax is given precedence. The PowerShell example is presented before the Linux grep example. There is also a focus on Windows-specific directory variables and quoting conventions, with Linux/macOS guidance following or being less detailed.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples, rather than always listing Windows first.
- When showing command examples, alternate the order or provide a combined table for parity.
- Provide equal detail for Linux/macOS shell conventions (e.g., quoting, environment variables) as is given for Windows/PowerShell.
- Use neutral phrasing such as 'On Windows, use... On Linux/macOS, use...' instead of always leading with Windows.
- Consider including Bash shell examples as the default, with PowerShell/Windows Command Prompt as alternatives.
- Ensure that all platform-specific instructions are equally detailed and easy to follow.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-optimize.md
...articles/storage/common/storage-use-azcopy-optimize.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing Windows command syntax first in environment variable examples, providing specific guidance for Windows Command Shell quoting before mentioning other shells, and referencing Windows-specific command patterns. While Linux and macOS equivalents are included, Windows is consistently prioritized in order and detail.
Recommendations
- Present Linux and Windows command examples side-by-side or in parallel order, alternating which OS is listed first.
- Provide explicit Linux shell (bash/zsh) and macOS examples with equal prominence to Windows examples.
- When discussing shell quoting, mention Linux/macOS conventions first or together with Windows, rather than treating Windows as the default.
- Include a dedicated section or callout for Linux/macOS-specific performance tuning tips, not just a brief mention (e.g., concurrent local scanning).
- Ensure all environment variable and command-line examples are shown for both Windows (cmd.exe and optionally PowerShell) and Linux/macOS, with clear context.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-batch-create-sample.md
...storage/elastic-san/elastic-san-batch-create-sample.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides a PowerShell script example for batch creation of Azure Elastic SAN volumes, assumes use of Windows file paths, and does not mention or provide equivalent instructions for Linux or cross-platform environments. There is no reference to Bash, Azure CLI, or Linux-compatible scripting, nor guidance for non-Windows users.
Recommendations
- Provide a Bash or Azure CLI example for batch creation of Elastic SAN volumes using a CSV file, suitable for Linux and macOS users.
- Use cross-platform file path examples (e.g., /home/user/ElasticSan/TestCsv3.csv) or clarify that the file path should be adapted for the user's OS.
- Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, or provide guidance for installing PowerShell on those platforms.
- Add a section comparing approaches for Windows and Linux, or at least acknowledge Linux users and direct them to equivalent tooling.
- Avoid assuming Windows as the default environment; use neutral language and examples where possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-emulator.md
...b/main/articles/storage/common/storage-use-emulator.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows, as the Azure Storage Emulator itself is a Windows-only tool. All setup, usage, and authentication instructions are Windows-centric, including references to Windows UI elements, Windows authentication, and tools like SQL Server Management Studio. Command-line examples and authentication flows are provided only for Windows (including PowerShell), with no Linux or cross-platform alternatives. While Azurite is mentioned as the recommended cross-platform replacement, no practical guidance or parity examples for Linux users are provided within this page.
Recommendations
- Add a clear, prominent section at the top directing Linux and macOS users to Azurite, including a summary of installation and usage steps.
- Provide equivalent command-line examples for Azurite (npm install, run commands) alongside or instead of Storage Emulator instructions.
- Include authentication and connection string examples for Azurite, and show how to generate SAS tokens using cross-platform tools (e.g., Azure CLI, SDKs) rather than only PowerShell.
- Minimize references to Windows-specific UI elements (Start menu, taskbar, Windows authentication) or provide cross-platform alternatives where possible.
- Where Storage Explorer is mentioned, clarify its cross-platform availability and provide usage notes for Linux/macOS.
- Consider splitting the documentation into Windows (Storage Emulator) and cross-platform (Azurite) guides, or at least provide side-by-side instructions.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-client-version.md
...n/transport-layer-security-configure-client-version.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell and .NET examples, both of which are primarily Windows-centric. There are no Linux or cross-platform command-line examples (such as Bash, curl, or Python). Additionally, the verification step recommends Fiddler, a Windows-only tool, without mentioning Linux alternatives. The order of examples and tool recommendations further reinforce a Windows-first perspective.
Recommendations
- Add examples for configuring TLS in common Linux environments, such as using curl, Python, or Java.
- Include Bash or shell script examples for setting environment variables or configuring TLS settings.
- Mention and provide instructions for cross-platform or Linux-native network traffic tools (e.g., tcpdump, Wireshark, or OpenSSL s_client) for verifying TLS versions.
- Ensure that .NET examples clarify cross-platform applicability (e.g., .NET Core/5+/6+ on Linux/macOS).
- Present examples in a platform-neutral order or group them by platform, rather than defaulting to Windows/PowerShell first.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-migrate-to-TLS2.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-migrate-to-TLS2.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows operating systems, tools, and frameworks (e.g., .NET Framework, Visual Studio, PowerShell) and providing tips and next steps that are almost exclusively relevant to Windows environments. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or configuration steps mentioned. The guidance assumes a Windows-centric development and deployment context.
Recommendations
- Add explicit guidance for Linux and macOS users, including how to check and enforce TLS 1.2 support on those platforms.
- Include examples using common Linux tools (e.g., OpenSSL, curl, wget) to verify TLS versions and connectivity.
- Mention how to configure TLS settings for popular Linux development frameworks (e.g., Python, Java, Node.js) and package managers.
- Reference cross-platform editors and tools (e.g., VS Code) alongside Windows-only tools like Visual Studio.
- Provide parity in quick tips, such as noting which Linux distributions and versions have TLS 1.2 enabled by default.
- Include troubleshooting steps and links for Linux environments, not just PowerShell and WinHTTP.
- Balance the order of presentation so that Windows and Linux guidance are given equal prominence, or group them by platform.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azcopy-v10.md
...main/articles/storage/common/storage-use-azcopy-v10.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux installation instructions and download links, but there is a noticeable Windows bias in several areas. Windows/PowerShell examples are often given first or in more detail, and some scripting and usage notes focus on Windows-specific tools or patterns. The main example command for copying data uses a Windows path, and batch file/SAS token escaping is discussed only for Windows. Linux scripting examples are present but less emphasized in some sections.
Recommendations
- Alternate the order of Windows and Linux examples or present them side-by-side to avoid always listing Windows first.
- Provide Linux shell (bash) equivalents for all scripting and usage examples, especially where only PowerShell or Windows batch examples are given (e.g., escaping SAS tokens in bash scripts).
- Use platform-neutral paths (e.g., /local/path or <local-path>) in generic AzCopy command examples, or provide both Windows and Linux path examples.
- When discussing adding AzCopy to the system path, include explicit Linux/macOS instructions (e.g., modifying ~/.bashrc or ~/.profile).
- Where batch file or PowerShell-specific advice is given, add corresponding notes for bash or other common Linux scripting environments.
- Ensure that troubleshooting and optimization sections reference both Windows and Linux tools/utilities where relevant.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.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 prioritizing Windows-specific tools and workflows. PowerShell is featured as a primary scripting example before the cross-platform Azure CLI. There are references to the Windows implementation of SSL, and the use of Azure PowerShell is highlighted without mention of Linux-native alternatives or shell scripting. No explicit Linux or Bash examples are provided, and the documentation does not address Linux-specific considerations or tools for managing TLS settings.
Recommendations
- Provide Bash or shell script examples alongside PowerShell, especially for common Linux scenarios.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Avoid language that implies Windows is the default or primary platform (e.g., referencing the Windows SSL stack without noting Linux/OpenSSL context).
- Include troubleshooting or configuration notes relevant to Linux environments, such as OpenSSL versions or common Linux distributions.
- Where screenshots or UI steps are shown, clarify if there are differences for Linux users (e.g., Azure CLI installation or usage).
- If referencing PowerShell, note that PowerShell Core is available cross-platform, and provide guidance for installing or using it on Linux.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-use-azurite.md
...ob/main/articles/storage/common/storage-use-azurite.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by prioritizing Windows-centric tools (Visual Studio, .exe paths), using Windows file paths (c:\azurite), and providing command-line examples and instructions that assume a Windows environment. Linux and macOS equivalents for file paths, environment variable setting, and directory mounting in Docker are either omitted or only mentioned as secondary notes. There are no explicit Linux/macOS command-line examples for running Azurite, and the Visual Studio integration is only described for Windows.
Recommendations
- Provide parallel Linux/macOS examples for all command-line instructions, including npm, GitHub, and Docker usage (e.g., use /home/user/azurite or ~/azurite instead of c:\azurite).
- When showing environment variable commands, always show both Windows (set) and Unix (export) forms side-by-side.
- Include Visual Studio Code and CLI workflows that are platform-agnostic or explicitly describe differences for Linux/macOS users.
- For Docker volume mounts, show both Windows (c:/azurite:/data) and Linux (-v ~/azurite:/data) syntax.
- In sections referencing executable locations (e.g., azurite.exe), clarify that this is Windows-specific and provide guidance for Linux/macOS users (e.g., running azurite from npm global install).
- Avoid using Windows paths as the only example; always provide Unix-style path alternatives.
- Add a summary table or section explicitly outlining platform-specific differences and setup steps.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/elastic-san/elastic-san-best-practices.md
...cles/storage/elastic-san/elastic-san-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides both Windows and Linux guidance, but there is a noticeable Windows-first bias. Windows tools and workflows (PowerShell, Registry Editor, iSCSI Initiator app) are mentioned first or in more detail, and Windows-specific screenshots and references are more prominent. Linux instructions are present but sometimes less detailed or appear after Windows equivalents.
Recommendations
- Alternate the order of Windows and Linux sections/examples to avoid always presenting Windows first.
- Provide equal detail and clarity for Linux instructions, including screenshots and references to common Linux tools (e.g., GNOME Disks, system utilities) where applicable.
- Include links to Linux-specific documentation or man pages, similar to the PowerShell/Windows references.
- Where possible, use platform-neutral language and structure, grouping platform-specific instructions under clear subheadings.
- Ensure parity in troubleshooting and advanced configuration guidance for both Windows and Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-choose-cloud-tiering-policies.md
...e/file-sync/file-sync-choose-cloud-tiering-policies.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows Server, NTFS, File Server Resource Manager (FSRM), and Windows-specific tools like Robocopy. There are no examples or guidance for Linux or cross-platform scenarios, and all technical explanations assume a Windows file system and management context.
Recommendations
- Clearly state early in the article that Azure File Sync is a Windows-only solution, if that is the case. If not, add explicit guidance for Linux or cross-platform users.
- If any Linux support exists (e.g., via SMB or other means), provide equivalent instructions, examples, and caveats for Linux file systems and tools.
- Where Windows-specific tools or concepts are mentioned (e.g., NTFS, FSRM, Robocopy), note their Linux equivalents or clarify that these instructions do not apply to Linux.
- Add a section or callout that addresses the lack of Linux support, and direct users to alternative solutions if they are on non-Windows platforms.
- Ensure that any tables or technical details about file systems or cluster sizes mention whether they are relevant only to NTFS/Windows or if there are parallels in Linux environments.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-replace-drive.md
.../articles/storage/file-sync/file-sync-replace-drive.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions assume the use of Windows Server, Windows command line, and Windows-native tools such as Robocopy. There are no Linux equivalents, nor is there any mention of performing these steps on a Linux server or using cross-platform tools. The documentation presumes the reader is operating in a Windows-only ecosystem.
Recommendations
- Add explicit statements about Azure File Sync's compatibility (or lack thereof) with Linux servers. If unsupported, clarify this early in the documentation.
- If Linux is supported, provide parallel instructions for Linux environments, including equivalent commands (e.g., using rsync or cp for file copying) and service management.
- Mention cross-platform tools where possible, or at least acknowledge alternatives for non-Windows environments.
- Avoid assuming the use of Windows-only utilities (like Robocopy) without offering alternatives or explanations for users on other platforms.
- If only Windows is supported, clearly state this at the beginning to set user expectations.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-cloud-tiering-policy.md
...es/storage/file-sync/file-sync-cloud-tiering-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the PowerShell cmdlet `Invoke-StorageSyncFileRecall` as the only method for recalling files, without mentioning any Linux equivalents or cross-platform alternatives. There are no examples or instructions for configuring or managing Azure File Sync cloud tiering from Linux systems, nor is there any discussion of Linux tools or command-line patterns.
Recommendations
- Provide equivalent Linux command-line instructions or tools for managing Azure File Sync cloud tiering, if available.
- If Azure File Sync is only supported on Windows, clearly state this limitation early in the documentation.
- Where PowerShell cmdlets are referenced, mention whether they are available on PowerShell Core (cross-platform) or only on Windows PowerShell.
- Include a note or section addressing Linux/Unix users, clarifying support status and offering guidance or alternatives if possible.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/file-sync/file-sync-server-endpoint-delete.md
.../storage/file-sync/file-sync-server-endpoint-delete.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All operational steps reference Windows-specific tools (Task Scheduler, Event Viewer), PowerShell cmdlets/scripts, and Windows file paths. There are no examples or guidance for performing these tasks on Linux or other platforms, nor is there any mention of Linux support or alternatives.
Recommendations
- Explicitly state whether Azure File Sync server endpoints are supported on Linux. If not, clarify this early in the documentation.
- If Linux support exists or is planned, provide equivalent instructions and examples for Linux environments, including CLI commands, log file locations, and troubleshooting steps.
- Where possible, use cross-platform Azure CLI or REST API examples instead of (or in addition to) PowerShell.
- Reference Linux-native tools (e.g., cron, systemd, journalctl) where appropriate, or provide guidance for analogous operations.
- Include a section or note addressing platform support and any limitations, so users on non-Windows platforms are aware of their options.