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 1576-1600 of 1657 flagged pages
Storage
Understand storage account migration from classic to Azure Resource Manager
...es/storage/common/classic-account-migration-process.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references migration using the Azure portal, PowerShell, and Azure CLI, listing PowerShell (a Windows-centric tool) before Azure CLI (cross-platform). In the 'See also' and 'Validation' sections, PowerShell migration guides are mentioned before Azure CLI equivalents. No Linux-specific tools or shell examples are provided, and there is no explicit mention of Linux/macOS environments or considerations.
Recommendations
- List Azure CLI (cross-platform) before PowerShell when describing migration options.
- Explicitly mention that Azure CLI works on Linux/macOS and provide example commands for these platforms.
- Include a note or section addressing Linux/macOS users, clarifying that all migration steps can be performed on non-Windows systems using Azure CLI.
- Ensure parity in referenced guides: if a PowerShell guide is linked, also link to the CLI guide and vice versa.
Create Pull Request
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 its main content. However, there are subtle signs of Windows-first bias: PowerShell is mentioned before Azure CLI as a tool for revoking access to customer-managed keys, and the reference to managed disk encryption links to separate Windows and Linux pages, with the Windows link listed first. No examples or instructions are given that are Windows-only, and Azure CLI is mentioned as an alternative, but the ordering and tool references show a slight preference for Windows.
Recommendations
- List Azure CLI before PowerShell when mentioning tools for key management, or present both equally.
- Ensure that Linux/macOS tools and workflows are referenced with equal prominence and ordering as Windows tools.
- Where links are provided for both Windows and Linux, alternate the order or clarify that both are equally supported.
- Add explicit examples or notes for Linux/macOS users where relevant, especially in sections mentioning command-line tools.
Storage
Enable infrastructure encryption for double encryption of data
...les/storage/common/infrastructure-encryption-enable.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows-centric tooling (PowerShell) before cross-platform options (Azure CLI), and provides detailed PowerShell examples. While Azure CLI examples are included and are cross-platform, the ordering and emphasis may subtly favor Windows users. No Linux/macOS-specific examples or troubleshooting are provided, and there is no mention of shell-specific considerations for non-Windows platforms.
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 provide any necessary shell syntax notes (e.g., line continuation differences).
- Add a short section or note for Linux/macOS users, confirming parity and highlighting any platform-specific caveats.
- Consider including Bash or shell script examples where appropriate.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing Windows-only UI elements).
Storage
Apply an Azure Resource Manager lock to a storage account
.../main/articles/storage/common/lock-account-resource.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for applying an Azure Resource Manager lock via the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, and there is explicit mention of the Az PowerShell module, which is primarily used on Windows. There are no Linux/macOS-specific instructions or notes, and the CLI example is not highlighted as cross-platform. The documentation does not mention Linux tools or shell patterns, nor does it clarify that Azure CLI is available on Linux/macOS.
Recommendations
- Explicitly state that Azure CLI is cross-platform and available on Linux/macOS.
- Provide Linux/macOS shell example syntax (e.g., bash/zsh) for Azure CLI commands, including environment variable usage.
- Consider listing Azure CLI instructions before PowerShell, as CLI is more universal.
- Add a note about installing Azure CLI on Linux/macOS, with a link to installation instructions.
- If possible, include screenshots or references for Linux/macOS users in portal instructions.
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: Azure portal instructions and role assignment steps are presented without explicit mention of platform differences, but the local development section references Windows-centric tools (Visual Studio) before cross-platform alternatives (Azure CLI). The overall flow and examples are cross-platform, and all code samples are provided for multiple languages without OS-specific commands. However, Windows tools are mentioned first and more prominently than Linux/macOS equivalents.
Recommendations
- Explicitly mention cross-platform alternatives (e.g., VS Code, Azure CLI, PowerShell Core) alongside Visual Studio when discussing local development tooling.
- Clarify that Azure portal steps are identical across platforms and provide CLI or ARM template alternatives for users who prefer command-line or automation approaches.
- In local development sections, list Azure CLI before Visual Studio, or mention both together to avoid Windows-first ordering.
- Add a brief note confirming that all code samples and steps are OS-agnostic unless stated otherwise.
Storage
Upgrade to a general-purpose v2 storage account
...ain/articles/storage/common/storage-account-upgrade.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides upgrade instructions for Azure storage accounts using the Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given a dedicated section and example, and is listed before Azure CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are cross-platform considerations (such as OS-specific installation notes) discussed. The ordering and emphasis slightly favor Windows users.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users where relevant.
- Clarify that Azure CLI is fully cross-platform and provide installation links for Linux/macOS alongside Windows.
- Consider listing Azure CLI instructions before PowerShell, as CLI is more universally accessible.
- Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance.
- Ensure screenshots and UI references are OS-neutral or provide notes for differences.
Storage
Determine which encryption key model is in use for the storage account
...les/storage/common/storage-encryption-key-model-get.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides three approaches: Azure portal, PowerShell, and Azure CLI. PowerShell is presented as a primary command-line example, which is Windows-centric. The Azure CLI example is cross-platform, but PowerShell is listed before CLI, and no Linux/macOS-specific shell examples (e.g., Bash) are given. There is no mention of Linux-specific tools or considerations.
Recommendations
- List Azure CLI examples before PowerShell to emphasize cross-platform parity.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Provide Bash or shell script examples for Linux/macOS users, if relevant.
- Add a note clarifying that PowerShell is primarily for Windows, while Azure CLI is cross-platform.
Storage
Choose an Azure solution for data transfer
...torage/common/storage-choose-data-transfer-solution.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows minor Windows bias by listing PowerShell examples before Azure CLI examples in the 'Next steps' section and mentioning Azure PowerShell as a scriptable tool alongside AzCopy and Azure CLI. However, Linux/macOS users are not blocked from completing any tasks, as Azure CLI and SDKs for multiple languages are also referenced.
Recommendations
- List Azure CLI examples before PowerShell examples in the 'Next steps' section to reflect cross-platform parity.
- Explicitly mention that AzCopy and Azure CLI are cross-platform tools, and provide links to Linux/macOS installation guides.
- Add a note clarifying that Azure PowerShell is primarily for Windows, while Azure CLI is recommended for Linux/macOS.
- Ensure that graphical tools (like Azure Storage Explorer) are described as cross-platform where applicable.
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 creating IP network rules in Azure Storage using the Portal, PowerShell, and Azure CLI. The PowerShell section is presented before the Azure CLI section, which may suggest a Windows-first bias. PowerShell is primarily a Windows tool, though it is available on other platforms. There are no Linux-specific tools or shell examples (e.g., Bash), but the Azure CLI section does provide parity for Linux/macOS users. No critical functionality is missing for non-Windows users.
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.
- Consider adding Bash script examples or notes for Linux users where relevant.
- Clarify that PowerShell is available cross-platform, but CLI may be more familiar to Linux/macOS users.
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 shows mild Windows bias. Windows tools and patterns (e.g., Azure PowerShell, SMB protocol, Active Directory) are mentioned before or more prominently than Linux equivalents. PowerShell is listed before Azure CLI in several places, and Windows protocols (SMB) and identity solutions (Active Directory) are referenced more often than Linux/NFS alternatives. However, Linux/macOS support is acknowledged, and most features are described as cross-platform.
Recommendations
- Present Azure CLI examples and references before or alongside PowerShell, as CLI is cross-platform.
- Explicitly mention Linux/macOS support for all tools and protocols (e.g., clarify that Azure CLI, AzCopy, and Storage Explorer work on Linux/macOS).
- Provide Linux/NFS examples and references with equal prominence to SMB/Windows examples.
- Include references to Linux authentication and identity solutions where relevant (e.g., Kerberos, LDAP).
- Ensure that sample scenarios and feature lists mention Linux/macOS compatibility and usage patterns.
- Where Windows-specific tools or protocols are mentioned, add equivalent Linux/macOS instructions or links.
Storage
Manage network security exceptions for Azure Storage
...e/common/storage-network-security-manage-exceptions.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing network security exceptions. However, PowerShell (typically associated with Windows) is presented before Azure CLI, which is cross-platform and more commonly used on Linux/macOS. There is a slight bias in ordering, but all critical steps are covered for Linux users via Azure CLI.
Recommendations
- Present Azure CLI examples before PowerShell, or clarify that CLI is cross-platform and suitable for Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Consider adding Bash or shell script examples for common automation scenarios.
- Add a note about PowerShell Core availability on Linux/macOS if relevant.
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 a comparison for Azure Storage encryption and linking to the Windows-specific Cryptography API: Next Generation (CNG) for further information about cryptographic modules. These references may make Windows users feel more at home, but do not provide equivalent Linux/macOS comparisons or resources. No examples or tooling are provided that are exclusive to Windows, and SDK/library coverage is cross-platform.
Recommendations
- When comparing Azure Storage encryption to BitLocker, also mention Linux/macOS equivalents such as LUKS or FileVault to provide parity.
- In addition to referencing Windows CNG, include links or notes about cryptographic modules and standards relevant to Linux/macOS environments (e.g., OpenSSL, libgcrypt, or platform FIPS modules).
- Ensure that any future examples or tooling references include both Windows and Linux/macOS options, especially if command-line or scripting is involved.
Storage
Transfer data to or from Azure Files by using AzCopy v10
...in/articles/storage/common/storage-use-azcopy-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Path Examples
Windows Shell Notes
Summary
The documentation provides both Windows (SMB) and Linux (NFS) examples for all major AzCopy operations, using tabbed sections for parity. However, Windows-style paths (e.g., C:\myDirectory) and Windows Command Shell (cmd.exe) quoting conventions are consistently presented first in notes and examples. Guidance for quoting paths is Windows-centric, with Linux/macOS instructions presented as exceptions. No PowerShell-specific examples or Windows-only tools are present, and Linux/NFS scenarios are clearly called out where relevant. Overall, Linux parity is strong, but Windows paths and conventions are prioritized in presentation.
Recommendations
- Alternate the order of examples so that Linux/NFS examples are sometimes shown first.
- Provide a summary table or section at the top highlighting OS-specific requirements and conventions (quoting, path separators) for all platforms equally.
- Include explicit macOS notes where relevant, as current notes only mention Linux and Windows.
- Consider using generic paths (e.g., /home/user/myDirectory or ~/myDirectory) in introductory syntax examples before showing OS-specific tabs.
- Clarify in notes that Linux/NFS operations are not supported on Windows/macOS, and vice versa, to help users quickly identify platform limitations.
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 with a tip about quoting conventions, mentioning Windows Command Shell (cmd.exe) first and instructing users to use double quotes on Windows and single quotes elsewhere. However, all actual command examples use single quotes, which are suitable for Linux/macOS shells but not for Windows cmd.exe. No PowerShell-specific examples or Windows-only tools are present, and Linux/macOS usage is implicitly supported. The only bias is the ordering and phrasing of the quoting tip, which places Windows first.
Recommendations
- Explicitly show both quoting styles in examples, or provide a table illustrating the differences for Windows cmd.exe, PowerShell, Linux, and macOS shells.
- Include a brief note or section confirming AzCopy is cross-platform and that all commands work on Linux/macOS with the provided quoting style.
- Consider rephrasing the quoting tip to mention Linux/macOS first or present all platforms equally.
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
Powershell Heavy
Summary
The documentation shows minor Windows bias. In sections discussing environment variable setup and quoting conventions, Windows commands and behaviors are presented first or with special notes, while Linux/macOS equivalents are included but not emphasized. The examples themselves are platform-neutral, but guidance for Windows users is more explicit.
Recommendations
- Present Linux/macOS commands before or alongside Windows commands in environment variable setup tables.
- Provide explicit notes for Linux/macOS shell quoting conventions, not just exceptions for Windows cmd.exe.
- Include brief instructions or links for installing AzCopy on Linux/macOS, similar to the Windows guidance.
- Ensure troubleshooting and next steps sections mention cross-platform considerations.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents Windows/Powershell instructions and examples before Linux/Azure CLI equivalents in multiple sections. The disconnect script section lists Windows first, and the deletion commands use PowerShell as the primary tab before Azure CLI. While Linux instructions are present and functional, the ordering and prominence favor Windows users.
Recommendations
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Use neutral tab ordering (e.g., Azure CLI first, or alphabetical) for command examples.
- Explicitly mention parity between PowerShell and CLI commands to reassure non-Windows users.
- Consider adding macOS-specific notes if relevant.
- Ensure terminology and parameter explanations are equally detailed for both platforms.
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 provides both Linux and Windows examples for environment variable configuration, but Windows (cmd.exe and PowerShell) is mentioned first in tips and example explanations. The guidance for quoting arguments prioritizes Windows-specific behavior before mentioning Linux shells. There is a slight tendency to present Windows instructions or considerations before Linux equivalents, though both platforms are ultimately covered.
Recommendations
- Present Linux and Windows instructions in parallel or in a neutral order, rather than Windows-first.
- When discussing shell quoting, mention Linux/macOS conventions first or equally, given the prevalence of Bash in cross-platform scenarios.
- Ensure that all examples and tips explicitly mention macOS where applicable, not just Linux.
- Consider using a tabbed or side-by-side format for platform-specific instructions throughout, not just for environment variables.
- Review for any subtle language that implies Windows is the default or primary platform.
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 page exhibits mild Windows bias. It references Windows-specific implementation details (e.g., Azure Storage relies on Windows SSL, not OpenSSL), and the PowerShell example is presented before the Azure CLI example. The documentation also links to Application Gateway configuration using PowerShell, and screenshots and step-by-step instructions are portal-centric (which is cross-platform but often Windows-oriented in practice). However, Azure CLI and ARM template examples are provided, which are platform-agnostic and usable on Linux/macOS.
Recommendations
- Add explicit Linux/macOS notes or examples where relevant, especially for client-side TLS testing and configuration.
- Reference OpenSSL or other cross-platform tools for TLS testing and troubleshooting, not just Windows SSL.
- Ensure CLI examples are presented before or alongside PowerShell examples to emphasize cross-platform parity.
- Where screenshots or instructions are portal-centric, clarify that the portal is accessible from any OS/browser.
- If referencing Application Gateway configuration, provide both PowerShell and Azure CLI (or REST API) links/examples.
Storage
Best practices for configuring an Elastic SAN
...cles/storage/elastic-san/elastic-san-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides parity between Windows and Linux, offering configuration guidance and examples for both platforms. However, there is a noticeable Windows bias: Windows examples and tools (PowerShell, Registry Editor, iSCSI Initiator app) are often presented first, and Windows-specific instructions are more detailed, with screenshots and references to Windows tools. Linux instructions are present and reasonably complete, but lack the same level of visual guidance and tool-specific references. Azure CLI is mentioned but PowerShell is referenced first for enabling Accelerated Networking.
Recommendations
- Alternate the order of Windows and Linux sections to avoid consistently presenting Windows first.
- Provide Linux screenshots and step-by-step visual guides similar to those given for Windows (e.g., updating iSCSI initiator name).
- Reference Linux tools (e.g., iscsiadm, multipath-tools) with equal prominence and detail as Windows tools.
- Include Azure CLI examples before or alongside PowerShell examples for cross-platform parity.
- Ensure that all configuration steps are equally detailed for both platforms, including troubleshooting and validation steps.
Storage
Use clustered applications on Azure Elastic SAN
...cles/storage/elastic-san/elastic-san-shared-volumes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions Windows Server Failover Cluster (WSFC) before Pacemaker when listing cluster managers, and does not provide any concrete examples, scripts, or guidance for either Windows or Linux. However, the ordering and naming suggest a slight Windows-first bias, and there are no Linux-specific instructions or examples to ensure parity.
Recommendations
- Provide example workflows or scripts for both Windows (WSFC) and Linux (Pacemaker) cluster managers.
- Explicitly mention how to configure SCSI-3 Persistent Reservations using common Linux tools (e.g., sg_persist, multipath) and provide command-line examples.
- Ensure that Linux and macOS users are given equal visibility and guidance for deploying clustered applications on Elastic SAN.
- Consider listing cluster managers in alphabetical order or alternating which platform is mentioned first.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias: Windows-specific backup coordination tools (Volume Shadow Service) are mentioned before Linux equivalents, and PowerShell examples are consistently presented before Azure CLI examples. The documentation refers to Windows applications and tools first, and PowerShell is given equal or greater prominence than Azure CLI, which is more cross-platform. However, Linux is acknowledged, and CLI examples are provided for all tasks.
Recommendations
- Mention Linux coordination tools (e.g., fsfreeze) before or alongside Windows tools like Volume Shadow Service.
- Provide more detail or examples for Linux application-consistent backup strategies, not just file-consistent (e.g., using LVM snapshots, database-specific tools).
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first to emphasize cross-platform support.
- Clarify that Azure CLI works on Windows, Linux, and macOS, and encourage its use for non-Windows users.
- Add explicit notes or examples for macOS users where relevant.
Storage
Migrate to SMB Azure file shares using Azure Storage Mover
.../articles/storage/files/migrate-files-storage-mover.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools like Robocopy are referenced as migration alternatives, and the agent deployment instructions mention Hyper-V and VMware (both common in Windows environments) without explicit Linux VM guidance. There are no Linux-specific migration examples, and the mention of Azure PowerShell precedes Azure CLI, which is more cross-platform. While the page states that SMB sources can be Windows, Linux, or NAS, practical steps and examples are not provided for Linux users.
Recommendations
- Add explicit Linux migration examples, such as how to mount SMB shares on Linux and register the agent from a Linux VM.
- Include instructions for deploying the Storage Mover agent on popular Linux hypervisors (e.g., KVM, VirtualBox) and cloud VMs.
- Reference Linux-native tools (e.g., rsync, smbclient) as alternatives or for verification, where appropriate.
- Present Azure CLI examples before or alongside Azure PowerShell, emphasizing CLI's cross-platform nature.
- Clarify any OS-specific requirements or differences in agent installation and operation.
Storage
Introduction to Azure Queue Storage
...articles/storage/queues/storage-queues-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Next steps' section. The quickstart links for .NET, Java, Python, and Node.js all specify tabs or environment variables related to Windows (e.g., 'environment-variable-windows') and PowerShell, with no mention of Linux or macOS equivalents. This may create friction for non-Windows users seeking platform-specific guidance.
Recommendations
- Add explicit Linux/macOS tabs or instructions to quickstart guides, including environment variable setup and CLI usage.
- Ensure examples and walkthroughs are available for Bash and other common Linux shells, not just PowerShell.
- Review linked quickstart pages to confirm parity in platform coverage and update links/tabs to reflect cross-platform support.
Storage
Configure a Site-to-Site VPN for Azure Files
...icles/storage/files/storage-files-configure-s2s-vpn.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation exhibits mild Windows bias by mentioning Windows Server's RRAS as the only example of an on-premises VPN appliance, without listing Linux alternatives. Windows Server is referenced before any Linux solution, and the RRAS documentation is linked directly. However, the main configuration steps for Azure resources are provided via Azure Portal, PowerShell, and CLI, which are cross-platform. Mounting instructions for Windows, macOS, and Linux are linked at the end, ensuring parity for file share access.
Recommendations
- Explicitly mention common Linux VPN appliances (e.g., strongSwan, OpenVPN, Libreswan) as supported options alongside Windows RRAS.
- Provide links to Linux VPN gateway configuration guides, similar to the RRAS link for Windows.
- List both Windows and Linux options together when discussing on-premises VPN appliances, rather than mentioning Windows first.
- Add a brief example or reference for configuring a Linux-based VPN gateway in the 'Configure on-premises network appliance' section.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally presents Windows concepts and tools before Linux/macOS equivalents, such as mentioning PowerShell and Windows-specific features (e.g., Azure File Sync) more prominently. While Linux and macOS are acknowledged, Windows terminology and tools are often foregrounded, and scripting/tooling examples reference PowerShell before Azure CLI. However, explicit Linux/macOS examples are not missing, and parity is maintained in the 'Next steps' section.
Recommendations
- Ensure that scripting and tooling sections mention Azure CLI and cross-platform tools before or alongside PowerShell.
- When describing features like Azure File Sync, clarify their Windows-only nature and highlight any Linux/macOS alternatives or limitations.
- Balance the order of platform mentions (e.g., sometimes list Linux/macOS before Windows, or use neutral phrasing).
- Provide equal depth and visibility for Linux/macOS management and mounting scenarios throughout the documentation, not just in the 'Next steps' section.