Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 426-450 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-aad-auth-qs.md
...ure-government/documentation-government-aad-auth-qs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows-centric tools (Visual Studio 2019), omitting any Linux or cross-platform development environments, and not providing Linux-specific instructions or examples. All configuration and code examples assume a Windows/ASP.NET Core workflow, with no mention of how to perform equivalent steps on Linux or with non-Windows tooling.
Recommendations
- Include instructions for setting up and configuring the application using cross-platform tools such as Visual Studio Code, JetBrains Rider, or command-line interfaces available on Linux.
- Provide Linux-specific guidance for editing configuration files, running the application, and managing dependencies (e.g., using dotnet CLI on Linux).
- Add examples or notes for deploying and testing the application locally on Linux, including how to set up the development environment and run the app.
- Avoid assuming the use of Visual Studio 2019; instead, refer to 'your preferred IDE or editor' and provide steps for both Windows and Linux users.
- Explicitly mention that the instructions are applicable to both Windows and Linux, or provide separate sections for each platform where workflows differ.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-image-gallery.md
...e-government/documentation-government-image-gallery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for listing images, referencing connecting via PowerShell, and listing Windows VM creation guides before Linux. There are no CLI or Bash/Linux-native examples for obtaining images, and Windows tools and workflows are prioritized.
Recommendations
- Add Azure CLI and Bash examples for listing available VM images, alongside PowerShell.
- Include instructions for connecting to Azure Government using the Azure CLI, not just PowerShell.
- Balance the 'Next steps' section by listing Linux VM creation guides alongside or before Windows guides, and include PowerShell, CLI, and portal options for both OS types.
- Avoid referencing only Windows tools (e.g., PowerShell) when cross-platform tools (e.g., Azure CLI) are available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-developer-guide.md
...government/documentation-government-developer-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing 'Connect with PowerShell' before 'Connect with CLI' in the Quickstarts section, and by including 'Connect with Visual Studio' (a Windows-centric tool) without mentioning cross-platform alternatives like VS Code. The prominence of PowerShell and Visual Studio, both traditionally Windows-focused, suggests a prioritization of Windows tools and workflows. There are no explicit Linux examples or references to Linux-specific tools, and the CLI (which is cross-platform) is mentioned after PowerShell.
Recommendations
- Reorder the Quickstarts section to list cross-platform tools (such as Azure CLI) before or alongside PowerShell.
- Explicitly mention and provide links to cross-platform tools like Visual Studio Code, and clarify their support for Azure Government development.
- Add Linux-specific guidance or examples, such as connecting to Azure Government using Bash or shell scripts.
- Ensure parity in documentation by providing equivalent instructions for both Windows and Linux environments wherever possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-manage-oms.md
...zure-government/documentation-government-manage-oms.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows examples and tools, such as System Center Operations Manager and System Center Endpoint Protection, and by providing more detailed or visual examples for Windows scenarios. Linux is mentioned, but often as a secondary consideration, and there are fewer Linux-specific examples or screenshots. Some sections, such as antimalware assessment, focus almost exclusively on Windows-native solutions. There is also a lack of Linux command-line or automation examples, and Windows onboarding instructions are referenced first.
Recommendations
- Ensure Linux onboarding instructions and links are presented alongside or before Windows instructions, not after.
- Include Linux-specific screenshots and examples (e.g., onboarding, monitoring, and threat detection on Linux VMs).
- Highlight Linux-compatible security tools and solutions, not just Windows-native ones like System Center Endpoint Protection.
- Provide Linux command-line (bash, shell script) and automation examples, not just references to Windows tools or portals.
- Balance the use of Windows and Linux terminology and visuals throughout the documentation.
- Explicitly mention any feature parity or differences between Windows and Linux support in Azure Monitor logs.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-plan-identity.md
...e-government/documentation-government-plan-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-centric identity solutions such as Active Directory Domain Services (AD DS) and Active Directory Federation Services (ADFS), referencing Windows Server documentation, and omitting any mention of Linux-based identity solutions or cross-platform alternatives. All examples and deployment guidance assume a Windows environment, with no consideration for Linux or open-source identity management tools. Even in sections discussing authentication protocols and infrastructure, only Windows tools and patterns are described.
Recommendations
- Include guidance or references for integrating Linux-based identity solutions (e.g., using LDAP, FreeIPA, or Samba as alternatives to AD DS) in Azure Government environments.
- Provide examples or documentation links for managing Azure Government identity from Linux systems, such as using Azure CLI, which is cross-platform, or scripting with Bash.
- Mention cross-platform authentication protocols and how they can be implemented in both Windows and Linux environments.
- When discussing domain controllers and federation services, acknowledge and provide resources for organizations that use non-Windows infrastructure.
- Balance references to Windows tools (like PowerShell, AD DS, ADFS) with equivalent Linux/open-source tools or at least note their absence and possible integration points.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-quickstarts-vm.md
...-government/documentation-government-quickstarts-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using a Windows-based VM image ('Data Science Virtual Machine - Windows 2016 CSP') as the example, with no mention of Linux alternatives. The instructions focus on connecting via RDP (a Windows protocol) and do not provide any Linux VM creation or SSH connection examples. There is no mention of Linux tools, patterns, or parity in the workflow.
Recommendations
- Include examples for creating Linux-based virtual machines (e.g., Ubuntu, CentOS) alongside the Windows example.
- Demonstrate how to connect to Linux VMs using SSH, and provide relevant instructions for generating SSH keys and connecting from different platforms.
- Mention both RDP (for Windows) and SSH (for Linux) as connection options, and clarify which applies to which OS.
- Where possible, provide CLI or script-based examples (e.g., Azure CLI, Bash) that are cross-platform, not just portal-based workflows.
- Highlight the availability of both Windows and Linux VM images in the Azure Government marketplace.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-government/documentation-government-plan-security.md
...e-government/documentation-government-plan-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows a subtle Windows bias. In the encryption in transit section, Windows, Windows Server, and Azure File shares using SMB 3.0 are mentioned explicitly, while Linux equivalents or cross-platform alternatives are not discussed. There are no Linux-specific examples or tools mentioned for encryption, file sharing, or monitoring. Additionally, the referenced blog posts for Microsoft Defender for Cloud include several Windows/Powershell-specific attack detection scenarios, with only two Linux-specific examples, and these Linux examples appear later in the list.
Recommendations
- When mentioning SMB 3.0 for Windows/Windows Server, also mention NFS or other Linux-compatible protocols and how encryption is handled for Linux VMs and file shares.
- Provide explicit Linux examples or guidance for encryption at rest/in transit, such as using dm-crypt, LUKS, or OpenSSL for client-side encryption.
- Include Linux command-line or scripting examples (e.g., bash, shell scripts) alongside or before Windows/Powershell examples where relevant.
- Ensure that blog post references and security scenarios are balanced between Windows and Linux, and consider listing Linux examples earlier or equally.
- Highlight Azure features/tools that are cross-platform or provide parity for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-dev-ops.md
...lob/main//articles/devtest-labs/devtest-lab-dev-ops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing PowerShell scripts and Azure CLI as primary automation methods, without mentioning Bash or Linux shell scripting. There are no explicit Linux examples or references to Linux-specific tools or workflows. The order of mentioning 'PowerShell scripts' before 'Azure CLI' and the absence of Linux/Bash examples suggest a Windows-first approach.
Recommendations
- Explicitly mention Bash or Linux shell scripting alongside PowerShell when discussing automation options.
- Provide examples or references for both Windows and Linux environments, especially in sections discussing scripting and automation.
- Ensure that any references to tools or scripting languages are balanced, e.g., 'executing PowerShell or Bash scripts, or using Azure CLI'.
- Add a note or example for integrating DevTest Labs in CI/CD pipelines from a Linux agent or using Linux-native tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-large-instances/onboarding-requirements.md
...icles/azure-large-instances/onboarding-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell/Azure CLI (Windows-style) commands for onboarding and configuration tasks, without offering equivalent Linux shell or cross-platform CLI examples. The instructions for enabling ExpressRoute Fast Path and related networking steps are written entirely in PowerShell, and there is no mention of Bash, Linux CLI, or cross-platform scripting. Additionally, the guidance to 'install the latest version of the Azure Resource Manager PowerShell cmdlets' is presented as a prerequisite, reinforcing a Windows-centric approach.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell commands, ensuring Linux users can follow the onboarding steps without needing Windows or PowerShell.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant cross-platform documentation.
- When referencing tools or prerequisites (such as PowerShell cmdlets), also reference the Azure CLI and its installation instructions for Linux.
- Where possible, use cross-platform scripting (e.g., az CLI) as the primary example, or present both PowerShell and Bash/CLI examples side by side.
- Clarify in each section whether the instructions are OS-agnostic or if there are any platform-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/azure-maps-authentication.md
...main//articles/azure-maps/azure-maps-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples for retrieving the Azure Maps Client ID using PowerShell and Azure CLI, but the PowerShell example is presented first and in more detail. There is no explicit Linux/bash example for retrieving the Client ID, nor is there mention of Linux-specific tools or workflows. The use of PowerShell as the primary scripting example and the ordering of examples may suggest a Windows-centric bias.
Recommendations
- Provide bash or shell script examples for Linux/macOS users alongside PowerShell and Azure CLI examples.
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used in Linux environments.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide example outputs for each where relevant.
- Where PowerShell is used, clarify that it is available cross-platform, or provide equivalent bash commands if functionality differs.
- Review the documentation for other subtle Windows-first language or assumptions, and ensure parity in instructions and examples for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-artifact-author.md
...//articles/devtest-labs/devtest-lab-artifact-author.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only PowerShell (.ps1) script examples and commands, referencing Windows-specific tools (such as Chocolatey), and linking to a sample artifact that is Windows-focused. There are no equivalent Linux/Bash examples, and the main example for secure strings and artifact creation is entirely Windows/PowerShell-centric. Linux is mentioned as a supported OS, but no Linux-specific guidance or examples are provided.
Recommendations
- Add parallel Linux/Bash examples for artifact definition and usage, including secure string handling and artifact install commands.
- Include a sample artifactfile.json and script (e.g., artifact.sh) for a Linux VM, demonstrating how to use Bash scripts and Linux package managers (such as apt or yum).
- Reference Linux tools and patterns (e.g., using bash, sh, or Linux package managers) alongside Windows tools like PowerShell and Chocolatey.
- Ensure that when introducing examples, both Windows and Linux variants are presented, or at least alternate between them.
- Provide links to Linux-focused sample artifacts in the public DevTest Labs artifact repository.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-dev-guide-java-sdk.md
...main//articles/azure-maps/how-to-dev-guide-java-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All shell and command-line examples use PowerShell syntax, including project creation, environment variable setup, and program execution. There are no equivalent Bash or Linux/macOS shell examples provided. The documentation assumes the use of Windows tools and patterns throughout, which may hinder Linux or macOS developers.
Recommendations
- For every PowerShell example, provide an equivalent Bash example for Linux/macOS users.
- When demonstrating environment variable setup, show both PowerShell and Bash export syntax.
- For file creation and navigation (e.g., creating demo.java, running Java programs), include Bash commands alongside PowerShell.
- Instruct users on how to run Java files on both Windows and Linux/macOS (e.g., 'java demo.java' vs 'java ./demo.java').
- Avoid assuming the use of Windows-specific tools or shells; clarify that the SDK and tools are cross-platform.
- Consider a 'Platform differences' note or section to highlight any OS-specific considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-delete-lab-vm.md
...in//articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides automation instructions exclusively using PowerShell, a Windows-centric tool, without offering equivalent examples for Linux users (such as Azure CLI or Bash scripts). The only automation example is a PowerShell script, and there is no mention of cross-platform or Linux-native tools for scripting or command-line automation.
Recommendations
- Provide equivalent automation examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Include Bash script examples for deleting VMs and labs, or at least reference how to perform these tasks using Bash and Azure CLI.
- Explicitly mention that PowerShell Core is cross-platform if the script is compatible, or clarify if the script is intended for Windows PowerShell only.
- Add a section or note for Linux/macOS users, guiding them to use Azure CLI or other appropriate tools for automation.
- Ensure that any references to scripting or automation do not assume a Windows environment by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-dev-guide-js-sdk.md
...b/main//articles/azure-maps/how-to-dev-guide-js-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using PowerShell commands (e.g., 'mkdir', 'cd', 'npm init', 'node search.js') for project setup and execution, without providing equivalent Linux/macOS shell (bash) commands. There are no Linux-specific instructions or examples, and Windows/PowerShell syntax is presented as the default, which may confuse or inconvenience Linux/macOS users.
Recommendations
- Provide all command-line examples in both PowerShell (Windows) and bash (Linux/macOS) syntax, or use bash as the default with PowerShell alternatives.
- Explicitly mention that the commands work on both Windows and Linux/macOS, or note any differences.
- For project setup and execution steps (e.g., creating directories, running scripts), include bash equivalents such as 'mkdir mapsDemo', 'cd mapsDemo', 'npm init', and 'node search.js'.
- Consider using cross-platform neutral commands or code blocks labeled for each OS (e.g., '```powershell' and '```bash').
- Add a note in the prerequisites or introduction clarifying that the SDK and instructions are cross-platform, and provide links or guidance for Linux/macOS users where needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-maps/how-to-use-indoor-module.md
.../main//articles/azure-maps/how-to-use-indoor-module.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by using PowerShell prompts (>) in npm install commands, referencing command-line usage in a way that is typical for Windows users, and omitting explicit Linux/macOS shell examples. There are no Linux-specific instructions or clarifications, and the only command-line examples are presented in a Windows-centric format.
Recommendations
- Provide command-line examples using a generic shell prompt ($) or show both Windows (PowerShell/cmd) and Linux/macOS (bash/zsh) variants for npm and related commands.
- Avoid using the '>' prompt, which is specific to PowerShell, unless also showing the equivalent for Unix-like systems.
- Add a note clarifying that the npm and webpack commands work on all platforms, and mention any OS-specific considerations if relevant.
- Where file paths or environment variables are referenced, show both Windows and Linux/macOS syntaxes if they differ.
- Consider including a section or callout for Linux/macOS users to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/devtest-labs/devtest-lab-create-environment-from-arm.md
...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its automation section by providing a detailed PowerShell script for automating environment creation, with no equivalent Bash or Linux shell example. PowerShell is a Windows-centric tool, and its exclusive use may disadvantage Linux users. While the Azure CLI is mentioned briefly, no concrete Linux/Bash example is provided, and the PowerShell workflow is presented first and in detail.
Recommendations
- Provide a full example of automating environment creation using Azure CLI in Bash, including a sample script and usage instructions.
- Present both PowerShell and Bash/Azure CLI examples side by side, or clearly indicate parity between Windows and Linux workflows.
- Avoid presenting Windows/PowerShell solutions first or exclusively; ensure Linux users are equally supported in automation and scripting scenarios.
- Explicitly mention any platform-specific requirements or differences, and provide guidance for both Windows and Linux users throughout the documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/application-volume-group-considerations.md
...etapp-files/application-volume-group-considerations.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and documentation first, such as linking to the Windows version of the 'Create a PPG using the Azure portal' guide. There are no Linux-specific examples, tools, or references provided, and the documentation does not mention or link to equivalent Linux guidance for proximity placement groups or other operations. This may give the impression that the guidance is primarily intended for Windows users, despite SAP HANA commonly running on Linux.
Recommendations
- Include links to both Windows and Linux versions of Azure documentation when referencing platform-specific guides (e.g., proximity placement groups).
- Add Linux-specific examples or notes where relevant, especially for common SAP HANA deployment tasks.
- Ensure that terminology and instructions are platform-neutral unless a step is truly Windows-specific; otherwise, provide parallel instructions for Linux environments.
- Review all external documentation links to ensure Linux parity and avoid defaulting to Windows-first documentation.
- Explicitly state that the guidance applies to both Windows and Linux SAP HANA deployments, and clarify any platform-specific differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-government.md
.../main//articles/azure-netapp-files/azure-government.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell connection instructions and commands, while omitting equivalent Linux or cross-platform shell (e.g., Bash) examples. The PowerShell section is more comprehensive than the Azure CLI section, and there is no mention of Linux-specific tools, patterns, or troubleshooting. The focus on PowerShell and lack of Linux/Bash examples may disadvantage users on non-Windows platforms.
Recommendations
- Add explicit Bash/Linux shell examples for connecting to Azure Government, especially for common tasks such as authentication and resource management.
- Expand the Azure CLI section to include more detailed, step-by-step instructions, similar to the PowerShell section.
- Include notes or links for Linux/macOS users regarding any platform-specific considerations or tools.
- Balance the prominence of PowerShell and CLI sections, ensuring that cross-platform tools are presented first or equally.
- Where PowerShell commands are shown, provide equivalent Bash/CLI commands side-by-side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azacsnap-configure-database.md
...cles/azure-netapp-files/azacsnap-configure-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides detailed, parity-rich instructions for SAP HANA, Oracle, and IBM Db2, all using Linux-native tools and shell commands. However, the Microsoft SQL Server section is Windows-centric, referencing only Windows executables (e.g., .\azacsnap.exe), and assumes a Windows environment without offering Linux alternatives or parity. The SQL Server section also appears last, but its instructions are Windows-specific, and there are no PowerShell or Windows command examples for the other databases, indicating a bias toward Windows for SQL Server scenarios.
Recommendations
- Add explicit instructions and examples for running AzAcSnap with Microsoft SQL Server on Linux (e.g., SQL Server on Linux, using azacsnap as a Linux binary, and connecting via sqlcmd or other Linux tools).
- Provide both Windows and Linux command-line examples for Microsoft SQL Server, including shell and PowerShell where appropriate.
- Clarify in the prerequisites and installation sections whether AzAcSnap supports SQL Server on Linux, and if so, provide parity in setup, configuration, and testing steps.
- Where Windows-specific tools or paths are mentioned (e.g., .\azacsnap.exe), also show the Linux equivalent (e.g., ./azacsnap) to ensure cross-platform clarity.
- Consider reordering or grouping instructions so that Linux and Windows environments are treated equally for all supported databases.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While the main instructions use the Azure Portal and Azure CLI (which are cross-platform), the REST API section specifically references 'REST API using PowerShell' and links to PowerShell-based examples, without mentioning or providing equivalent Linux/bash/cURL examples. The documentation also refers to right-clicking in the portal, a pattern more familiar to Windows users. There are no explicit Linux or bash examples for REST API usage, and PowerShell is mentioned as the automation tool for REST API interaction.
Recommendations
- Provide REST API usage examples using cURL or bash scripts alongside PowerShell examples to ensure Linux parity.
- When referencing automation, mention both PowerShell and bash/cURL as options for scripting REST API calls.
- Avoid using Windows-centric UI terminology (such as 'right-click') or clarify that equivalent actions can be performed on all platforms.
- Ensure that all code samples and automation references are cross-platform or explicitly note their platform specificity.
- Link to or provide documentation for using the Azure CLI and REST API from Linux/macOS environments, not just Windows/PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/configure-ldap-over-tls.md
...articles/azure-netapp-files/configure-ldap-over-tls.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes certificate generation and export using Windows Server tools (Certification Authority, MMC snap-in), with no mention of Linux-based methods or cross-platform alternatives. All examples and screenshots are Windows-centric, and there is no guidance for users managing AD DS or certificates from Linux or non-Windows environments.
Recommendations
- Add instructions for generating and exporting root CA certificates using common Linux tools such as OpenSSL.
- Include examples and screenshots for certificate management on Linux systems.
- Mention cross-platform certificate management options (e.g., using OpenSSL or certutil on Linux/macOS) alongside Windows tools.
- Ensure that steps for uploading certificates and configuring LDAP over TLS are not dependent on Windows-only workflows.
- Consider adding a section or callout for Linux administrators, highlighting any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md
...-netapp-files/azure-netapp-files-create-volumes-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based instructions and tooling for managing SMB volumes, such as using the Windows Security tab, Microsoft Management Console (MMC), and referencing Windows-specific commands and interfaces. There are no equivalent Linux examples or instructions for managing SMB permissions or accessing SMB shares from Linux clients. The documentation assumes the administrator is using Windows tools and does not mention or demonstrate how to perform similar tasks on Linux, despite SMB being accessible from Linux systems.
Recommendations
- Add examples and instructions for managing SMB share and file permissions from Linux clients, such as using 'smbclient', 'mount.cifs', or 'setfacl'.
- Include Linux command-line examples for mounting SMB shares and modifying permissions, alongside the Windows MMC and GUI instructions.
- Provide parity in screenshots and walkthroughs for both Windows and Linux environments where applicable.
- Explicitly mention that SMB volumes can be accessed and managed from Linux, and link to relevant documentation or guides.
- Ensure that references to tools and workflows do not assume a Windows-only environment, and introduce Linux alternatives where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md
...etapp-files/azure-netapp-files-set-up-capacity-pool.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell modules and commands before (and more prominently than) Azure CLI equivalents, and by providing explicit PowerShell command examples while only briefly mentioning Azure CLI. There are no Linux-specific examples or guidance, and the documentation assumes familiarity with Windows tooling.
Recommendations
- Provide Azure CLI command examples alongside PowerShell commands, especially for feature registration and status checks.
- Mention Azure CLI before or equally with PowerShell to avoid the impression that Windows is the primary or preferred platform.
- Include explicit Linux/macOS usage notes or examples where relevant, such as updating the Azure CLI or using CLI commands in Bash.
- Balance references to Windows-specific tools (like PowerShell modules) with cross-platform alternatives.
- Where screenshots or UI instructions are given, clarify that the steps are platform-agnostic or provide notes for non-Windows users if differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/azure-netapp-files-metrics.md
...icles/azure-netapp-files/azure-netapp-files-metrics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the section on registering and checking the status of the subscription quota feature. The primary examples use Azure PowerShell cmdlets (Register-AzProviderFeature, Get-AzProviderFeature), with Azure CLI (cross-platform) only mentioned secondarily in a brief note. There are no explicit Linux shell or Bash examples, and the PowerShell examples are presented first and in more detail. No Linux-specific tools or patterns are discussed elsewhere, but the bias is evident in the approach to command-line instructions.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
- Explicitly mention that both Azure CLI and PowerShell can be used, and clarify which is more suitable for Linux/macOS environments.
- Where possible, include Bash shell command examples for common tasks, or at least ensure parity in the depth and clarity of CLI and PowerShell instructions.
- Review other sections for subtle Windows-first language or screenshots, and ensure that instructions and visuals are platform-neutral or include Linux-relevant alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-netapp-files/create-active-directory-connections.md
...re-netapp-files/create-active-directory-connections.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows/PowerShell command examples (e.g., Get-ADUser, Set-ADUser), referencing Windows-specific tools and policies (such as Group Policy, registry keys, and Windows security policy settings), and omitting equivalent Linux/Unix commands or procedures for managing Active Directory integration. Windows terminology and tools are consistently mentioned first or exclusively, with little to no guidance for Linux administrators, despite the relevance of NFS and dual-protocol volumes.
Recommendations
- Provide equivalent Linux/Unix command examples for managing Active Directory integration, such as using 'adcli', 'realm', or 'ldapmodify' for Kerberos and LDAP configuration.
- Include instructions or references for configuring Kerberos encryption types and LDAP settings on Linux clients and servers.
- Balance the documentation by presenting both Windows and Linux procedures side by side, especially in sections relevant to NFS and dual-protocol volumes.
- Reference Linux tools (e.g., sssd, krb5.conf, nsswitch.conf) and describe how to configure them for Azure NetApp Files Active Directory integration.
- Clarify when certain steps or tools are Windows-only and provide alternative steps for Linux environments.
- Add troubleshooting tips and best practices for Linux-based environments, particularly for Kerberos, LDAP, and NFS integration.