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 876-896 of 896 flagged pages
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides step-by-step instructions for configuring customer-managed keys for Azure NetApp Files using the Azure Portal, Azure CLI, and Azure PowerShell. The Azure PowerShell section is presented as a first-class method alongside Azure CLI, and PowerShell-specific commands are detailed extensively. There is a subtle Windows bias in the inclusion and prominence of PowerShell examples, which are primarily relevant for Windows users. However, the Azure CLI examples are cross-platform and appear before PowerShell, and there are no explicit references to Windows-only tools or patterns. No Linux/macOS-specific examples or troubleshooting are provided, but Linux users can complete all tasks using the CLI.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows and provide guidance for Linux/macOS users on installing and using Azure PowerShell if needed.
  • Add explicit notes or links for Linux/macOS users regarding Azure CLI installation and usage.
  • Consider including bash shell scripting examples or tips for Linux/macOS users where relevant.
  • Ensure troubleshooting and error messages sections mention cross-platform considerations if any exist.
GitHub Create Pull Request
Azure Netapp Files Configure network features for an Azure NetApp Files volume ...icles/azure-netapp-files/configure-network-features.md
Low Priority View Details →
Scanned: 2026-01-13 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 PowerShell examples for most operations, but PowerShell (a Windows-centric tool) is often featured prominently, including for feature registration and volume management. In some sections, PowerShell commands are shown before or alongside CLI, and feature registration is first described using PowerShell. There are no Linux/macOS-specific shell examples (e.g., Bash), and screenshots and instructions focus on the Azure Portal, which is cross-platform but may be more familiar to Windows users. REST API and Terraform sections are platform-neutral.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell, as CLI is cross-platform.
  • Add explicit Bash shell examples for Linux/macOS users where appropriate.
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows.
  • Where PowerShell is used, note that Azure PowerShell is available on Linux/macOS, or link to installation instructions.
  • Consider adding a table or section summarizing command parity across platforms.
GitHub Create Pull Request
Azure Netapp Files Manage cross-zone-region replication for Azure NetApp Files ...etapp-files/cross-zone-region-replication-configure.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by presenting Azure PowerShell commands first for feature registration, with Azure CLI (cross-platform) only mentioned secondarily. The CLI commands are referenced but not shown as explicit examples. No Linux/macOS-specific tools or instructions are provided, and the workflow assumes familiarity with PowerShell and Windows-centric patterns.
Recommendations
  • Provide explicit Azure CLI command examples alongside PowerShell, not just as references.
  • Ensure that CLI instructions are presented with equal prominence and detail as PowerShell examples.
  • Clarify that all steps can be performed on Linux/macOS using Azure CLI.
  • Consider showing CLI examples first or side-by-side with PowerShell to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Azure Netapp Files Configure cross-tenant customer-managed keys for Azure NetApp Files volume encryption ...ure-netapp-files/customer-managed-keys-cross-tenant.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides step-by-step instructions for configuring cross-tenant customer-managed keys for Azure NetApp Files, but all examples and tool references are platform-neutral (Azure CLI and REST API) and GUI-based via the Azure Portal. However, there is a subtle Windows bias in the ordering and presentation: GUI navigation steps assume familiarity with the Azure Portal, which is most commonly used on Windows, and there are no explicit Linux/macOS shell examples or notes about cross-platform differences. All CLI instructions use Azure CLI, which is cross-platform, but there are no Linux-specific considerations or troubleshooting notes. No PowerShell-specific commands or Windows-only tools are mentioned.
Recommendations
  • Add explicit notes confirming that all CLI commands work identically on Linux/macOS and provide troubleshooting steps for common cross-platform issues (e.g., authentication, environment variables).
  • Include screenshots or navigation tips for Azure Portal on macOS/Linux browsers, or mention that the portal is fully web-based and OS-agnostic.
  • If any step requires local file manipulation or scripting, provide bash/zsh examples alongside Azure CLI.
  • Clarify that Azure CLI is available and supported on Linux/macOS, and link to installation instructions for those platforms.
GitHub Create Pull Request
Azure Netapp Files Understand default and individual user and group quotas for Azure NetApp Files volumes ...s/default-individual-user-group-quotas-introduction.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows client instructions before Linux, and references Windows-specific concepts (such as SIDs and Windows Explorer) before their Linux equivalents (UIDs, quota command). While both platforms are covered, Windows examples and terminology are introduced first, and Windows tools are mentioned explicitly, indicating a mild Windows bias.
Recommendations
  • Present Linux and Windows client instructions in parallel or alternate their order to avoid implicit prioritization.
  • When describing individual user quotas, mention UNIX UID and Linux usage before or alongside Windows SID and tools.
  • Include macOS-specific instructions or clarify if Linux instructions apply to macOS clients.
  • Where possible, use neutral terminology (e.g., 'file manager' instead of 'Windows Explorer') or provide equivalent Linux/macOS tools.
  • Ensure that all examples and screenshots are balanced between platforms.
GitHub Create Pull Request
Azure Netapp Files Integration FAQs for Azure NetApp Files ...ob/main/articles/azure-netapp-files/faq-integration.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page displays a subtle Windows bias: when discussing mounting Azure NetApp Files volumes on AVS VMs, Windows is mentioned first and receives specific mention for SMB shares, while Linux is only referenced generically for NFS mounts. There are no Linux-specific examples or detailed instructions, and SMB usage is described only for Windows VMs, omitting any mention of Linux SMB clients.
Recommendations
  • Provide explicit Linux examples for mounting NFS and SMB volumes, including relevant commands and tools (e.g., mount, cifs-utils).
  • Mention Linux SMB client compatibility and any caveats or configuration steps.
  • Alternate the order of Windows and Linux references, or present them together to avoid perceived prioritization.
  • Include links to Linux-specific documentation or guides where appropriate.
GitHub Create Pull Request
Azure Netapp Files Understand the allow local NFS users with LDAP option with LDAP in Azure NetApp Files ...s/lightweight-directory-access-protocol-local-users.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by focusing on NTFS security style volumes and Windows user mapping in the dual protocol section, and by referencing Active Directory and Windows user/group concepts before or instead of Linux equivalents. There are no explicit Linux/macOS command examples, and the discussion of user mapping is centered around Windows authentication scenarios.
Recommendations
  • Include explicit examples of Linux/macOS user and group mapping, such as references to /etc/passwd, /etc/group, and common Linux authentication flows.
  • Provide parity in explanations for both UNIX and Windows environments, ensuring that Linux/macOS scenarios are described with equal detail.
  • Add troubleshooting steps or configuration examples for Linux NFS clients (e.g., idmapd.conf, nsswitch.conf) alongside Windows/Active Directory references.
  • Clarify the impact of the 'Allow local NFS users with LDAP' option for Linux/macOS-only environments, not just dual-protocol setups.
GitHub Create Pull Request
Azure Netapp Files Understand NAS file permissions in Azure NetApp Files ...zure-netapp-files/network-attached-file-permissions.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by describing Windows SMB inheritance controls first, including a screenshot of the Windows interface, while Linux/NFS inheritance is described in text only and with less detail. Windows tools (advanced permission view) are mentioned explicitly, whereas Linux/NFS equivalents (umask, setgid, ACLs) are referenced generically and without visual aids or command examples.
Recommendations
  • Add Linux/NFS-specific examples, such as command-line usage of setgid, umask, and setfacl for inheritance.
  • Include screenshots or terminal output demonstrating permission inheritance management on Linux/NFS systems.
  • Present Windows and Linux/NFS approaches in parallel, giving equal detail and prominence to both.
  • Reference relevant Linux tools (e.g., getfacl, setfacl) explicitly, similar to how Windows tools are mentioned.
GitHub Create Pull Request
Azure Netapp Files Understand NFSv4.x access control lists in Azure NetApp Files ...rticles/azure-netapp-files/nfs-access-control-lists.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias, primarily in its introductory sections. It references Windows ACLs and NTFS permissions before Linux equivalents, and links to Windows documentation for ACL concepts. However, all practical examples, commands, and configuration steps use Linux tools (nfs4_getfacl, nfs4_setfacl, chmod, chown), and there are no PowerShell or Windows command-line examples. The page is fully actionable for Linux/macOS users.
Recommendations
  • In the introduction, mention Linux ACLs and their documentation alongside Windows ACLs to provide parity.
  • Link to Linux-specific ACL documentation (e.g., man pages for nfs4_acl, getfacl, setfacl) when discussing ACL concepts.
  • If referencing SMB/NTFS permissions, also reference POSIX ACLs and their similarities/differences.
  • Consider reordering the introduction to present Linux/NFS concepts first, or in parallel with Windows concepts.
  • Add a brief note clarifying that all examples use Linux tools and that Windows users should use SMB/NTFS ACL management.
GitHub Create Pull Request
Azure Netapp Files Azure VMware Solution datastore performance considerations for Azure NetApp Files ...p-files/performance-azure-vmware-solution-datastore.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows tools and concepts (NTFS, volume shadow copies, MSSQL Filegroups) are mentioned alongside Linux equivalents, but Windows examples and references (e.g., 'Creating striped volumes in Windows Server') are listed before Linux ones in the 'Next steps' section. The monitoring section references vCenter Server (cross-platform) and Azure API/Console, but does not provide Linux-specific CLI or scripting examples. The main test environment uses Ubuntu Linux, and Linux file systems (XFS, LVM) are discussed in detail, but Windows parity is not fully addressed in performance testing or configuration examples.
Recommendations
  • Provide explicit Linux CLI examples for monitoring and managing datastores (e.g., using Azure CLI, REST API, or Linux tools).
  • Ensure Linux-related links (such as 'Linux NFS mount options best practices') appear before or alongside Windows links in 'Next steps'.
  • Include performance testing results or configuration examples for Windows guest VMs, not just Ubuntu.
  • Mention Linux backup/snapshot tools (e.g., LVM snapshots, xfs_freeze) with equal prominence as Windows tools.
  • Clarify any differences in striping, snapshot, or backup operations between Windows and Linux guests.
GitHub Create Pull Request
Azure Netapp Files How Azure NetApp Files snapshots work .../articles/azure-netapp-files/snapshots-introduction.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation lists Windows-centric tools (PowerShell) alongside cross-platform options (Azure CLI, REST API) for snapshot management, but PowerShell is explicitly mentioned and linked before Linux-native alternatives. There are no Linux-specific examples, and Windows tooling is referenced as a primary method for manual and automated snapshot operations. However, the overall guidance is platform-neutral and does not prevent Linux/macOS users from completing tasks.
Recommendations
  • Add explicit Linux/macOS command-line examples using Azure CLI for common snapshot operations.
  • Clarify that Azure CLI and REST API are fully supported on Linux/macOS and provide sample commands.
  • When listing tools, alternate the order or group cross-platform tools (CLI, REST API) before platform-specific ones (PowerShell).
  • Include a note or section on managing snapshots from Linux/macOS environments, possibly with sample scripts.
  • Avoid referencing PowerShell as a default unless specifically targeting Windows administrators.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates mild Windows bias, primarily in the order of examples and the use of PowerShell for Active Directory operations. Windows/AD-centric troubleshooting steps and terminology are presented first and most prominently, with Linux/NFS guidance appearing later. Some critical Kerberos/NFS troubleshooting steps do include Linux-specific commands and service names, but Windows tools (e.g., PowerShell) are referenced for AD configuration without Linux alternatives.
Recommendations
  • When providing example commands for AD configuration (e.g., setting Kerberos encryption type), include equivalent Linux LDAP/AD tooling (such as ldapmodify or samba-tool) alongside PowerShell.
  • Where troubleshooting steps reference Windows/AD concepts (e.g., OU paths, group membership), clarify how Linux-based environments or Samba AD might differ, and provide links or examples.
  • Ensure that Linux/NFS troubleshooting steps are presented with equal prominence and detail as Windows/SMB steps, possibly by grouping by platform or protocol.
  • For every PowerShell example, provide a Linux shell/CLI equivalent if possible.
  • Explicitly mention macOS where relevant, especially for NFS client troubleshooting.
GitHub Create Pull Request
Azure Netapp Files What changing to volume hard quota means for your Azure NetApp Files service ...les/azure-netapp-files/volume-hard-quota-guidelines.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. In the VM-level monitoring section, Windows examples (Explorer, dir command) are presented before Linux (df command). CLI management screenshots and examples predominantly use Azure PowerShell, with no explicit Bash/Azure CLI terminal examples shown. The portal instructions use Windows-centric UI language (right-click, context menu), and there is a general tendency to mention Windows tools and patterns before Linux equivalents.
Recommendations
  • Present Linux examples (e.g., df, Bash CLI) alongside or before Windows examples in monitoring sections.
  • Include screenshots and command-line examples using Bash/Azure CLI, not just PowerShell.
  • Clarify that Azure CLI commands can be run from Bash on Linux/macOS, and provide sample commands in Bash syntax.
  • Balance portal instructions with references to cross-platform UI conventions (e.g., 'context menu' instead of 'right-click').
  • Explicitly mention macOS where Linux is referenced, if applicable.
GitHub Create Pull Request
Azure Netapp Files What's new in Azure NetApp Files ...ocs/blob/main/articles/azure-netapp-files/whats-new.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure NetApp Files 'What's New' is generally cross-platform and covers both Windows and Linux features. However, there is a mild Windows bias: Windows-specific features (such as SMB, Active Directory, Windows Server domain controllers, and Windows client behaviors) are mentioned frequently and sometimes described before their Linux/NFS equivalents. Windows-centric terminology (e.g., Windows File Explorer, NTFS, SMB, Active Directory) is used in several feature descriptions, and some features (like Access-based Enumeration, Non-browsable shares, SMB Continuous Availability) are described primarily in terms of their Windows client impact, with Linux/NFS features discussed separately or later.
Recommendations
  • When describing features that apply to both Windows and Linux, present both perspectives equally, and avoid describing Windows workflows first unless there is a technical reason.
  • For features that have both SMB (Windows) and NFS (Linux) applicability, include explicit Linux/NFS examples and terminology alongside Windows/SMB examples.
  • Where Windows tools or patterns (e.g., Windows File Explorer, NTFS) are mentioned, also mention equivalent Linux tools or behaviors (e.g., Linux file browsers, POSIX permissions) if relevant.
  • Ensure that Linux/NFS features are given equal prominence and detail in feature descriptions, especially for dual-protocol or cross-platform capabilities.
  • Add cross-platform usage notes or examples where possible, especially for features like quotas, snapshots, and directory services.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/includes/oracle-dnfs.md ...in/articles/azure-netapp-files/includes/oracle-dnfs.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but it also fails to mention or provide guidance for Linux environments, which are common for Oracle dNFS deployments. There is no explicit Windows bias, but the absence of Linux-specific context or examples may leave Linux administrators underserved.
Recommendations
  • Include explicit references to both Windows and Linux environments where relevant, especially since Oracle dNFS is frequently deployed on Linux.
  • Provide platform-specific patching guidelines or clarify if the linked guidelines apply equally to both Windows and Linux.
  • Add examples or notes for Linux administrators to ensure parity and clarity.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/test-disaster-recovery.md .../articles/azure-netapp-files/test-disaster-recovery.md
Low Priority View Details →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides high-level steps for disaster recovery testing with Azure NetApp Files but does not include any platform-specific examples or commands. However, it omits explicit examples or guidance for both Windows and Linux environments, with a slight implicit bias due to the lack of Linux-specific mounting or operational instructions, which are often necessary for cross-platform parity.
Recommendations
  • Include explicit examples for mounting/unmounting Azure NetApp Files volumes on both Windows (using SMB/NFS with PowerShell or GUI) and Linux (using NFS with mount commands).
  • Reference both Windows and Linux tools or commands where applicable, especially in steps involving VM preparation, volume mounting, and application testing.
  • Provide links to platform-specific documentation for mounting Azure NetApp Files volumes on Windows and Linux.
  • Clarify that the workflow applies to both Windows and Linux VMs, and highlight any platform-specific considerations.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-billing-tags.md ...ain/articles/azure-netapp-files/manage-billing-tags.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only portal-based (GUI) instructions for managing Azure NetApp Files billing tags and downloading cost data. There are no command-line examples or references for either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI, Bash). However, the lack of any CLI examples means Linux users are not shown how to perform these tasks from the command line, which is a common workflow for Linux environments.
Recommendations
  • Add Azure CLI examples for adding, editing, and viewing tags on capacity pools, as well as for downloading cost data, to ensure Linux users have clear, platform-agnostic instructions.
  • If PowerShell examples are added in the future, ensure Azure CLI (cross-platform) equivalents are provided alongside.
  • Explicitly mention that these tasks can be performed via both the Azure Portal and command-line tools, and provide links to relevant CLI documentation.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md ...ure-netapp-files/azure-netapp-files-delegate-subnet.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides only Azure Portal (GUI) instructions for delegating a subnet to Azure NetApp Files and does not include any command-line examples. There is no explicit Windows bias (such as PowerShell or Windows tool references), but there is a lack of parity for users who prefer or require CLI-based workflows, which are common in Linux environments.
Recommendations
  • Add Azure CLI examples for subnet delegation, as Azure CLI is cross-platform and widely used on Linux.
  • If relevant, include Azure PowerShell examples as well, but ensure Azure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that the steps can be performed via CLI or automation tools, and provide links or references to relevant documentation for both Linux and Windows users.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md ...ure-netapp-files/azure-netapp-files-delegate-subnet.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides only Azure Portal (GUI) instructions for subnet delegation and does not include any command-line examples. There is no mention of Windows-specific tools, but the absence of CLI (such as Azure CLI or PowerShell) examples means Linux users do not have parity, as they often rely on CLI tools for automation and scripting.
Recommendations
  • Add Azure CLI examples for creating and delegating a subnet to Azure NetApp Files, as Azure CLI is cross-platform and widely used on Linux.
  • If including PowerShell examples, ensure they are presented alongside Azure CLI examples, not before them.
  • Explicitly mention that the steps can be performed using either the Azure Portal, Azure CLI, or PowerShell, and provide links or references to relevant CLI documentation.
  • Consider including sample scripts for both Azure CLI and PowerShell to cover both Linux and Windows users.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/monitor-azure-netapp-files.md ...icles/azure-netapp-files/monitor-azure-netapp-files.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally avoids overt Windows bias, providing platform-neutral descriptions. However, in the 'Capacity utilization monitoring' section, it states: 'You can check the used and available capacity of a volume by using Windows or Linux clients.' The order of mention ('Windows or Linux') subtly prioritizes Windows, which is a minor instance of 'windows_first' bias. No explicit PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples are present.
Recommendations
  • When listing platforms, alternate or alphabetize (e.g., 'Linux or Windows clients') to avoid implicit prioritization.
  • Where possible, provide example commands for both Windows (e.g., PowerShell) and Linux (e.g., Bash) to ensure parity.
  • Explicitly mention cross-platform tools or interfaces (such as Azure CLI) and provide usage examples for both environments.
  • Review other documentation pages linked from this one to ensure that any referenced guides do not exhibit stronger Windows bias.
GitHub Create Pull Request
Azure Netapp Files https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/manage-billing-tags.md ...ain/articles/azure-netapp-files/manage-billing-tags.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only portal-based (GUI) instructions and does not include any command-line examples for managing tags or billing data. There are no examples using PowerShell, Azure CLI, or other tools. However, the absence of Azure CLI (cross-platform) or Linux-specific instructions means Linux users do not have parity with potential Windows users who might expect PowerShell or CLI options.
Recommendations
  • Add Azure CLI examples for adding, editing, and viewing tags on capacity pools, as Azure CLI is cross-platform and widely used on Linux.
  • Include instructions for downloading and processing billing/tag data using command-line tools (e.g., az costmanagement, curl, jq) suitable for Linux environments.
  • If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided alongside.
  • Explicitly mention that all portal-based steps are platform-agnostic, but provide links or references to CLI documentation for users who prefer or require command-line automation.
GitHub Create Pull Request
← Previous Page 36 of 36 Next →