Azure Netapp Files

252
Total Pages
149
Linux-Friendly Pages
103
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

896 issues found
Showing 826-850 of 896 flagged pages
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/reestablish-deleted-volume-relationships.md ...tapp-files/reestablish-deleted-volume-relationships.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page primarily uses Azure PowerShell commands for feature registration, with PowerShell examples shown first and in detail. The mention of Azure CLI (which is cross-platform and more common on Linux) is brief and lacks example commands, creating a Windows-first impression and making it harder for Linux users to follow along.
Recommendations
  • Provide Azure CLI command examples alongside PowerShell examples for all feature registration and status-checking steps.
  • Present Azure CLI and PowerShell examples in parallel or with equal prominence, rather than prioritizing PowerShell.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider including bash shell script snippets or Linux terminal screenshots where appropriate to demonstrate parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-performance-metrics-volumes.md ...iles/azure-netapp-files-performance-metrics-volumes.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally aims for cross-platform neutrality, mentioning both Linux and Windows for tools like FIO and providing links to both Windows and Linux VM sizing. However, there is subtle Windows bias: the VM sizing section lists the Windows VM sizes link before the Linux equivalent, and there are no explicit Linux command-line examples (e.g., FIO usage on Linux), nor are there any Linux-specific screenshots or walkthroughs. The only API example uses curl, which is cross-platform but more common on Linux, yet there are no PowerShell or Windows CLI examples either. The 'Performance benchmarks for Linux' is relegated to a 'Next steps' link rather than being integrated into the main content.
Recommendations
  • Provide explicit Linux and Windows command-line examples for running FIO or SSB, showing both platforms equally.
  • Alternate the order of Windows and Linux references (e.g., sometimes list Linux first).
  • Include Linux-specific screenshots or terminal output where appropriate.
  • Integrate Linux benchmarking guidance directly into the main content, not just as a 'Next steps' link.
  • If API examples are shown with curl, consider also showing PowerShell/Windows CLI equivalents for parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/configure-customer-managed-keys.md .../azure-netapp-files/configure-customer-managed-keys.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring customer-managed keys, but there is a notable emphasis on PowerShell, which is primarily a Windows tool. The PowerShell section is given equal prominence to the Azure CLI, despite CLI being cross-platform, and there are no explicit Linux shell (bash) or scripting examples. The documentation does not mention or demonstrate Linux-specific workflows or tools, and PowerShell is presented as a primary automation method alongside the CLI.
Recommendations
  • Clearly state that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
  • Add explicit bash shell examples (where relevant) to show Linux-native scripting, especially for variable assignment and command chaining.
  • De-emphasize PowerShell as a primary automation method, or clarify that PowerShell Core is available cross-platform, but provide bash alternatives for Linux users.
  • Include a section or note for Linux users, highlighting any OS-specific considerations or confirming that all steps are supported on Linux.
  • Where screenshots or UI references are shown, clarify that the Azure Portal is OS-agnostic and accessible from any browser.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/default-individual-user-group-quotas-introduction.md ...s/default-individual-user-group-quotas-introduction.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows client instructions (Windows Explorer and dir command) before Linux client instructions, and references Windows-specific concepts (Security Identifiers/SIDs) before UNIX equivalents (UIDs/GIDs). Windows tools and patterns are mentioned first in several places, and the 'Next steps' section links to Windows-specific documentation. However, both Windows and Linux examples are present, and Linux parity is generally maintained in technical content.
Recommendations
  • Alternate the order of Windows and Linux client instructions in relevant sections, or present them in parallel to avoid implicit prioritization.
  • When introducing user/group identification, mention UNIX (UID/GID) and Windows (SID) concepts together, or start with UNIX when discussing NFS.
  • In 'Next steps', provide links to both Windows and Linux documentation for related concepts (e.g., link to Linux user/group management alongside Windows Security Identifiers).
  • Ensure that all example scenarios and screenshots are balanced between Windows and Linux clients.
  • Explicitly state that both Windows and Linux clients are supported and that instructions apply equally, where appropriate.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/application-volume-group-add-volume-secondary.md ...files/application-volume-group-add-volume-secondary.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell limitations in a prominent callout and includes a shared include file about CLI & PowerShell, but does not provide any Linux-specific (bash, shell, or Linux CLI) examples or mention Linux-native tools. The only command-line context is PowerShell, and the documentation does not clarify parity or provide Linux-first or cross-platform examples, which may lead Linux users to feel unsupported.
Recommendations
  • Add explicit Linux CLI (bash/az CLI) examples alongside or before PowerShell references.
  • Clarify whether all steps and tools are supported equally on Linux and Windows, especially for SAP HANA administrators who are often on Linux.
  • Replace or supplement the '[Application volume group CLI & PowerShell limitation]' include with a cross-platform note, or provide a Linux-specific limitations section if applicable.
  • Where screenshots or UI steps are shown, add notes or examples relevant to Linux environments (e.g., mounting NFS volumes from Linux hosts).
  • Ensure that any references to command-line tools or scripts are provided in both PowerShell and bash/az CLI formats.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azacsnap-release-notes.md .../articles/azure-netapp-files/azacsnap-release-notes.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally presents Windows support and features before or more prominently than Linux equivalents, especially in recent release notes. For example, new features for Microsoft SQL Server on Windows are highlighted, and Windows support is called out as a major milestone. However, there are no explicit examples or instructions tailored for Linux users, nor are Linux-specific tools or patterns discussed, despite the tool supporting both platforms. This may give the impression of a Windows-centric focus and leaves Linux users with less guidance.
Recommendations
  • When introducing new features, provide parity in examples and explanations for both Windows and Linux platforms.
  • Explicitly mention Linux support and features alongside Windows, rather than after or as an aside.
  • Include Linux-specific configuration examples, troubleshooting tips, and references to common Linux tools or patterns where relevant.
  • Ensure that documentation for environment variables, configuration files, and command usage includes Linux shell and scripting examples, not just generic or Windows-centric instructions.
  • Highlight any differences or considerations for Linux users, such as file paths, permissions, or service management, to improve clarity and usability.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md ...app-files/azure-netapp-files-solution-architectures.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is organized to present Windows and SQL Server solutions before Linux and open-source solutions in several sections, and references to Windows-specific tools (e.g., DFS Namespaces, FSLogix, SMB, Windows DFS-N) are present. However, Linux solutions are also well-represented, especially for SAP, Oracle, and HPC workloads. There are no clear cases of missing Linux examples where a Windows example is present, and Linux tools and patterns are included where relevant.
Recommendations
  • Reorder sections or present Linux and Windows solutions in parallel to avoid the perception of Windows-first bias.
  • When referencing Windows-specific tools (e.g., DFS Namespaces, FSLogix), ensure that Linux/NFS equivalents or alternatives are also mentioned and linked where possible.
  • In sections like Virtual Desktop Infrastructure, provide explicit guidance or references for Linux-based VDI solutions if supported.
  • Where possible, use neutral terminology (e.g., 'file sharing' instead of 'SMB file sharing') and clarify when a solution is cross-platform.
  • Add a summary table or matrix mapping solution types to both Windows and Linux workloads to highlight parity and available guidance.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/convert-nfsv3-nfsv41.md ...in/articles/azure-netapp-files/convert-nfsv3-nfsv41.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation demonstrates a mild Windows bias in the feature registration section, where Azure PowerShell commands are presented first and most prominently, with Azure CLI (cross-platform) only mentioned in passing. However, the main workflow examples for converting NFS volumes and client-side operations are Linux-centric, using Linux commands and file paths. There are no exclusive Windows tools or missing Linux examples in the core NFS conversion steps.
Recommendations
  • Present Azure CLI commands alongside Azure PowerShell commands in the feature registration section, giving them equal prominence and example code blocks.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is often used on Windows.
  • Consider providing a brief note or example for users managing NFS mounts from Windows (if supported), or clarify that the workflow is intended for Linux/UNIX clients.
  • Maintain parity in all command-line examples by offering both PowerShell and CLI alternatives where applicable.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/customer-managed-keys-cross-tenant.md ...ure-netapp-files/customer-managed-keys-cross-tenant.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by presenting Azure PowerShell commands first for feature registration and status checking, with Azure CLI commands mentioned only as an alternative in text. The only explicit command-line examples for feature registration are in PowerShell, while the rest of the process uses Azure CLI and REST, which are cross-platform. There are no Linux-specific examples or guidance, but the CLI and REST steps are platform-agnostic.
Recommendations
  • Provide Azure CLI command examples alongside or before PowerShell examples for feature registration and status checking.
  • Explicitly state that all CLI and REST commands work on Linux, macOS, and Windows.
  • Where PowerShell is used, offer equivalent Bash/Linux shell commands if possible.
  • Add a note or section clarifying that the instructions are cross-platform and do not require Windows or PowerShell.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/default-individual-user-group-quotas-introduction.md ...s/default-individual-user-group-quotas-introduction.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, but in the 'Observing user quota settings and consumption' section, Windows client instructions are presented before Linux client instructions, and Windows-specific tools (Windows Explorer, dir command) are mentioned explicitly. Linux instructions are present and use the standard quota(1) tool, but the ordering and explicit mention of Windows tools indicate a mild 'Windows-first' and 'windows_tools' bias.
Recommendations
  • Alternate the order of client instructions (e.g., present Linux first in some sections or use a neutral ordering such as alphabetical).
  • Explicitly mention equivalent tools or commands for both platforms in parallel, rather than describing Windows tools in more detail or first.
  • Where possible, provide screenshots or examples for both platforms with equal prominence.
  • In the 'Next steps' section, consider linking to Linux/UNIX identity documentation alongside the Windows Security Identifiers link.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-integration.md ...ob/main/articles/azure-netapp-files/faq-integration.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by mentioning Windows VMs and SMB mapping on Windows VMs before Linux equivalents, and by omitting explicit instructions or examples for Linux when discussing SMB shares. While NFS mounting is mentioned for both Windows and Linux VMs, SMB mapping is only described for Windows, with no mention of Linux SMB clients or usage.
Recommendations
  • Provide explicit examples or instructions for mounting Azure NetApp Files SMB shares on Linux VMs, including references to common Linux tools (e.g., mount.cifs, smbclient).
  • When listing supported platforms or use cases, mention Linux and Windows in parallel (e.g., 'You can mount Azure NetApp Files NFS volumes on both Windows and Linux VMs. You can map SMB shares on both Windows and Linux VMs.').
  • Include links to relevant Linux documentation or guides for both NFS and SMB usage.
  • Review all integration scenarios to ensure Linux is given equal prominence and technical detail as Windows.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/large-volumes-requirements-considerations.md ...app-files/large-volumes-requirements-considerations.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a mild Windows bias by providing an Azure PowerShell example first for checking feature registration, with the Azure CLI (cross-platform) alternative only mentioned in passing and without a full example. No Linux-specific tools or shell commands are shown, and the only explicit code block is for PowerShell. However, the rest of the document is largely platform-neutral, and there is a reference to Linux performance benchmarks.
Recommendations
  • Provide both Azure PowerShell and Azure CLI examples in code blocks, with equal prominence and detail.
  • Consider listing the Azure CLI (which is cross-platform and commonly used on Linux) example before or alongside PowerShell, not after.
  • Where possible, include Linux shell command examples (e.g., using az CLI in bash) to demonstrate parity.
  • Ensure that any references to tools or commands are balanced between Windows and Linux environments, or clearly indicate cross-platform compatibility.
  • If referencing performance benchmarks for Linux, consider also referencing any available for Windows, or clarify if Linux is the primary supported/tested platform.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/monitor-volume-capacity.md ...articles/azure-netapp-files/monitor-volume-capacity.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows (SMB) client instructions before Linux (NFS) client instructions, and provides more detailed, step-by-step guidance for Windows users (including both GUI and command-line options with screenshots). Windows-specific tools and patterns (File Explorer, dir command) are mentioned and illustrated, while the Linux section is more concise and only covers the df command. There is no evidence of missing Linux examples, but the ordering and depth favor Windows.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel to avoid implicit prioritization.
  • Provide equivalent depth for Linux instructions, such as including both GUI (if available, e.g., GNOME Files) and CLI examples, and screenshots for Linux tools.
  • Mention Linux-specific nuances or alternative commands (e.g., using 'lsblk', 'stat', or graphical disk utilities) where appropriate.
  • Ensure REST API and CLI sections reference cross-platform usage equally, and avoid linking PowerShell as the only scripting example.
  • Explicitly state that both Windows and Linux are equally supported and provide parity in troubleshooting tips and caveats.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/reestablish-deleted-volume-relationships.md ...tapp-files/reestablish-deleted-volume-relationships.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation primarily uses Azure PowerShell commands for feature registration, with Azure CLI (cross-platform) only mentioned secondarily and without example syntax. This prioritizes Windows/PowerShell usage and may disadvantage Linux or macOS users who typically use Azure CLI.
Recommendations
  • Provide Azure CLI command examples alongside PowerShell for all steps, not just a mention.
  • Present Azure CLI and PowerShell examples in parallel or with equal prominence, rather than PowerShell first.
  • Explicitly state that both Azure CLI and PowerShell can be used on all platforms, and link to installation guides for both.
  • Consider including Bash shell examples for relevant operations, especially for Linux users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/snapshots-restore-file-client.md ...es/azure-netapp-files/snapshots-restore-file-client.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux (NFS) and Windows (SMB) client instructions for restoring files from snapshots, with clear parity in basic restore steps. However, the Windows section includes additional restore options (using the 'Previous Versions' tab) and multiple screenshots, whereas the Linux section is limited to command-line instructions without mention of graphical tools or advanced features. The Windows instructions also reference Windows-specific UI elements and tools, potentially giving the impression of richer support or easier workflows on Windows.
Recommendations
  • Add information about graphical file managers on Linux (e.g., Nautilus, Dolphin) and how users can access the .snapshot directory and restore files using a GUI, similar to the Windows screenshots.
  • If available, mention any Linux desktop environment features or third-party tools that provide snapshot browsing or file restoration (e.g., GNOME's file versioning, Timeshift, or integration with NetApp snapshots).
  • Include screenshots for the Linux workflow to match the visual guidance provided for Windows users.
  • If Windows 'Previous Versions' is highlighted, clarify whether there are equivalent features or recommended alternatives for Linux users, or explicitly state if such features are not available.
  • Ensure that advanced options or tips are presented for both platforms, or note platform-specific limitations to maintain transparency and parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/volume-delete.md ...blob/main/articles/azure-netapp-files/volume-delete.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions and omits any command-line examples. There is no mention of PowerShell or Windows-specific tools, but the lack of CLI examples (such as Azure CLI or Bash) means Linux users do not have parity. The instructions do not reference Linux-specific tools or workflows, nor do they provide cross-platform command-line guidance.
Recommendations
  • Add Azure CLI examples for deleting a volume, including sample commands that work on Linux, macOS, and Windows.
  • If applicable, include PowerShell examples, but ensure they are presented alongside Azure CLI/Bash examples to maintain parity.
  • Explicitly mention that the deletion can be performed via CLI and provide links to relevant CLI documentation.
  • Clarify any OS-specific steps for unmounting the volume (e.g., provide both Linux and Windows unmount instructions).
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/whats-new.md ...ocs/blob/main/articles/azure-netapp-files/whats-new.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation for Azure NetApp Files generally maintains cross-platform parity, frequently referencing both Linux (NFS) and Windows (SMB) use cases. However, there is a notable emphasis on Windows-centric features and terminology, particularly around SMB, Active Directory, and Windows client behaviors. Windows tools and patterns (e.g., Windows File Explorer, NTFS, Windows client, FSLogix, Citrix App Layering, SQL Server on Windows) are mentioned more often and sometimes before their Linux/NFS equivalents. Some features are described with a Windows-first perspective, such as access-based enumeration and non-browsable shares, where the behavior is explained in terms of Windows client experience. There are also several features that are only relevant to Windows/SMB environments, with less emphasis on Linux/NFS-only enhancements.
Recommendations
  • Where features are described in terms of Windows client experience (e.g., access-based enumeration, non-browsable shares), add equivalent explanations for Linux/NFS clients or clarify if the feature is not applicable.
  • When listing protocol support or describing new features, present NFS (Linux) and SMB (Windows) use cases in parallel, rather than defaulting to Windows-first explanations.
  • For features that are SMB/Windows-specific, explicitly state their relevance and, where possible, provide links or references to comparable Linux/NFS features or best practices.
  • Ensure that examples, troubleshooting steps, and user scenarios include both Linux and Windows perspectives where applicable.
  • Highlight Linux/NFS-only enhancements with equal prominence as Windows/SMB features to reinforce cross-platform parity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/volume-hard-quota-guidelines.md ...les/azure-netapp-files/volume-hard-quota-guidelines.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias, particularly in the ordering and depth of examples. In the VM-level monitoring section, Windows examples (Explorer, dir command, screenshots) are presented first and in greater detail, followed by Linux examples. In the CLI/PowerShell section, PowerShell screenshots and references are prominent, with no explicit Linux shell (bash) command-line examples or screenshots, even though Azure CLI is cross-platform. There are no exclusive Windows-only tools, but the documentation tends to prioritize Windows workflows and visuals.
Recommendations
  • Alternate the order of Windows and Linux examples in sections to avoid always presenting Windows first.
  • Provide equivalent bash/Azure CLI command-line examples and screenshots alongside PowerShell examples, especially in the CLI/PowerShell section.
  • Include more detailed Linux workflow descriptions and visuals where possible (e.g., showing Linux file manager properties for mapped drives, if applicable).
  • Explicitly state that Azure CLI commands work identically on Linux, macOS, and Windows, and show examples in a Linux terminal.
  • Where possible, balance the number of screenshots and depth of explanation between Windows and Linux sections.
GitHub Create Pull Request
Azure Netapp Files Configure customer-managed keys for Azure NetApp Files volume encryption .../azure-netapp-files/configure-customer-managed-keys.md
Low Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring customer-managed keys for Azure NetApp Files. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as the tabbed instructions), PowerShell is presented before or alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell. There are no Linux/macOS-specific shell examples (e.g., Bash), but the CLI examples are cross-platform. No Windows-only tools or patterns are mentioned, and the instructions are generally platform-neutral outside of the PowerShell sections.
Recommendations
  • Ensure Azure CLI examples are presented first in tabbed sections, as CLI is cross-platform and more widely used outside Windows.
  • Clearly indicate that PowerShell is optional and primarily for Windows users.
  • Consider adding Bash script snippets for common tasks, especially where CLI commands are used in pipelines or with environment variables.
  • Add a brief note clarifying that all CLI examples work on Linux/macOS and Windows, while PowerShell is Windows-centric.
GitHub Create Pull Request
Azure Netapp Files Troubleshoot volume errors for Azure NetApp Files ...in/articles/azure-netapp-files/troubleshoot-volumes.md
Low Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation covers troubleshooting for Azure NetApp Files volumes across SMB, NFS, and dual-protocol scenarios. While it is not Windows-only, there is a mild Windows bias: in sections involving Kerberos and NFSv4.1, PowerShell commands (Set-ADComputer) are provided for configuring Kerberos encryption types, but equivalent Linux/UNIX LDAP/NFS administrative commands are not shown. Additionally, Active Directory (AD DS) and Microsoft Entra Domain Services are discussed before any mention of Linux-based directory services or alternatives, and some troubleshooting steps reference Windows tools (Active Directory Users and Computers) without Linux equivalents.
Recommendations
  • Provide Linux/UNIX command-line equivalents for AD/LDAP operations where PowerShell or Windows UI steps are shown (e.g., using ldapmodify, samba-tool, or relevant utilities).
  • Include troubleshooting steps for common Linux-based directory services (such as OpenLDAP or Samba AD) where applicable, or clarify that only Microsoft AD DS is supported.
  • When referencing tools like 'Active Directory Users and Computers', mention Linux alternatives or note that these steps require access to a Windows system.
  • Where PowerShell commands are shown, add equivalent steps for Linux administrators (e.g., using Kerberos or LDAP tools).
  • Ensure that examples for mounting, troubleshooting, and configuring NFS/LDAP include both Windows and Linux client perspectives.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files for Azure Government ...b/main/articles/azure-netapp-files/azure-government.md
Low Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government using the Azure portal, Azure CLI, REST API, and PowerShell. While the CLI and REST API sections are cross-platform, the PowerShell section is detailed and prominent, and PowerShell is a Windows-centric tool. The PowerShell access section is more extensive than the CLI section, and PowerShell is mentioned in the 'Next steps' links before any Linux-native automation options. There are no Linux/macOS-specific examples or mentions of Bash, shell scripting, or automation tools commonly used on those platforms.
Recommendations
  • Add Bash or shell script examples for connecting to Azure Government using Azure CLI, demonstrating automation workflows on Linux/macOS.
  • Include a note clarifying that Azure CLI is fully supported on Linux/macOS and provide links to installation instructions for those platforms.
  • Balance the PowerShell section with equivalent detail for CLI usage, including example scripts for common NetApp Files tasks.
  • Mention cross-platform automation options (e.g., Python SDK, Terraform) if relevant for Azure NetApp Files.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files for Azure Government ...b/main/articles/azure-netapp-files/azure-government.md
Low Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government using the Azure portal, Azure CLI, REST API, and PowerShell. While the Azure CLI and REST API sections are platform-neutral, the PowerShell section is detailed and includes multiple connection examples, and PowerShell is a Windows-centric tool (though available on Linux/macOS). The PowerShell section appears after CLI and REST API, but the 'Next steps' section highlights PowerShell-specific REST API usage before mentioning general REST API documentation. There are no Linux/macOS-specific examples or mentions of tools like Bash, nor guidance for Linux users beyond CLI/REST.
Recommendations
  • Add explicit Bash or shell examples for connecting to Azure Government using Azure CLI on Linux/macOS.
  • Clarify that PowerShell Core is cross-platform and provide installation guidance for Linux/macOS users.
  • Ensure parity in example depth between PowerShell and CLI sections (e.g., show equivalent resource management commands in both).
  • In 'Next steps', list platform-neutral REST API documentation before PowerShell-specific usage.
GitHub Create Pull Request
Azure Netapp Files Create a capacity pool for Elastic zone-redundant service in Azure NetApp Files ...icles/azure-netapp-files/elastic-capacity-pool-task.md
Low Priority View Details →
Scanned: 2026-02-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page mentions PowerShell and the Az.NetAppFiles module explicitly in the 'Before you begin' section, including instructions and a link for updating the module. While Azure CLI and REST API are also referenced, PowerShell is called out separately and before REST API, with no equivalent Linux/macOS shell guidance (e.g., Bash, zsh). There are no command-line examples for any platform, but the explicit PowerShell mention may create a perception of Windows-first bias.
Recommendations
  • Add explicit instructions or links for updating Azure CLI for Linux/macOS users, similar to the PowerShell guidance.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide parity in setup instructions for each.
  • If relevant, include example commands for both Azure CLI (Bash/zsh) and PowerShell, or clarify that all steps can be performed in the Azure Portal regardless of OS.
  • Consider reordering the 'Before you begin' section to list Azure CLI before PowerShell, or group them together as cross-platform options.
GitHub Create Pull Request
Azure Netapp Files Azure NetApp Files for Azure Government ...b/main/articles/azure-netapp-files/azure-government.md
Low Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government via the portal, Azure CLI, REST API, and PowerShell. While CLI and REST API methods are platform-agnostic, the PowerShell section is detailed and includes multiple connection types and commands. PowerShell instructions are given their own section and are more extensive than for other platforms. The order of sections places PowerShell after CLI and REST API, but the PowerShell section is notably more detailed. There are no Linux/macOS-specific examples or mentions of Bash, Cloud Shell, or other non-Windows tools. However, the CLI instructions are sufficient for Linux/macOS users, and the feature itself is not Windows-specific.
Recommendations
  • Add explicit mention that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • Include Bash or shell script examples for connecting via CLI, if applicable.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide links to cross-platform PowerShell installation guides.
  • Consider adding a note or section for Linux/macOS users to highlight parity and any platform-specific considerations.
GitHub Create Pull Request
Azure Netapp Files Configure customer-managed keys for Azure NetApp Files volume encryption .../azure-netapp-files/configure-customer-managed-keys.md
Low Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring customer-managed keys for Azure NetApp Files. However, PowerShell examples are given equal prominence as CLI, and in some sections, PowerShell is referenced before CLI. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. The CLI examples are cross-platform, but the presence and prominence of PowerShell may signal a slight Windows bias.
Recommendations
  • Ensure Azure CLI examples are shown first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples where relevant, especially for scripting tasks (e.g., using variables, piping outputs).
  • Clarify that PowerShell examples are optional and primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Consider adding a short note at the top of the examples section indicating CLI is cross-platform and PowerShell is Windows-centric.
  • Review screenshots and UI references to ensure they do not assume a Windows environment (e.g., avoid showing Windows-only UI elements if not necessary).
GitHub Create Pull Request
← Previous Page 34 of 36 Next →