593
Pages Scanned
47
Pages Flagged
593
Changed Pages
7.9%
% Pages Flagged
Scan Information
Started At: 2025-07-17 00:00:07
Finished At: 2025-07-17 00:10:58
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 593
Files Completed: 593
Problematic Pages
47 issues found
Azure Fluid Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-fluid-relay/concepts/customer-managed-keys.md
...es/azure-fluid-relay/concepts/customer-managed-keys.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and instructions before Azure CLI, referencing PowerShell modules and commands prominently, and linking to Windows-specific managed identity tutorials. There is no mention of Linux-specific shell usage, nor are there Bash or cross-platform scripting examples. The prerequisite tutorial link is Windows VM-specific, and PowerShell is presented as the primary scripting interface.
Recommendations
- Provide Bash and cross-platform shell examples alongside PowerShell, especially for Azure CLI usage.
- Reference Linux and macOS environments explicitly, including links to managed identity tutorials for Linux VMs.
- Avoid presenting PowerShell examples before CLI or REST unless usage data shows a clear majority of users on Windows.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary OS-specific notes.
- Balance tool references by including both Windows and Linux equivalents where relevant (e.g., for identity creation or key management).
Create Pull Request
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
...-docs/blob/main/articles/azure-netapp-files/faq-nfs.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides a detailed answer for troubleshooting NFS access from Windows clients, including explicit PowerShell commands and Windows mount examples, but does not provide equivalent troubleshooting or usage examples for Linux clients. The only Linux-specific guidance is a brief mention of editing /etc/fstab for persistent mounts, without concrete commands or troubleshooting steps. This results in a Windows-first and Windows-tools bias, with missing Linux examples for common scenarios.
Recommendations
- For every Windows-specific example (such as enabling CaseSensitiveLookup or mounting NFS volumes), provide equivalent Linux commands and troubleshooting steps (e.g., using mount options, nfs-utils, or systemd automount).
- When mentioning PowerShell or Windows tools, ensure Linux tools (such as mount, nfsstat, or showmount) are also referenced and described.
- If a scenario is described for Windows (e.g., slow folder lookup), include a comparable Linux scenario or note if it is not applicable.
- Avoid placing Windows examples or tools before Linux equivalents in sections that apply to both platforms; present both in parallel or start with Linux if the technology (NFS) is more commonly associated with Unix/Linux.
- Expand the Linux guidance beyond /etc/fstab to include troubleshooting, mount options, and common issues, matching the depth given to Windows.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md
...es/healthcare-apis/dicom/dicom-configure-azure-rbac.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for creating custom roles, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or ARM templates. There are no Linux or cross-platform command-line examples, and the only automation tool mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples for creating custom roles, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention and link to documentation for creating custom roles using ARM templates or the Azure Portal, which are platform-agnostic.
- When referencing PowerShell, clarify that it is available cross-platform, but also provide equivalent instructions for non-Windows users.
- Add a section or note highlighting cross-platform tools and approaches for managing Azure RBAC, ensuring Linux users are equally supported.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-migration-robocopy.md
...cles/storage/files/storage-files-migration-robocopy.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. It exclusively describes migration using RoboCopy, a Windows-only tool, and all instructions, examples, and troubleshooting are tailored for Windows systems. There are no Linux-based migration examples or equivalent tools mentioned, despite the initial claim that sources can include Linux servers. The mounting instructions, command syntax, and optimization tips are all Windows-specific, and there is no guidance for performing similar migrations from or on Linux systems.
Recommendations
- Provide equivalent migration instructions for Linux environments, such as using rsync, smbclient, or other Linux-compatible SMB tools.
- Include Linux command-line examples for mounting Azure file shares (e.g., using mount.cifs or smbclient).
- Discuss Linux-based migration scenarios, including any limitations or differences compared to RoboCopy.
- Mention cross-platform tools (such as AzCopy, if/when feature parity is sufficient) and provide guidance for both Windows and Linux users.
- Structure the documentation so that Windows and Linux instructions are presented in parallel or clearly separated sections, rather than focusing solely on Windows.
- Clarify in the introduction that the article is Windows-specific, or link to a separate Linux migration guide if available.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/files-whats-new.md
...cs/blob/main/articles/storage/files/files-whats-new.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and patterns (such as Azure File Sync, which is only available for Windows servers) are highlighted, often with no Linux equivalent mentioned. PowerShell is frequently referenced, sometimes before or instead of cross-platform tools like Azure CLI. Windows Server and SMB (a protocol most closely associated with Windows) are discussed in detail, while Linux/NFS features are mentioned less frequently and often as secondary. There are also cases where examples or instructions are only provided for Windows or Windows tools, with Linux equivalents missing or less emphasized.
Recommendations
- Wherever PowerShell is mentioned, ensure Azure CLI (which is cross-platform) is also referenced equally and examples are provided for both.
- When introducing features or tools (such as Azure File Sync), clarify platform support and, if not available for Linux, suggest alternative solutions or explicitly state the limitation.
- For every Windows/SMB example or feature, provide a Linux/NFS equivalent where possible, and ensure Linux/NFS features are not consistently presented after Windows/SMB ones.
- In lists or instructions, avoid always mentioning Windows or Windows tools first; alternate or group by platform.
- Expand documentation and guidance for Linux administrators, including more detailed examples and troubleshooting for Linux/NFS scenarios.
- Where features are Windows-only, clearly label them as such and provide links to Linux-relevant documentation.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-python.md
...articles/azure-functions/functions-reference-python.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias, primarily in the way it presents development and publishing workflows. Windows terminology ("command prompt") is used alongside "terminal" without explicit mention of Linux or macOS. Remote build is recommended for Windows users, and local build is discouraged on Windows, but there is little explicit guidance for Linux users. The documentation references Visual Studio Code and Azure Functions Core Tools, which are cross-platform, but does not provide Linux-specific examples, terminal commands, or troubleshooting tips. There are no PowerShell-specific examples, but the overall pattern assumes a Windows-first perspective.
Recommendations
- Explicitly mention Linux and macOS in all references to 'terminal or command prompt', and provide example commands using bash/zsh where appropriate.
- Include Linux-specific troubleshooting tips, such as file permission issues, case sensitivity, or common dependency installation problems.
- When discussing publishing and build workflows, clarify which steps or recommendations apply to Linux, macOS, and Windows, and provide parity in guidance.
- Add explicit examples of using Azure Functions Core Tools and CLI commands in a Linux shell environment.
- Where folder structures are shown, use generic or Linux-style paths (e.g., forward slashes) or provide both Windows and Linux path examples.
- Highlight any differences in behavior or requirements when developing and deploying from Linux/macOS versus Windows.
- Consider including a section or callout for Linux/macOS users with tips or known issues.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/compute-linked-services.md
.../main/articles/data-factory/compute-linked-services.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation demonstrates some Windows bias, particularly in the Azure Batch section, where PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) are referenced as the primary method for resource creation and management, with no equivalent Linux/CLI examples. Windows tools such as Microsoft Azure Storage Explorer are mentioned for storage management, with no mention of Linux-native alternatives. The documentation also refers to 'CMDLETs & APIS' for VM sizing, which is a Windows-centric term. While the HDInsight examples specify Linux as the default OS, and the JSON configuration is platform-neutral, the overall pattern is to mention Windows tools and patterns first or exclusively.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside PowerShell cmdlets for Azure Batch and other resource management tasks, ensuring parity for Linux and macOS users.
- When referencing tools like Microsoft Azure Storage Explorer, also mention cross-platform or Linux-native alternatives (e.g., AzCopy, Azure CLI storage commands, or third-party Linux-compatible tools).
- Use neutral terminology such as 'commands' or 'APIs' instead of 'CMDLETs' when referring to resource configuration, or clarify that both PowerShell and CLI options are available.
- Where possible, include Linux shell (bash) script examples or references, especially for common operational tasks (e.g., deleting storage containers, managing clusters).
- Ensure that documentation sections referencing management or troubleshooting steps do not assume use of Windows-only tools or interfaces.
Governance
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/governance/policy/concepts/policy-for-kubernetes.md
...es/governance/policy/concepts/policy-for-kubernetes.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation is largely cross-platform and Kubernetes-focused, but there are subtle signs of Windows bias. Windows-specific domains (e.g., login.windows.net), references to Azure PowerShell, and the use of Azure CLI (which is cross-platform but often associated with Windows environments) are present. The documentation sometimes lists Windows tools (Azure PowerShell) before Linux-native equivalents, and troubleshooting/logging examples do not explicitly address Linux-specific nuances. However, the majority of command-line examples use Azure CLI and kubectl, which are cross-platform, and there is explicit mention that the Azure Policy Add-on for Kubernetes can only be deployed to Linux node pools. There are no overtly missing Linux examples, but the documentation could do more to highlight Linux-native workflows and tools.
Recommendations
- When listing tools or commands, always mention cross-platform or Linux-native options first (e.g., Azure CLI before Azure PowerShell).
- Where Azure PowerShell is referenced, provide equivalent Bash or shell commands for Linux users.
- Clarify that Azure CLI and kubectl commands are cross-platform and provide explicit instructions for both Windows and Linux environments where paths, environment variables, or behaviors differ.
- Avoid using Windows-specific domains or terminology unless strictly necessary; if used, clarify their relevance to all platforms.
- Add troubleshooting/logging sections that address common Linux-specific issues (e.g., permissions, file paths, environment setup).
- Explicitly mention that all examples work on Linux unless otherwise noted, and provide any necessary Linux-specific prerequisites or caveats.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows bias by presenting Windows/Powershell tools and patterns before Linux equivalents, providing more detail for Windows scenarios, and omitting Linux-specific automation examples (e.g., no Bash scripting or Linux CLI nuances). While Azure CLI is cross-platform, the PowerShell section is highlighted and no Linux shell scripting is shown. The documentation also refers to Windows-specific behaviors and features before Linux ones.
Recommendations
- Provide Linux/Bash shell scripting examples alongside or before PowerShell examples in the automation section.
- Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any Linux-specific flags or considerations if applicable.
- Balance the order of presentation: when listing availability or features, alternate or combine Windows and Linux information rather than listing Windows first.
- Include troubleshooting or configuration steps that are specific to Linux environments, such as permissions or environment variables, if relevant.
- Where screenshots or portal instructions are given, clarify any differences in experience for Linux-hosted apps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-sidecar-multi-container-apps.md
...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by requiring PowerShell for the migration script, providing only PowerShell commands for key steps (such as decoding base64), and referencing a .ps1 script without any Linux shell or Bash alternatives. There are no Linux or Bash equivalents for the script-based migration, and PowerShell is listed as a prerequisite. This may hinder Linux/macOS users, who are likely to use Bash or other Unix shells.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell commands, especially for decoding base64 and running migration scripts.
- Offer a cross-platform migration script (e.g., a Bash script or a Docker container) or document how to run the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
- List prerequisites in a cross-platform way, e.g., 'PowerShell (Windows) or Bash (Linux/macOS)'.
- Where possible, use Azure CLI and Docker commands, which are cross-platform, and avoid steps that require Windows-only tools.
- Add explicit Linux/macOS instructions or notes for each step that currently only shows a Windows/PowerShell approach.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented alongside Azure CLI for automation, but no explicit Linux shell or bash scripting examples are provided. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, but Linux equivalents are not. In the FAQ, certain features are noted as 'Windows container apps only' without clarifying Linux support or alternatives. While OpenSSL is mentioned (which is cross-platform), the overall pattern is to mention Windows tools and patterns first, with limited Linux-specific guidance.
Recommendations
- When mentioning certificate export using IIS or Certreq.exe, also provide equivalent Linux commands (e.g., using OpenSSL or certutil) for users who generated CSRs on Linux.
- In automation sections, provide bash scripting examples or reference Linux shell usage in addition to Azure CLI and PowerShell.
- In the FAQ, clarify Linux support for features currently described as 'Windows container apps only', and provide alternatives or workarounds for Linux users where possible.
- When listing tools or workflows, avoid listing Windows-specific tools first or exclusively; ensure Linux and cross-platform tools are given equal prominence.
- Consider adding a table or section summarizing certificate management workflows for both Windows and Linux environments.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details →
Detected Bias Types
missing_linux_example
windows_first
powershell_heavy
Summary
The documentation page does not provide any command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There are no references to Linux tools, Bash, or cross-platform CLI usage. This suggests a bias towards Windows and PowerShell, with Linux users left without clear guidance.
Recommendations
- Add links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux.
- Include Bash or shell script examples alongside PowerShell where command-line configuration is discussed.
- Ensure that 'Next steps' and further reading sections provide parity for both Windows and Linux users.
- Explicitly mention that Application Gateway can be managed from any OS using Azure CLI or REST API, and provide documentation links.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-use-managed-service-identity.md
...t/api-management-howto-use-managed-service-identity.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples for scripting and automation, with no mention or examples of Azure CLI (cross-platform) or Bash scripting. The installation and usage instructions reference only PowerShell, which is traditionally associated with Windows, and there is no guidance for Linux or macOS users. The structure also presents PowerShell before ARM templates, and there are no Linux-native tools or shell examples provided.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all scripting/automation tasks.
- Include Bash shell script examples where appropriate, especially for resource creation and management.
- Explicitly mention that Azure CLI and ARM templates are cross-platform and can be used on Linux, macOS, and Windows.
- Reorder sections or provide parallel examples so that Windows and Linux users see their options equally (e.g., 'Azure CLI', 'Azure PowerShell', 'ARM template').
- Reference installation guides for Azure CLI on Linux and macOS, not just PowerShell.
- Where screenshots or UI steps are shown, clarify if there are any platform-specific differences.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no explicit Linux shell or Bash alternatives for PowerShell commands. The outbound IPv6 support section specifically notes that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. In command examples, PowerShell is presented as an alternative to Azure CLI, but not vice versa, and there is no mention of Linux-specific tools or workflows. The documentation does not provide parity in examples or explanations for Linux users, especially in areas where Windows-specific features or limitations are discussed first or exclusively.
Recommendations
- For every PowerShell example, provide an equivalent Bash or Linux shell example, or clarify when one is not applicable.
- Explicitly mention when a feature is Windows-only and, where possible, provide Linux alternatives or workarounds.
- In sections discussing command-line access, clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- When listing command examples, alternate the order (e.g., show Azure CLI before PowerShell, or group by platform).
- Add notes or links for Linux users where features are not available, and suggest best practices or alternatives.
- Include Linux-specific troubleshooting or testing steps (e.g., using dig instead of nslookup, or curl commands for both platforms).
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/modify-vm-policy-cli.md
...docs/blob/main/articles/backup/modify-vm-policy-cli.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a Windows bias by providing a file path example (C:\temp2\Policy.json) that is specific to Windows, without offering a Linux or cross-platform alternative. There are no Linux or macOS file path examples, and no mention of Linux-specific considerations for file handling. The documentation assumes a Windows environment for file operations, which may confuse or exclude Linux users.
Recommendations
- Provide both Windows and Linux/macOS file path examples when referencing files (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
- Explicitly mention that the Azure CLI commands work on all platforms and clarify any platform-specific differences.
- Include a note or section addressing common file path conventions for Linux/macOS users.
- Ensure that screenshots, if any, and further examples are platform-neutral or show parity between Windows and Linux.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing 'Run as administrator' for setup. There are no Linux or cross-platform alternatives or examples provided for these steps.
Recommendations
- Provide equivalent Azure CLI (az) and/or Azure Resource Manager (ARM) template examples for checking and configuring Application Gateway settings, which are cross-platform.
- Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or mitmproxy, with example usage for capturing and analyzing HTTP/HTTPS traffic.
- When referencing setup steps, avoid Windows-specific instructions like 'Run as administrator' unless also providing the Linux/macOS equivalent.
- Explicitly mention that Fiddler is one option and suggest alternatives for users on Linux or macOS.
- Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from other platforms where possible.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.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 Azure PowerShell examples for command-line operations, referencing PowerShell before (or instead of) Azure CLI or other cross-platform tools, and omitting Linux/Unix-specific instructions or examples. The use of PowerShell commands and terminology assumes a Windows environment, and there are no equivalent CLI/bash examples or guidance for Linux users.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Where PowerShell is referenced, explicitly mention that the steps can be performed on any OS with PowerShell Core, or provide equivalent bash/CLI scripts.
- Add Linux-specific notes or screenshots where portal navigation or file formats may differ.
- Ensure that all ARM template and scripting examples are presented in a platform-neutral way, or provide both Windows (PowerShell) and Linux (CLI/bash) variants.
- Update the 'Next steps' section to include links to CLI-based guides, not just PowerShell.
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/delete-account.md
...e-docs/blob/main/articles/automation/delete-account.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell examples are presented as the only scripting/automation option, and the documentation does not mention or prioritize Linux-native tools or workflows. The structure and examples assume a Windows-centric approach, potentially excluding Linux users or those preferring cross-platform tools.
Recommendations
- Add Azure CLI examples (az automation account delete, az monitor log-analytics solution delete, etc.) alongside PowerShell for all relevant operations.
- Include Bash shell snippets where appropriate, especially for users on Linux or macOS.
- When listing command-line options, present Azure CLI before or alongside PowerShell to avoid the impression of Windows-first bias.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider providing REST API examples using curl or httpie for users who prefer direct API calls.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing only Windows browser UI elements).
Automation
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automation/automation-runbook-types.md
...b/main/articles/automation/automation-runbook-types.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a strong Windows and PowerShell bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in much greater detail than Python or Linux-specific options. Many examples, sample scripts, and troubleshooting steps reference Windows file paths (e.g., C:\modules), Windows environment variables, and Windows-specific behaviors. There is little to no coverage of Linux-specific runbook authoring, execution, or troubleshooting, and no Linux shell (bash) examples are provided. Even where Linux is mentioned (e.g., Hybrid Runbook Workers), details are minimal compared to the extensive PowerShell/Windows coverage.
Recommendations
- Add Linux-specific examples and troubleshooting steps, especially for Hybrid Runbook Workers running on Linux.
- Provide parity in sample scripts, such as showing how to manage modules, file paths, and environment variables on Linux (e.g., using /opt, $HOME, or /tmp instead of C:\ paths).
- Include bash or Python shell examples where appropriate, not just PowerShell.
- Clarify which features and limitations apply to Linux Hybrid Runbook Workers, and document any Linux-specific constraints or workarounds.
- Reorder or balance the presentation so that Python and Linux options are not always secondary to Windows/PowerShell.
- Explicitly mention Linux support (or lack thereof) in each runbook type's description and limitations.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS equivalents. The tutorial assumes a Windows environment (e.g., file paths like c:\appgwcert.pfx), and does not provide alternative instructions for Linux or cross-platform users.
Recommendations
- Provide equivalent Azure CLI (az) commands for each step, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include instructions for generating self-signed certificates using OpenSSL, which is available on all platforms, not just New-SelfSignedCertificate (Windows-only).
- Use platform-agnostic file paths or note differences (e.g., c:\appgwcert.pfx vs. ~/appgwcert.pfx).
- Explicitly mention that the tutorial can be followed on Linux/macOS and provide any required adjustments.
- Add a section or callouts for Linux/macOS users, including how to install and use Azure PowerShell or Azure CLI on those platforms.
- Consider providing a toggle or tabs for PowerShell and Azure CLI/Bash examples throughout the tutorial.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-develop-local.md
...in/articles/azure-functions/functions-develop-local.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation demonstrates a mild Windows bias. Visual Studio (Windows-only) is consistently listed first in environment tables, and Windows-specific tools like PowerShell and Visual Studio are highlighted before cross-platform or Linux-native alternatives. The HTTP test tools section lists PowerShell and Microsoft Edge (Windows-centric) before curl, which is more common on Linux. There are no explicit Linux-only examples or tools, and Linux is generally mentioned as 'also supported' rather than as a primary platform.
Recommendations
- In environment tables, alternate the order of Windows and cross-platform tools, or list cross-platform tools (like VS Code and CLI) first to emphasize parity.
- In the HTTP test tools section, list curl and Bruno before PowerShell and Microsoft Edge, or group tools by platform.
- Include explicit Linux/macOS terminal examples (e.g., bash commands) alongside or before Windows/Powershell examples.
- Highlight Linux/macOS support more prominently, not just as a secondary note.
- Where Visual Studio is mentioned, clarify that it is Windows-only and suggest equivalent Linux/macOS workflows (e.g., JetBrains Rider, VS Code, CLI).
- Add a section or callout specifically for Linux/macOS users, summarizing recommended tools and workflows.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/resources/troubleshoot.md
...in/articles/remote-rendering/resources/troubleshoot.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias, particularly in troubleshooting steps that assume a Windows environment. Several instructions reference Windows-specific tools (PowerShell, Windows Explorer, registry commands), and there are no equivalent examples or guidance for Linux or macOS users. File system limitations and codec installation steps are described only for Windows, and the use of Windows terminology and screenshots is pervasive. No Linux or cross-platform alternatives are provided for key troubleshooting scenarios.
Recommendations
- Provide equivalent troubleshooting steps for Linux and macOS where applicable, especially for tasks like codec installation, file permissions, and file system limitations.
- Include command-line examples for Linux (bash) alongside PowerShell/cmd examples.
- When referencing file system limitations, clarify which are Windows-specific and note any differences for Linux/macOS.
- Avoid assuming the use of Windows Explorer; suggest cross-platform alternatives (e.g., file managers, terminal commands).
- For package installation and driver updates, provide links or instructions for Linux/macOS where possible.
- Explicitly state when a step or limitation is Windows-only, and offer guidance or workarounds for other platforms.
- Add screenshots or terminal output from Linux/macOS environments where relevant.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference-java.md
...n/articles/azure-functions/functions-reference-java.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation generally aims for cross-platform parity, but there are subtle Windows biases. Command-line examples are consistently provided for both Bash (Linux/macOS) and Cmd (Windows), but the Windows/Cmd tabs are always listed after Bash, which is positive. However, there is a notable absence of explicit PowerShell examples, which is good, but the documentation refers to 'command prompt' (a Windows term) alongside 'terminal' in some places. Some sections, such as Java version support, list Windows before Linux, and the table for supported Java versions is headed 'Java versions (Windows)' before 'Java versions (Linux)'. There are no Linux-specific tools or troubleshooting steps, and the documentation does not mention Linux-specific differences or caveats. While the documentation is not overtly Windows-centric, it does not provide Linux-first or Linux-specific guidance, and some language and ordering choices subtly prioritize Windows.
Recommendations
- When referencing command-line development, use 'terminal' or 'shell' instead of 'command prompt' to avoid Windows-centric language.
- In tables and lists, alternate the order of Windows and Linux, or use alphabetical order to avoid always listing Windows first.
- Add Linux-specific troubleshooting tips or notes where relevant, especially for environment variables, file paths, or permissions.
- Explicitly mention that all CLI and Maven commands work identically on Linux, macOS, and Windows, and highlight any OS-specific caveats.
- Consider including PowerShell examples only if there are unique steps, and always provide Bash equivalents.
- Where IDEs are mentioned, clarify that all are cross-platform (e.g., IntelliJ, Eclipse, VS Code) and that the experience is consistent across OSes.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/disable-showmount.md
.../main/articles/azure-netapp-files/disable-showmount.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page primarily uses Azure PowerShell commands for feature registration and management, with only a brief mention of Azure CLI as an alternative. There are no Linux shell or bash examples, and the PowerShell examples are presented first and in detail, which may disadvantage Linux users or those who prefer CLI/bash environments.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside or before PowerShell examples, especially for feature registration and status checking.
- Include explicit bash/Linux shell command blocks for tasks that can be performed from non-Windows environments.
- Clarify that all operations can be performed from any OS using Azure CLI, and provide links or instructions for installing and using Azure CLI on Linux.
- Ensure screenshots and UI references are OS-agnostic or supplemented with CLI output examples.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/create-volumes-dual-protocol.md
...les/azure-netapp-files/create-volumes-dual-protocol.md
High Priority
View Details →
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a Windows bias primarily in the 'Manage LDAP POSIX Attributes' section, where only Windows-based tools (Active Directory Users and Computers MMC snap-in) are described for managing POSIX attributes. There are no equivalent instructions or examples for performing these tasks from Linux or cross-platform tools. Additionally, the instructions for accessing the Attribute Editor are Windows-specific, and the documentation does not mention or provide guidance for Linux-based LDAP management tools. While NFS client configuration is referenced, it is only linked out and not described inline, and the overall flow assumes Windows administrative environments for directory and attribute management.
Recommendations
- Add equivalent instructions for managing LDAP POSIX attributes using Linux-based tools such as ldapmodify, ldapadd, or graphical tools like Apache Directory Studio.
- Include examples or references for editing LDAP attributes from Linux command line or cross-platform tools, not just Windows MMC.
- When describing attribute management, present both Windows and Linux methods, or at least mention that Linux-based alternatives exist.
- Consider reordering sections or providing parallel instructions so that Linux and Windows administrative tasks are given equal prominence.
- Where screenshots are provided for Windows tools, consider adding screenshots or command examples for Linux tools to improve parity.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/pre-backup-post-backup-scripts.md
...main/articles/backup/pre-backup-post-backup-scripts.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by referencing only Windows file paths and conventions (e.g., 'Drive:' notation, backslashes in paths), mentioning Windows-specific technologies (e.g., Exchange, SQL Server, SharePoint), and omitting any mention of Linux or cross-platform usage. There are no examples or instructions for Linux environments, nor any discussion of Linux-compatible scripting or file system conventions.
Recommendations
- Include explicit guidance for Linux environments, such as using forward slashes in paths and Linux mount points (e.g., '/mnt/data').
- Provide Linux-specific examples for ScriptingConfig.xml, including how to specify data sources and script paths.
- Clarify whether MABS supports Linux agents and, if so, document any differences in script execution or configuration.
- Mention Linux scripting languages (e.g., Bash, Python) and how to invoke them in the configuration.
- Ensure that references to Windows technologies are balanced with Linux equivalents where applicable, or clearly state if only Windows is supported.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md
...n/articles/backup/backup-azure-alternate-dpm-server.md
High Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation exclusively describes recovery using Azure Backup Server and System Center Data Protection Manager (DPM), both of which are Windows-only tools. All instructions, screenshots, and terminology are focused on the Windows GUI and workflow, with no mention of Linux-based recovery, command-line alternatives, or cross-platform considerations. There are no examples or guidance for Linux environments or tools.
Recommendations
- Explicitly state in the introduction that Azure Backup Server and DPM are Windows-only, and clarify support for Linux workloads if any.
- If Linux-based recovery is supported (e.g., for files backed up from Linux VMs), add equivalent instructions or reference documentation for Linux recovery scenarios.
- Include command-line or script-based recovery examples (such as PowerShell for Windows and Bash/CLI for Linux, if supported).
- Mention and link to Azure-native or cross-platform backup/recovery options for Linux users, such as Azure CLI or Recovery Services Vault operations for Linux VMs.
- Ensure parity in documentation structure and detail for both Windows and Linux recovery workflows if both are supported.
Backup
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/manage-backup-vault.md
...-docs/blob/main/articles/backup/manage-backup-vault.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. When mentioning command-line options for moving Backup vaults, it lists PowerShell before CLI, and the PowerShell module is referenced directly, while the CLI reference is less prominent. There are no explicit Linux-specific examples or guidance, and no mention of Bash or Linux shell environments. The documentation assumes familiarity with PowerShell and does not provide parity for Linux users, such as Bash or cross-platform CLI examples, nor does it clarify that the Azure CLI is cross-platform.
Recommendations
- When referencing command-line tools, list Azure CLI before or alongside PowerShell, and clarify that Azure CLI is cross-platform (Windows, Linux, macOS).
- Provide explicit Bash/Linux shell examples where scripts or command-line operations are discussed, or at least mention that the Azure CLI commands work identically on Linux.
- Where PowerShell modules are referenced, also provide equivalent Azure CLI commands and documentation links.
- Add a section or note clarifying that all portal and Azure CLI instructions are applicable to Linux users, and provide links to Azure CLI installation and usage on Linux.
- Avoid assuming PowerShell as the default scripting environment; use neutral language or provide both PowerShell and Bash/CLI script snippets.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md
...main/articles/cyclecloud/how-to/user-authentication.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing Windows-style username formats (DOMAIN\user), and referencing Windows authentication patterns without equivalent Linux-focused examples. While LDAP and Entra ID are mentioned, there is a lack of explicit Linux authentication scenarios, examples, or command-line instructions (e.g., for Linux PAM, SSH integration, or Linux user mapping). The only mention of Linux is in the context of SSH keys for cluster nodes, but this is not given the same prominence or step-by-step detail as the Windows/AD sections.
Recommendations
- Add explicit Linux authentication examples, such as integrating with Linux PAM, local /etc/passwd, or SSSD.
- Provide step-by-step instructions for configuring LDAP authentication from a Linux client perspective, including sample Linux user formats and command-line tools.
- Include Linux username formats (e.g., user@domain.com, uid-based logins) alongside Windows formats in all relevant sections.
- Balance the order of presentation so that Linux/LDAP authentication is described with equal prominence and detail as Active Directory.
- Reference Linux tools (e.g., ldapsearch, kinit, ssh) and provide troubleshooting steps for Linux environments.
- Clarify that CycleCloud supports both Windows and Linux authentication scenarios equally, and provide parity in screenshots and configuration walkthroughs.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deliver-proof-concept.md
...ob/main/articles/devtest-labs/deliver-proof-concept.md
High Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows client OS access and licensing (Windows 10/8.1, MSDN, Enterprise Dev/Test subscription) in the Azure subscription section, with no mention of Linux equivalents or licensing. The examples and prerequisites focus on Windows tools and Microsoft-centric collaboration platforms (Visual Studio, Teams, SharePoint) without referencing Linux or open-source alternatives. There are no explicit Linux or cross-platform examples for VM usage, remote access, or DevTest Labs scenarios.
Recommendations
- Include information about using Linux-based VMs in DevTest Labs, including licensing and Marketplace image options.
- Provide examples or references for connecting to Linux VMs (e.g., SSH instructions, Linux remote desktop options) alongside RDP/Windows examples.
- Mention open-source or cross-platform collaboration tools (e.g., GitHub, GitLab, Slack, Mattermost) in addition to Microsoft Teams, SharePoint, and Azure Repos.
- Clarify that DevTest Labs supports both Windows and Linux environments, and provide links to relevant Linux documentation.
- Balance the order of presentation so that Linux options are mentioned alongside or before Windows options where appropriate.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md
...in/articles/data-factory/connector-upgrade-guidance.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides only a PowerShell script example for programmatically finding impacted objects, with no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or Python). This suggests a bias toward Windows users and tools, potentially excluding users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples using Azure CLI and/or REST API calls, which are cross-platform and work natively on Linux and macOS.
- Include a Bash or Python script example for finding impacted objects, or at least reference how to adapt the PowerShell logic for non-Windows environments.
- Explicitly mention that the PowerShell script can be run using PowerShell Core (pwsh) on Linux/macOS, if applicable, and provide instructions for doing so.
- Ensure that future documentation sections do not assume Windows as the default environment, and always offer cross-platform guidance where possible.
IoT Central
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/iot-central/core/howto-integrate-with-devops.md
...ticles/iot-central/core/howto-integrate-with-devops.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a bias toward Windows and PowerShell-centric workflows. All scripting examples use PowerShell, and the main automation scripts are provided only as PowerShell (.ps1) files. There are no equivalent Bash, shell, or cross-platform scripting examples, nor is there guidance for users who prefer or require Linux-native tooling. The documentation assumes the use of PowerShell 7 on all platforms, but does not provide alternative approaches for users who may not wish to use PowerShell or are working in environments where PowerShell is not standard.
Recommendations
- Provide equivalent Bash/shell script examples for all PowerShell scripts, especially for key automation steps such as generating configuration files and applying configurations.
- Explicitly mention and demonstrate how to run the workflow on Linux/macOS environments, including any necessary prerequisites or differences.
- Offer guidance or references for users who prefer to use Azure CLI, Python, or other cross-platform scripting languages instead of PowerShell.
- If PowerShell is required, clarify why and provide troubleshooting or installation guidance for Linux/macOS users, including any known limitations.
- Consider providing Docker-based examples or containers to encapsulate the workflow in a platform-neutral way.
Healthcare Apis
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/healthcare-apis/dicom/dicom-register-application.md
...es/healthcare-apis/dicom/dicom-register-application.md
High Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the PowerShell command 'New-SelfSignedCertificate' for creating self-signed certificates, without mentioning Linux or cross-platform alternatives. No Linux or macOS command-line examples or tools are provided for certificate creation, and the only explicit command-line tool mentioned is Windows-specific.
Recommendations
- Provide equivalent Linux/macOS instructions for creating self-signed certificates, such as using 'openssl' (e.g., 'openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes').
- Mention cross-platform tools or approaches (e.g., Azure CLI, OpenSSL) alongside Windows tools.
- Where PowerShell is referenced, clarify if it is available cross-platform, or provide alternative shell commands.
- Add explicit Linux/macOS screenshots or terminal examples where relevant, or at least mention that the steps are applicable across platforms.
- Review for other Windows-centric terminology and ensure parity in tool and workflow recommendations.
Load Balancer
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/whats-new.md
...ure-docs/blob/main/articles/load-balancer/whats-new.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation page exhibits subtle Windows bias. For example, the only explicit link to a hands-on guide for creating a dual stack application refers to a PowerShell-based tutorial (which is Windows-centric), and there are no visible Linux or cross-platform CLI examples or references. The documentation does not mention Linux tools or provide parity in example commands or scripts. This could make Linux users feel less supported or require extra effort to find relevant guidance.
Recommendations
- Add equivalent Linux/bash/Azure CLI examples and links wherever PowerShell or Windows-specific instructions are referenced.
- Ensure that links to tutorials or how-to guides (e.g., for creating dual stack applications) include both PowerShell and Azure CLI/Bash options, and mention both in the main documentation.
- Wherever possible, use cross-platform tools (such as Azure CLI) in examples, or provide both PowerShell and Bash/Azure CLI snippets side by side.
- Explicitly mention Linux support and tools in relevant sections to reassure non-Windows users that their platforms are equally supported.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/how-to-scale-out-for-migration.md
...ain/articles/migrate/how-to-scale-out-for-migration.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a strong Windows bias. All setup instructions, scripts, and tooling are targeted exclusively at Windows Server environments. Only PowerShell scripts are provided, and all examples, command-line instructions, and validation steps use Windows-specific tools (e.g., CertUtil, PowerShell, Windows roles like IIS). There is no mention of Linux-based deployment, nor are there any Bash or cross-platform alternatives. The appliance is required to run on Windows Server 2019/2022, and Linux users are not provided with equivalent guidance or support.
Recommendations
- Provide equivalent instructions and scripts for deploying the Azure Migrate appliance on supported Linux distributions, if possible.
- Include Bash or shell script alternatives for key steps such as installer execution, hash validation, and configuration.
- Mention Linux compatibility (or lack thereof) explicitly in the prerequisites, and provide guidance for Linux-only environments.
- If the appliance is Windows-only by design, clarify this early and suggest workarounds or alternatives for Linux users.
- Offer examples using Linux-native tools (e.g., sha256sum for hash validation) alongside Windows tools.
- Document any limitations or roadmap for Linux support to set user expectations.
Migrate
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/discovered-metadata.md
...docs/blob/main/articles/migrate/discovered-metadata.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows-first bias in several ways: Windows examples, tools, and PowerShell cmdlets are often listed before Linux equivalents, and in some sections (such as ASP.NET, Java, and Spring Boot web app data), only Windows server discovery is described. There is heavy reliance on Windows-specific tools (WMI, PowerShell, Registry, etc.), and more detailed breakdowns for Windows features compared to Linux. Linux examples, while present, are sometimes less detailed or appear after Windows content.
Recommendations
- Ensure Linux and Windows sections are presented with equal prominence and detail, possibly by interleaving or parallelizing their presentation.
- Where Windows-specific tools (e.g., PowerShell, WMI) are mentioned, provide equivalent Linux commands or tools alongside, not just after.
- For sections like ASP.NET, Java, and Spring Boot web app data, clarify if Linux discovery is supported, and if so, provide Linux-specific details/examples. If not supported, explicitly state this.
- Balance the level of detail in Linux sections to match that of Windows, especially for software inventory, feature data, and storage metadata.
- Avoid using only Windows-centric terminology (e.g., 'cmdlet', 'WMI class') without Linux equivalents (e.g., 'command', 'proc file', 'systemd unit').
- In tables, present Windows and Linux data side by side where possible, rather than in separate, sequential sections.
- Review related content and links to ensure Linux scenarios are equally represented.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enterprise-security-package.md
...main/articles/hdinsight/enterprise-security-package.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page exhibits mild Windows bias, particularly in the 'Next steps' section, where a link to 'Work in Apache Hadoop on HDInsight from a Windows PC' is given before any mention of Linux or cross-platform tools. There is also a reference to Windows-specific tools, but no equivalent Linux-focused guidance or examples are provided. The main body of the documentation does not provide command-line or configuration examples, so bias in code samples is not present.
Recommendations
- Add parallel Linux-focused guidance and links in the 'Next steps' section, such as 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'Using HDInsight from Linux/macOS'.
- Ensure that any references to platform-specific tools (e.g., Windows tools) are balanced with Linux/macOS equivalents.
- Where possible, provide cross-platform instructions or clearly indicate when steps are platform-specific.
- Review linked documentation to ensure Linux users have equivalent onboarding and troubleshooting resources.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-scale-targets.md
.../articles/storage/files/storage-files-scale-targets.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exhibits a Windows bias primarily in the Azure File Sync sections. It explicitly states that the Azure File Sync agent runs on Windows Server, with all performance guidance and examples referencing Windows Server only. There are no mentions of Linux support, tools, or equivalent sync solutions for Linux clients. The rest of the documentation is protocol-agnostic (SMB/NFS) and does not show overt platform bias, but the File Sync section is Windows-centric.
Recommendations
- Clearly state platform support for Azure File Sync at the beginning of the relevant section. If Linux is not supported, make this explicit; if partial support exists, document it.
- If there are Linux-compatible alternatives for file synchronization with Azure Files (such as rsync, Azure CLI, or third-party tools), mention and link to them.
- Provide performance guidance and examples for Linux clients accessing Azure Files via SMB or NFS, including any relevant tuning or limitations.
- Where possible, use cross-platform terminology and avoid assuming Windows-only deployments, especially in general Azure Files sections.
- Add a comparison table or section outlining feature parity and differences between Windows and Linux clients for Azure Files and Azure File Sync.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-reference.md
...b/main/articles/azure-functions/functions-reference.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page demonstrates a mild Windows bias, primarily by listing Windows-centric tools (such as Visual Studio) before cross-platform or Linux-native alternatives, especially in the C# section. Visual Studio is consistently mentioned first, and there is no explicit mention of Linux-specific editors or shell environments (e.g., Bash, Linux terminal) in examples or tool recommendations. However, the documentation does provide cross-platform options like Visual Studio Code and Azure Functions Core Tools, and avoids exclusive use of PowerShell or Windows-only commands.
Recommendations
- Ensure that cross-platform tools (e.g., Visual Studio Code, Azure Functions Core Tools) are listed before or alongside Windows-specific tools like Visual Studio, especially in introductory and quickstart sections.
- Explicitly mention Linux and macOS compatibility for all tools where applicable, and provide links to Linux/macOS installation guides.
- Include examples or references to using the command line in Bash or other Linux shells, not just 'command prompt', to clarify cross-platform support.
- Where PowerShell is referenced, also mention Bash or sh equivalents if relevant.
- Consider adding a section or callout for Linux/macOS users to highlight any differences or tips for those environments.
Azure Vmware
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-vmware/azure-vmware-solution-known-issues.md
...les/azure-vmware/azure-vmware-solution-known-issues.md
Medium Priority
View Details →
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation page primarily describes Azure VMware Solution known issues in a platform-neutral manner, but there are subtle signs of Windows bias. Specifically, remediation steps for VMware Tools vulnerabilities reference the Azure VMware Solution Run command 'Set-Tools-Repo' without clarifying if or how this applies to Linux VMs, and one issue explicitly refers to 'VMware Tools for Windows.' There are no Linux-specific examples, tools, or guidance, and no mention of Linux guest considerations for VMware Tools updates or vulnerabilities.
Recommendations
- When referencing VMware Tools updates or vulnerabilities, explicitly state whether the guidance applies to both Windows and Linux VMs, or provide separate instructions if the process differs.
- If using commands like 'Set-Tools-Repo,' clarify their applicability to Linux guests and provide Linux-specific update instructions if needed.
- For issues that mention 'VMware Tools for Windows,' add parallel information for Linux guests, including any differences in remediation or impact.
- Include examples or notes for both Windows and Linux environments where guest OS actions are required, ensuring parity in documentation.
- Review all workaround steps to ensure they are inclusive of both Windows and Linux guest scenarios, especially for security advisories and update processes.
Azure Netapp Files
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-netapp-files/faq-data-migration-protection.md
...es/azure-netapp-files/faq-data-migration-protection.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation demonstrates mild Windows bias by listing the Windows tool (robocopy) before its Linux/Unix equivalent (rsync) in both migration and replication sections. Robocopy is specifically called out for SMB workloads, while rsync is mentioned for NFS. There are no explicit Linux command-line examples or references to Linux-native SMB tools (such as smbclient or cifs-utils), and no PowerShell-specific commands are present. However, both tools are mentioned, and the documentation does not exclusively focus on Windows.
Recommendations
- Alternate the order of tool mentions (e.g., sometimes list rsync before robocopy) to avoid a default Windows-first impression.
- Include Linux-native SMB tools (such as smbclient or cifs-utils) as alternatives for SMB data migration, not just robocopy.
- Provide example command lines for both Windows and Linux environments to ensure parity.
- Explicitly state that both Windows and Linux tools are supported and provide links to their documentation.
- Consider a table comparing migration tools across platforms (Windows, Linux, Mac) for both NFS and SMB.
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 →
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 methods), while Linux instructions are more concise and only mention the 'df -h' command. Windows-specific tools and UI patterns (File Explorer, 'dir' command) are highlighted, whereas Linux coverage is limited to a single command-line example. There is also a reference to PowerShell in the REST API section, but no equivalent mention of Bash or Linux scripting.
Recommendations
- Alternate the order of Windows and Linux sections in different documentation pages, or present them in parallel to avoid consistently prioritizing Windows.
- Expand the Linux section to include both GUI (if applicable, e.g., GNOME Files or KDE Dolphin) and command-line methods, mirroring the depth of the Windows instructions.
- Provide Linux shell scripting examples for monitoring capacity, similar to the PowerShell mention in the REST API section.
- Where possible, use neutral language and structure (e.g., 'On Windows (SMB) clients...' and 'On Linux (NFS) clients...') rather than always listing Windows first.
- Include links to Linux-specific tools or documentation where PowerShell or Windows tools are referenced.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-resource-instances.md
.../common/storage-network-security-resource-instances.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples before Azure CLI examples, potentially favoring Windows users. The PowerShell section is more extensive, with multiple scenarios and commands, while the Azure CLI section is briefer. There are no explicit Linux-specific examples or mentions of Linux tooling, but Azure CLI is cross-platform and included. No Linux shell or scripting examples are provided, and PowerShell is presented as the primary scripting interface.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Ensure parity in the depth and breadth of examples for both PowerShell and Azure CLI, covering all scenarios equally.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell commands (e.g., bash) where appropriate.
- Consider adding a short section or note for Linux users, highlighting any OS-specific considerations or best practices.
- Avoid implying PowerShell is the default or preferred scripting environment unless there is a technical reason.
Logic Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-maps-data-transformation-visual-studio-code.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/logic-apps/create-maps-data-transformation-visual-studio-code.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation explicitly states that the Data Mapper tool is only available in Visual Studio Code running on Windows operating systems. There are no instructions, examples, or troubleshooting steps for Linux or macOS users. The prerequisites and all workflow steps assume a Windows environment, and there is no mention of Linux compatibility or workarounds.
Recommendations
- Clearly indicate in the introduction and prerequisites that the Data Mapper tool is currently Windows-only, and provide a roadmap or status update for Linux/macOS support if available.
- Add a dedicated section for Linux/macOS users, outlining any possible workarounds, alternative tools, or expected timelines for cross-platform support.
- If partial functionality is available on Linux/macOS (e.g., editing maps manually, using CLI tools, or deploying maps), document those workflows explicitly.
- Ensure all screenshots, file paths, and instructions are either cross-platform or provide platform-specific variants.
- Monitor and update the documentation as soon as Linux/macOS support is released, ensuring parity in examples and troubleshooting guidance.
Storage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/common/storage-network-security-ip-address-range.md
...ge/common/storage-network-security-ip-address-range.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed instructions for both PowerShell and Azure CLI, but the PowerShell (Windows-centric) section is presented before the Azure CLI (cross-platform) section. There are no Linux-specific examples or mentions of Linux tools, and the PowerShell section is more prominent, which may suggest a Windows-first bias.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide installation instructions for Linux.
- Consider adding Bash or shell script examples for common Linux workflows, or at least acknowledge Linux usage scenarios.
- Balance the prominence of PowerShell and CLI sections, or combine them under a 'Command-line' heading with clear OS applicability notes.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/create-first-function-vs-code-node.md
.../azure-functions/create-first-function-vs-code-node.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation is generally cross-platform and focuses on Visual Studio Code, which is available on Windows, macOS, and Linux. However, there is a subtle Windows bias in the troubleshooting section, where a specific issue and solution are called out for Windows users ('When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.') without mentioning equivalent Linux or macOS troubleshooting steps. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present, but the only OS-specific troubleshooting tip is for Windows, indicating a 'windows_first' bias.
Recommendations
- Add troubleshooting tips relevant to Linux and macOS users, such as common issues with permissions, shell configuration, or dependencies on those platforms.
- Where OS-specific guidance is given (such as the WSL Bash note), provide parallel advice for Linux and macOS users, or clarify that the guidance is only relevant to Windows.
- Explicitly state that all steps are applicable to Windows, Linux, and macOS unless otherwise noted, to reinforce cross-platform parity.
- If possible, include a table or section summarizing any platform-specific considerations for all supported operating systems.
Azure Functions
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md
...le-task-scheduler/durable-task-scheduler-versioning.md
Low Priority
View Details →
Detected Bias Types
missing_linux_example
Summary
The documentation does not provide any OS-specific examples, but it does include a 'powershell' pivot without a corresponding Linux shell (e.g., Bash) or CLI example. There are no explicit Windows tools or patterns, but the absence of Linux/Unix shell examples or references creates an implicit bias by omission.
Recommendations
- If a 'powershell' pivot is included, add a corresponding 'bash' or 'shell' pivot with equivalent Linux/Unix command-line examples.
- Ensure that any CLI or scripting examples are provided for both Windows and Linux environments, or clarify when examples are OS-agnostic.
- Review the documentation for any implicit assumptions about the user's operating system and explicitly mention cross-platform support where applicable.
- If the feature is not available or behaves differently on Linux, state this clearly in the documentation.