Scan Details - Linux-first Docs for Azure

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation is heavily oriented toward Windows environments, with exclusive use of Windows tools (PowerShell scripts, IIS, RDGatewayFedAuth.msi, System Center VMM), and no mention of Linux equivalents or cross-platform alternatives. All code and automation examples are in PowerShell, and the workflow assumes RDP and Windows-based gateway solutions. There are no instructions or examples for Linux-based remote desktop gateways, certificate management, or automation, and Linux users are not addressed.

Recommendations:

Provide Linux-based examples for certificate creation and management (e.g., using OpenSSL or Linux CLI tools).
Include instructions or references for setting up a remote desktop gateway on Linux (such as xrdp, FreeRDP, or Guacamole) and how to integrate with Azure DevTest Labs.
Offer automation scripts in Bash or Azure CLI (not just PowerShell) for key steps such as certificate handling and lab configuration.
Mention and document cross-platform RDP clients and their compatibility with token authentication.
Clarify which steps or tools are Windows-specific and provide Linux alternatives where possible.
Consider a section or callout for Linux administrators, outlining any differences or additional requirements.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a web GUI often associated with Windows workflows), mentioning Azure PowerShell and Azure Classic CLI as automation tools, and not providing equivalent Linux-native command-line examples (such as Azure CLI on Bash or Linux scripting). The order of mention puts PowerShell before CLI, and there are no explicit Linux shell or scripting examples, despite HDInsight clusters being Linux-based by default.

Recommendations:

Include Azure CLI (az) command-line examples for installing and managing HDInsight applications, with sample Bash scripts.
When mentioning automation, list Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
Provide explicit Linux/Bash examples for tasks such as deploying Resource Manager templates, not just PowerShell.
Reference Linux-native tools and workflows (e.g., SSH, Bash scripting) more prominently, especially since HDInsight clusters are Linux-based.
Ensure that all instructions and examples are validated on both Windows and Linux environments, and note any OS-specific differences.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the primary tool for creating Logic App templates, without mentioning or providing examples for equivalent Linux-friendly tools such as Azure CLI or Bash scripting. The only explicit tooling guidance is for Azure PowerShell, which is most commonly used on Windows. There are no Linux or cross-platform command-line examples, nor are Linux-native tools or workflows discussed. This may lead Linux or macOS users to believe that Windows is required or preferred for these tasks.

Recommendations:

Add Azure CLI examples alongside or in place of Azure PowerShell references, as Azure CLI is cross-platform and widely used on Linux and macOS.
When mentioning tools, list Azure CLI first or equally with PowerShell to avoid the impression of Windows-first bias.
Provide explicit Bash or shell script examples for common deployment tasks, such as deploying ARM templates or managing parameters files.
Include a note clarifying that all template and deployment operations can be performed on Linux, macOS, and Windows, and link to relevant cross-platform documentation.
Where possible, avoid referencing Windows-specific tools (e.g., PowerShell modules) as the only option for template generation or deployment.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias in several areas: Windows tools and terminology are often mentioned first or exclusively (e.g., BitLocker, Windows Defender, WSUS, Windows Update), PowerShell cmdlets are referenced without equivalent Linux command examples, and some best practices (such as backup and encryption) provide detailed Windows-centric steps or links while Linux alternatives are less emphasized or missing. Linux is sometimes mentioned, but examples, tooling, and detailed guidance are more comprehensive for Windows.

Recommendations:

Provide Linux-specific examples and command-line instructions (e.g., bash, CLI, or Ansible) alongside PowerShell cmdlets.
When referencing Windows tools (like BitLocker, Windows Defender, WSUS), also mention and link to Linux equivalents (e.g., dm-crypt, ClamAV, unattended-upgrades, etc.) with equal detail.
Ensure that best practices and step-by-step guides are presented in a platform-neutral way or with parallel sections for both Windows and Linux.
Avoid always listing Windows first in lists or examples; alternate or present both platforms together.
Expand on Linux-specific Azure features (e.g., Azure Disk Encryption for Linux, Linux antimalware solutions, update management) with the same depth as Windows.
Include links to Linux documentation and community resources where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ powershell_heavy

Summary:

The documentation is heavily oriented toward Windows environments. It references Windows Server features (such as NTFS, Event Viewer, and Windows Server data deduplication), uses Windows-specific terminology (e.g., reparse points, FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS), and provides operational details and troubleshooting steps only for Windows. There are no examples, instructions, or considerations for Linux or cross-platform scenarios, and the only command-line tool mentioned is a PowerShell cmdlet.

Recommendations:

Clarify early in the documentation that Azure File Sync cloud tiering is currently only supported on Windows Server, if that is the case. If Linux support is planned or available, add corresponding sections.
If Linux support is available, provide equivalent examples, operational details, and troubleshooting steps for Linux (e.g., file attributes, file system support, event logging locations, and command-line tools).
Where Windows-specific features are discussed (NTFS, Event Viewer, PowerShell), note their platform specificity and, if possible, offer Linux alternatives or explicitly state that these features are not available on Linux.
Avoid using only PowerShell cmdlets in examples; if CLI or REST API alternatives exist, include them and show cross-platform usage.
In tables and screenshots, clarify if the UI or attributes shown are Windows-specific, and provide Linux equivalents if applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by exclusively referencing Windows file paths (e.g., F:\sync1), Windows tools (RoboCopy), and PowerShell cmdlets (Invoke-StorageSyncFileRecall). There are no examples or instructions for Linux systems, nor is there mention of Linux support or equivalent commands. The documentation assumes the use of Windows servers and omits guidance for Linux-based environments.

Recommendations:

Include explicit statements about platform support, clarifying whether Linux servers are supported as Azure File Sync endpoints.
If Linux is supported, provide equivalent Linux examples (e.g., Linux file paths, CLI commands, and tools) alongside Windows examples.
If PowerShell cmdlets are referenced, offer alternative commands for Linux environments (such as Azure CLI or shell scripts) where possible.
Avoid referencing Windows-specific tools (like RoboCopy) without mentioning Linux equivalents (such as rsync) or clarifying platform applicability.
Add a section or note addressing cross-platform considerations, including any limitations or differences in feature support between Windows and Linux.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias by specifying 'Windows' as the operating system in the app creation step and omitting any mention of Linux or cross-platform alternatives. There are no examples or instructions for deploying or configuring the app on Linux-based App Service plans, and no Linux-specific guidance is provided for runtime stack, startup commands, or environment variable management.

Recommendations:

Provide parallel instructions for creating the App Service app on Linux, including selecting 'Linux' as the operating system and specifying supported runtime stacks.
Include Linux-specific notes for configuring environment variables and startup commands, as the UI and options can differ from Windows.
Add a table or section comparing Windows and Linux App Service plans, highlighting any differences relevant to SRE Agent usage.
Ensure that all steps (deployment, slot management, environment variable configuration) are described for both Windows and Linux App Service environments.
If certain features are Windows-only, explicitly state this and provide workarounds or alternatives for Linux users.

Create pull request

Scan Information

Problematic Pages