Storage
1359
Total Pages
1162
Linux-Friendly Pages
197
Pages with Bias
14.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
392 issues found
Showing 351-375 of 392 flagged pages
Storage
Blob Storage feature support in Azure storage accounts
...e/blobs/storage-feature-support-in-storage-accounts.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation page lists both Azure CLI and PowerShell command support for Blob Storage, but only explicitly mentions PowerShell (a Windows-centric tool) in the feature tables. There is no explicit mention of Linux/macOS equivalents for PowerShell commands, nor are Linux/macOS-specific tools (other than Blobfuse) highlighted. The order of presentation does not favor Windows, but the inclusion of PowerShell as a distinct feature may signal a Windows bias.
Recommendations
- Add explicit references to Linux/macOS command-line tools (such as Bash scripts, azcopy, or REST API usage) alongside PowerShell.
- Clarify that Azure CLI is cross-platform and provide example links for Linux/macOS usage.
- If PowerShell is listed as a feature, consider listing Bash or other Linux-native scripting options for parity.
- Ensure that any referenced quickstart or command documentation includes Linux/macOS instructions and examples.
Create Pull Request
Storage
Quickstart: Azure Blob Storage library - .NET
...icles/storage/blobs/storage-quickstart-blobs-dotnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Minor Windows Tools
Summary
The documentation provides both Visual Studio (Windows-centric) and .NET CLI instructions, but Visual Studio steps and screenshots are shown first and in more detail. The CLI instructions do mention Bash, but most examples and troubleshooting steps reference Windows tools (cmd, PowerShell) before Linux equivalents. There are no explicit Linux/macOS-only examples or troubleshooting, and Visual Studio is presented as the primary IDE, which is Windows-only.
Recommendations
- Present .NET CLI instructions before Visual Studio steps, or side-by-side, to emphasize cross-platform usage.
- Include explicit Linux/macOS terminal examples (e.g., Bash, zsh) and troubleshooting steps for package installation and permissions.
- Add screenshots or instructions for popular cross-platform editors (e.g., Visual Studio Code) and mention their parity.
- Clarify that all .NET CLI commands work on Linux/macOS and Windows, and highlight any OS-specific caveats.
- Avoid language like 'In a console window (such as cmd, PowerShell, or Bash)'βinstead, use 'terminal (Windows: cmd/PowerShell, Linux/macOS: Bash/zsh)'.
Storage
Static website hosting in Azure Storage
.../articles/storage/blobs/storage-blob-static-website.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation lists Windows-centric tools such as Azure PowerShell and Azure Storage Explorer alongside cross-platform tools, but PowerShell is highlighted as a primary upload method. There is no explicit mention of Linux/macOS-specific CLI patterns or parity, and Windows tools are often listed before Linux-friendly alternatives. No Linux/macOS-specific examples or troubleshooting are provided.
Recommendations
- Add explicit Linux/macOS CLI examples for uploading and managing content (e.g., bash scripts, Linux file paths).
- Clarify that Azure CLI and AzCopy are fully cross-platform and provide usage examples for Linux/macOS.
- Balance tool ordering so that cross-platform tools (Azure CLI, AzCopy) are listed before Windows-specific tools (PowerShell, Storage Explorer).
- Include troubleshooting notes for Linux/macOS users (e.g., file permission issues, case sensitivity).
- Mention Linux-native editors (e.g., VS Code on Linux) and workflows.
Storage
Quickstart: Azure Blob Storage client library for Python
...icles/storage/blobs/storage-quickstart-blobs-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there is mild Windows bias in authentication instructions and environment variable setup. Windows tools (PowerShell, setx) are mentioned before Linux equivalents, and PowerShell is given its own authentication tab alongside Azure CLI and Visual Studio Code, while Bash is not explicitly mentioned. Linux instructions are present but sometimes appear after Windows ones.
Recommendations
- Present Linux and macOS instructions alongside or before Windows instructions, especially for environment variable setup.
- Include Bash or terminal authentication instructions explicitly, not just PowerShell.
- Avoid giving Windows-specific tools (PowerShell, setx) prominence over cross-platform alternatives.
- Add explicit macOS instructions where relevant.
- Use neutral language when referring to 'console windows' (e.g., 'terminal or command prompt').
Storage
Customer-managed keys for account encryption
...icles/storage/common/customer-managed-keys-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally cross-platform and avoids explicit Windows bias in most sections. However, in the 'Revoke access to customer-managed keys' section, PowerShell is mentioned before Azure CLI as a tool for revoking access, which subtly prioritizes Windows tooling. There are no explicit Linux/macOS examples, nor are Linux-specific tools or shell commands referenced anywhere. The page does not provide platform-specific command examples, but the ordering and mention of PowerShell first is a minor Windows-first bias.
Recommendations
- List Azure CLI before PowerShell when referencing cross-platform tooling, as Azure CLI is available on Windows, Linux, and macOS.
- Explicitly state that both PowerShell and Azure CLI are supported on all major platforms.
- Where possible, provide example commands for both Azure CLI and PowerShell, and ensure parity in instructions for Linux/macOS users.
- Add a note clarifying that all management actions can be performed from any supported OS using Azure CLI or REST API.
Storage
How to upgrade a General Purpose v1 (GPv1) with ZRS redundancy account to GPv2
...rpose-version-1-zone-redundant-storage-upgrade-process.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides upgrade instructions via the Azure Portal, PowerShell, and Azure CLI. PowerShell is presented as a primary command-line method, which is Windows-centric, and no explicit Linux/macOS shell example (e.g., Bash) is given. The Azure CLI example is cross-platform, but PowerShell is listed before CLI, and no Linux-specific notes or examples are provided.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide example shell commands (e.g., Bash).
- Add a note clarifying that PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS.
- Include troubleshooting or environment-specific notes for Linux/macOS users if any steps differ.
Storage
Prevent authorization with Shared Key
...les/storage/common/shared-key-authorization-prevent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows-centric tools and workflows before their cross-platform equivalents. PowerShell is given as a primary example, and the Azure portal (which is most familiar to Windows users) is described first. While Azure CLI examples are provided and are cross-platform, there are no explicit Linux/macOS-specific instructions or notes, and PowerShell is presented before CLI. There are no references to Linux shell scripting, nor are there any mentions of Linux-specific tools or environments.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and provide any OS-specific notes if relevant.
- Include a brief note or section for Linux/macOS users, confirming that all steps are supported on their platforms.
- If possible, add bash/zsh shell scripting examples for common tasks, especially in sections where PowerShell scripts are shown.
- Ensure that screenshots and navigation instructions in the Azure portal are not Windows-specific (e.g., avoid references to Windows-only UI elements or paths).
Storage
Check the Last Sync Time property for a storage account
...lob/main/articles/storage/common/last-sync-time-get.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides instructions for checking the Last Sync Time property using both PowerShell and Azure CLI. However, PowerShell (a Windows-centric tool) is presented first, and the example is detailed. While Azure CLI is cross-platform and included, there are no Linux/macOS-specific notes or examples, and no mention of Bash or shell scripting patterns. The documentation implicitly prioritizes Windows tooling and patterns.
Recommendations
- Present Azure CLI examples before PowerShell, since CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as Bash usage or shell scripting context.
- Clarify that Azure CLI commands work natively on Linux/macOS, and provide installation links or references for those platforms.
- Consider including a table or section comparing tool availability and usage across platforms.
Storage
Configure passwordless connections between multiple services
...articles/storage/common/multiple-identity-scenarios.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-centric tools (Visual Studio) and patterns (Azure portal navigation, role assignment) before mentioning cross-platform alternatives like Azure CLI. Windows tools are mentioned as examples for local development sign-in, and .NET is presented first in code samples. However, the documentation provides code examples for multiple languages and does not rely on Windows-only features, ensuring Linux/macOS users can follow the instructions.
Recommendations
- Explicitly mention Azure CLI as a cross-platform tool for role assignment and local development, alongside Visual Studio.
- Clarify that all portal steps can be performed from any OS/browser, and provide CLI or PowerShell alternatives for resource and role assignment.
- Rotate the order of language tabs so that .NET is not always presented first, or randomize tab order.
- Add explicit notes or links to Linux/macOS developer setup guides for Azure Identity and managed identities.
- Where developer tools are referenced (e.g., Visual Studio), also mention VS Code and other cross-platform IDEs.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all major operations, but PowerShell (traditionally associated with Windows) is consistently presented before CLI in tab order and example sections. PowerShell prerequisites and commands are described in detail, sometimes with more context than CLI. There are no explicit Linux/macOS-only examples or troubleshooting notes, and no mention of Linux-specific shell patterns or issues. However, CLI instructions (which run natively on Linux/macOS) are present and complete, and Cloud Shell is highlighted as a Bash environment.
Recommendations
- Alternate the order of PowerShell and CLI tabs/examples so CLI is sometimes presented first, especially for cross-platform parity.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide links or notes for installing CLI on those platforms.
- Add troubleshooting notes or tips for Linux/macOS users (e.g., file permissions, shell differences) where relevant.
- Include references to Linux-native tools or patterns where possible (e.g., using Bash scripting for automation).
- Clarify that PowerShell Core is available on Linux/macOS, if PowerShell is required, and provide installation links.
Storage
Introduction to Azure Storage - Cloud storage on Azure
...b/main/articles/storage/common/storage-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Windows tools and patterns (e.g., Azure PowerShell, SMB protocol, drive letter mounting) are mentioned before or more prominently than Linux/macOS equivalents. PowerShell is listed before Azure CLI in multiple places. Some examples and terminology (e.g., drive letters, SMB) are Windows-centric, and Windows tools are referenced first in the tools section. However, Linux/macOS support is acknowledged (e.g., NFS, Azure Storage Explorer for all platforms), and no critical functionality is missing for non-Windows users.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI mentions, or list CLI first where appropriate, as CLI is cross-platform.
- Include explicit Linux/macOS usage examples or references alongside Windows ones, especially for mounting file shares and scripting.
- Add more details or links for Linux/macOS tools and workflows (e.g., mounting Azure Files via NFS on Linux, using AzCopy on Linux/macOS).
- Avoid Windows-centric terminology (e.g., 'drive letter') without also explaining the Linux/macOS equivalent (e.g., mount points).
- Ensure parity in tool recommendations (e.g., highlight AzCopy and Azure CLI as primary cross-platform tools before PowerShell).
Storage
Create an IP network rule for Azure Storage
...ge/common/storage-network-security-ip-address-range.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions for both Azure PowerShell and Azure CLI, but the PowerShell section appears before the CLI section, and PowerShell is traditionally associated with Windows. There are no explicit Linux/macOS-specific examples or notes, and no mention of platform-specific considerations for running PowerShell or CLI commands. The CLI section does provide parity in functionality, but the ordering and emphasis may subtly favor Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Add notes clarifying that Azure CLI works natively on Linux/macOS, while PowerShell may require installation of PowerShell Core on non-Windows systems.
- Include explicit instructions or links for installing and using PowerShell on Linux/macOS, if PowerShell examples are retained.
- Consider adding a table comparing PowerShell and CLI usage across platforms.
- Ensure that screenshots and UI references do not assume a Windows environment.
Storage
Set the default public network access rule: Azure Storage
.../common/storage-network-security-set-default-access.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell (Windows-centric) instructions before Azure CLI (cross-platform) examples. PowerShell is a Windows-first tool, and its inclusion as a primary method may signal bias towards Windows users. However, Azure CLI examples are provided, ensuring Linux/macOS users can follow along. No critical steps are Windows-only, and parity is generally maintained.
Recommendations
- Present Azure CLI (cross-platform) instructions before PowerShell examples, or side-by-side, to avoid Windows-first bias.
- Explicitly note that Azure CLI works on Windows, Linux, and macOS.
- Consider adding Bash or shell script examples for Linux users if relevant.
- Clarify that PowerShell Core is available on Linux/macOS, if PowerShell is retained.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias in the section on creating private endpoints, where PowerShell is mentioned as a primary automation method alongside Azure CLI, and no explicit Linux/macOS shell examples are provided. The ordering of examples places PowerShell before CLI, and there is no mention of Bash or Linux-specific tools or patterns. However, the Azure CLI is cross-platform, and most instructions are generic, so Linux/macOS users can still follow the guidance with minor friction.
Recommendations
- Add explicit Bash/Linux shell examples for creating private endpoints, or clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS.
- When listing automation options, alternate the order or clarify parity between PowerShell and CLI, rather than listing PowerShell first.
- Include a note or section for Linux/macOS users, confirming that all steps are supported and providing links to platform-specific setup guides for Azure CLI.
- If referencing PowerShell, also mention alternatives such as Bash scripts or other Linux-native tools where appropriate.
Storage
Create a resource instance network rule for Azure Storage
.../common/storage-network-security-resource-instances.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples for managing resource instance network rules, with PowerShell presented before Azure CLI. This ordering and emphasis may signal a Windows-centric bias, as PowerShell is primarily associated with Windows. While Azure CLI examples are included, there are no explicit Linux/macOS shell examples or references to platform-specific considerations.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell usage notes or examples where relevant (e.g., environment variable handling, quoting).
- Clarify that PowerShell Core is available cross-platform, if PowerShell examples are retained.
- Consider adding a table comparing PowerShell and CLI usage for parity.
Storage
Azure Storage encryption for data at rest
.../articles/storage/common/storage-service-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits minor Windows bias by referencing BitLocker as an analogy for Azure Storage encryption and linking to the Windows-specific Cryptography API: Next Generation (CNG) for further information about cryptographic modules. No Linux or cross-platform equivalents are mentioned, and Windows terminology appears before any cross-platform discussion. However, the page does not provide platform-specific command-line examples or instructions, and the core guidance is generally platform-neutral.
Recommendations
- Replace or supplement the BitLocker analogy with references to Linux disk encryption tools such as LUKS or dm-crypt to provide parity for Linux users.
- When referencing cryptographic APIs, include links or mentions of cross-platform standards (e.g., OpenSSL, libgcrypt) alongside Windows CNG.
- Explicitly state that Azure Storage encryption is platform-agnostic and does not require OS-specific configuration.
- Add a brief note or table comparing common encryption tools on Windows, Linux, and macOS for context.
Storage
Azure data transfer options for small datasets with low to moderate network bandwidth
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-solution-small-dataset-low-moderate-network.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell as a primary scripting/programmatic option alongside AzCopy and Azure CLI, with PowerShell mentioned before Azure CLI. While most tools are cross-platform, the ordering and emphasis on PowerShell may suggest a Windows-first perspective. No Linux-specific examples or tools are highlighted, and PowerShell is traditionally associated with Windows, despite its cross-platform support. There are no explicit Linux/macOS examples or recommendations.
Recommendations
- Provide explicit Linux/macOS usage examples for AzCopy, Azure CLI, and PowerShell (e.g., installation, command syntax).
- Mention Bash scripting and shell integration as alternatives to PowerShell for Linux/macOS users.
- Reorder scripting/programmatic tool recommendations to list truly cross-platform options (AzCopy, Azure CLI) before PowerShell.
- Include a note clarifying PowerShell's cross-platform availability and any Linux/macOS-specific considerations.
- Add links to Linux/macOS installation guides for each tool.
Storage
Grant limited access to data with shared access signatures (SAS)
...b/main/articles/storage/common/storage-sas-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Get started with SAS' section, where PowerShell is the first example listed for user delegation SAS creation. PowerShell is a Windows-centric tool, and its prominent placement may suggest a Windows-first approach. However, Linux-friendly tools like Azure CLI and SDKs for multiple languages are also referenced, and there are no critical sections that are Windows-only or missing Linux equivalents.
Recommendations
- List Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Ensure parity in example depth and coverage between PowerShell and Azure CLI, and consider adding Bash shell examples where relevant.
- Add a brief note at the start of the 'Get started' section clarifying that all major platforms are supported and that examples are available for Linux/macOS users.
Storage
Authorize access for AzCopy with a user identity
...e/common/storage-use-azcopy-authorize-user-identity.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for environment variable setup, but in some sections (notably 'Authorize by using Azure PowerShell'), only PowerShell examples are given, and PowerShell is presented as a primary method. The Azure PowerShell section lacks Linux/macOS parity, as it does not clarify that PowerShell Core is cross-platform or provide bash equivalents. In most cases, Linux and Windows instructions are present, but Windows/PowerShell is sometimes emphasized or shown first.
Recommendations
- Clarify that Azure PowerShell can be used cross-platform (PowerShell Core), or provide explicit bash equivalents for Linux/macOS users.
- When presenting PowerShell-only sections, add notes or examples for bash/zsh users, or clarify when a feature is Windows-specific.
- Ensure that Linux/macOS instructions are always presented with equal prominence and before or alongside Windows instructions.
- Consider adding a macOS tab where relevant, to reinforce cross-platform support.
Storage
Copy blobs between Azure storage accounts with AzCopy v10
...ticles/storage/common/storage-use-azcopy-blobs-copy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides AzCopy command examples that are cross-platform, but each example includes a tip stating that single quotes should be used except on Windows Command Shell (cmd.exe), where double quotes are required. The tip always mentions Windows first, and does not provide explicit Linux/macOS shell examples or discuss shell-specific nuances beyond quoting. No PowerShell-specific examples or Windows-only tools are used, and all commands are generic AzCopy CLI invocations.
Recommendations
- Present shell quoting guidance for Linux/macOS first, or in parallel with Windows guidance.
- Include explicit example commands for Bash/zsh (Linux/macOS) and cmd.exe/PowerShell (Windows), showing the correct quoting for each.
- Add a table or section summarizing shell differences for AzCopy usage across platforms.
- Clarify that AzCopy is fully cross-platform and provide installation/usage notes for Linux/macOS.
- Mention that the examples work as-is on Linux/macOS, and provide troubleshooting tips for common shell issues on those platforms.
Storage
Replace Azure Blob Storage properties & metadata with AzCopy
...common/storage-use-azcopy-blobs-properties-metadata.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides AzCopy command examples that use single quotes for path arguments, with a recurring tip noting that Windows Command Shell (cmd.exe) requires double quotes instead. This guidance is repeated in each section, but Windows is always mentioned first, and no Linux/macOS-specific shell examples or nuances are provided. There is a subtle bias in the order and framing, but Linux/macOS users can still follow the instructions with minor adaptation.
Recommendations
- Explicitly provide example commands for both Windows (cmd.exe) and Linux/macOS (bash/zsh) shells, showing the correct quoting for each.
- Add a table or section summarizing quoting requirements for major platforms (Windows cmd.exe, PowerShell, Linux/macOS bash/zsh).
- Consider alternating the order in which platforms are mentioned, or present both in parallel to avoid Windows-first bias.
- Include notes about other shell-specific considerations (e.g., escaping, environment variables) for Linux/macOS users.
Storage
Optimize the performance of AzCopy v10 with Azure Storage
...articles/storage/common/storage-use-azcopy-optimize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there is a mild Windows bias in the ordering and example presentation. In environment variable sections, Windows (PowerShell/cmd.exe) examples are presented after Linux, but the tip about quoting paths gives Windows-specific advice first. The documentation references PowerShell/cmd.exe for Windows, but does not mention macOS explicitly, and Linux is referenced more often. No critical functionality is Windows-only, and Linux users can complete all tasks.
Recommendations
- Explicitly mention macOS alongside Linux in all platform-specific instructions.
- Present Linux/macOS and Windows examples in parallel tabs or side-by-side, rather than sequentially.
- When giving tips about quoting or shell behavior, start with a neutral statement or mention all platforms equally.
- Add a note clarifying that AzCopy is supported on Linux, macOS, and Windows, and provide links to platform-specific installation guides if available.
Storage
Copy from Google Cloud Storage to Azure Storage with AzCopy
...cles/storage/common/storage-use-azcopy-google-cloud.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux/macOS instructions for setting environment variables, and it explicitly notes differences in quoting for command shells. However, in the section about quoting, Windows Command Shell (cmd.exe) is mentioned first and separately, and the guidance is tailored to Windows users before mentioning Linux/macOS shells. There are no PowerShell-only examples, and all AzCopy command examples are cross-platform. No Windows-only tools or patterns are present.
Recommendations
- Present Linux/macOS instructions before or alongside Windows instructions to avoid Windows-first bias.
- Clarify that AzCopy commands are identical across platforms except for quoting, and provide explicit examples for both quoting styles.
- Consider providing PowerShell and Bash example blocks side-by-side for environment variable setting and command usage.
- Ensure that any platform-specific notes are grouped together and given equal prominence.
Storage
Copy data from Amazon S3 to Azure Storage by using AzCopy
.../main/articles/storage/common/storage-use-azcopy-s3.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows credential-setting commands first and providing both PowerShell and Command Prompt examples, while Linux/macOS only get a single export command. Additionally, guidance on quoting in command shells prioritizes Windows (cmd.exe) and notes its difference, but does not provide explicit Linux/macOS shell examples or troubleshooting tips. All AzCopy usage examples are generic and cross-platform, but Windows-specific instructions are given more detail and precedence.
Recommendations
- Present Linux/macOS credential-setting commands before or alongside Windows commands, rather than after.
- Include explicit example commands for Linux/macOS shells (e.g., bash, zsh) where quoting or environment variable differences may arise.
- Add troubleshooting notes or tips for Linux/macOS users, such as common permission issues or shell-specific behaviors.
- Ensure parity in detail and explanation for Linux/macOS commands, not just listing them as a single line.
- Consider including a table or section that equally highlights cross-platform differences and best practices.
Storage
Enforce a Minimum Required Version of Transport Layer Security (TLS)
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/transport-layer-security-configure-minimum-version.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation exhibits mild Windows bias. It references Windows-specific implementation details (e.g., SSL stack not based on OpenSSL), gives PowerShell examples (Windows-centric) before Azure CLI, and links to Application Gateway configuration via PowerShell. However, Azure CLI and ARM template examples are provided, which are cross-platform, and no critical steps are Windows-only.
Recommendations
- Add explicit Linux/macOS notes or examples where relevant, especially for client-side TLS testing and configuration.
- When referencing Application Gateway SSL policy configuration, provide Azure CLI or REST API alternatives alongside PowerShell.
- Clarify that Azure CLI commands work on Linux/macOS and provide installation links for those platforms.
- Avoid statements that imply Windows is the default or primary platform unless technically necessary.
- If mentioning implementation details (e.g., SSL stack), briefly note Linux/OpenSSL differences or implications.