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 1651-1675 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-specs.md
...les/azure-resource-manager/templates/template-specs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for all command-line operations, which is positive for cross-platform parity. However, PowerShell examples are consistently presented first, and the narrative often refers to 'PowerShell or CLI' (rather than 'CLI or PowerShell'), subtly prioritizing Windows-centric tooling. There are no explicit Linux-only examples or references to Linux-specific workflows, shells, or file system conventions. No Windows-only tools are used, but the ordering and language suggest a mild Windows/PowerShell bias.
Recommendations
- Alternate the order of PowerShell and CLI examples throughout the documentation, or present CLI examples first in some sections to avoid implicit prioritization.
- Use more neutral phrasing such as 'Azure CLI or PowerShell' instead of always 'PowerShell or CLI'.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and consider adding a note or example showing CLI usage in a Linux shell (e.g., bash).
- Where file paths are shown (e.g., './mainTemplate.json'), clarify that the syntax is compatible with both Windows and Linux/macOS, or provide both styles if relevant.
- Consider including a brief section or note on cross-platform compatibility, especially for users on Linux or macOS.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-add-resource.md
...ce-manager/templates/template-tutorial-add-resource.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents deployment instructions with PowerShell examples before Azure CLI, and uses PowerShell-specific syntax and variables (e.g., $templateFile) in explanations. While Azure CLI is included, there is a subtle preference for Windows/PowerShell workflows, and no explicit mention of Linux or Bash environments. The 'Verify deployment' and 'Clean up resources' sections focus on the Azure Portal, which is cross-platform, but do not provide command-line alternatives for Linux users.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell to avoid implicit Windows-first bias.
- Include Bash/Linux shell variable examples (e.g., templateFile=...) alongside PowerShell variable usage.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide installation links for all platforms.
- Where possible, provide command-line alternatives (e.g., az group delete) for resource cleanup, not just portal instructions.
- Use neutral variable syntax in explanations (e.g., <template-file-path>) instead of PowerShell-specific variables like $templateFile.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-tutorial-add-tags.md
...source-manager/templates/template-tutorial-add-tags.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents deployment instructions with PowerShell examples before Azure CLI, which can be interpreted as a 'Windows-first' approach. The use of PowerShell as the first tab and the mention of 'Azure PowerShell' before 'Azure Command-Line Interface (CLI)' in the prerequisites further reinforce a Windows-centric bias. However, Azure CLI is also provided, which is cross-platform, and there are no exclusive references to Windows-only tools or missing Linux examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples across documentation pages, or default to Azure CLI first, as it is cross-platform and more familiar to Linux/macOS users.
- In the prerequisites, mention Azure CLI before Azure PowerShell, or present them together without preference.
- Explicitly state that both Azure CLI and PowerShell are available on all major platforms, and provide links to installation instructions for Linux/macOS users.
- Where possible, include screenshots or instructions for verifying deployments using Azure CLI (e.g., 'az resource show') in addition to the Azure portal.
- Ensure that none of the instructions assume a Windows environment (e.g., use of backslashes in file paths, PowerShell-specific syntax) unless clearly noted.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-functions-resource.md
...ource-manager/templates/template-functions-resource.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is largely neutral and cross-platform, focusing on ARM template functions with JSON examples. However, in the section describing how to determine which resource types have a list operation, the PowerShell (Windows-centric) approach is mentioned before the Azure CLI (cross-platform) equivalent. The PowerShell cmdlet is also described in more detail, which may suggest a slight Windows-first and PowerShell-heavy bias.
Recommendations
- Present Azure CLI (cross-platform) commands before PowerShell examples, or at least give them equal prominence.
- Provide equivalent Bash or shell script examples where appropriate, especially in sections where command-line interaction is demonstrated.
- Ensure that all tooling recommendations (such as 'Get-AzProviderOperation') are paired with their Azure CLI equivalents, with equal explanation and detail.
- Explicitly state that both Azure CLI and PowerShell are supported on all major platforms, and link to installation guides for both.
- Review other documentation pages linked from this one (such as deployment guides) to ensure Linux and macOS parity in examples and instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/error-policy-requestdisallowedbypolicy.md
...ubleshooting/error-policy-requestdisallowedbypolicy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for resolving the 'RequestDisallowedByPolicy' error, but the PowerShell section is given equal prominence to the Azure CLI, and the PowerShell examples use Windows-centric cmdlets. There are no explicit Linux shell (bash) examples or notes about cross-platform usage, and the PowerShell examples assume a Windows environment, which may not be as familiar or available to Linux users.
Recommendations
- Add explicit bash/Linux shell examples for querying policy definitions and assignments using Azure CLI, including examples with jq for JSON parsing.
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
- If PowerShell examples are included, mention that PowerShell Core is available on Linux and macOS, or provide equivalent bash commands.
- Consider listing Azure CLI (bash) examples before PowerShell to avoid a Windows-first impression.
- Explicitly state that all examples are cross-platform unless otherwise noted, and provide guidance for users on different operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/overview.md
...les/azure-resource-manager/troubleshooting/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in several places, and by providing explicit PowerShell command examples while only briefly mentioning Azure CLI equivalents. There are no Linux-specific tools or workflows mentioned, and the focus on Visual Studio Code (a cross-platform editor, but traditionally associated with Windows) is not balanced with mention of other editors or shell environments.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially since Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that all tools (VS Code, Azure CLI, Bicep linter, etc.) are available on Linux, and provide links or notes for Linux users where appropriate.
- Include example commands for both PowerShell and Bash shells when referencing command-line troubleshooting.
- Consider mentioning other popular cross-platform or Linux-native editors (such as Vim or Emacs) for syntax checking, or clarify that the VS Code extensions work on Linux.
- Avoid defaulting to Windows-first terminology or ordering; strive for parity in tool and example presentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/troubleshooting/quickstart-troubleshoot-arm-deployment.md
...ubleshooting/quickstart-troubleshoot-arm-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup steps, but consistently lists PowerShell (a Windows-centric tool) alongside CLI, and sometimes before or equally with CLI. There are no Linux-specific shell examples (e.g., Bash), and the prerequisites mention Visual Studio Code and PowerShell before CLI, which may suggest a slight Windows-first orientation. However, the use of Azure CLI does support cross-platform usage. There are no exclusive Windows tools or patterns, but the presence and prominence of PowerShell may be seen as a bias.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and consider providing Bash shell examples or notes for Linux users.
- List Azure CLI before PowerShell in all sections, as CLI is cross-platform and more inclusive.
- In prerequisites, clarify that Visual Studio Code and Azure CLI are available on Linux and macOS, not just Windows.
- Optionally, add a section or callout for Linux/macOS users, highlighting any differences or confirming parity.
- Avoid implying that PowerShell is required for non-Windows users; mention that PowerShell Core is cross-platform if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-resource-manager/templates/template-test-cases.md
...zure-resource-manager/templates/template-test-cases.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform and neutral, focusing on ARM template syntax and best practices. However, there is a subtle Windows bias in the reference to the ARM TTK test case file, which is a PowerShell (.ps1) script, and in the linked documentation for Custom Script Extensions, where the Windows link is listed before the Linux link. No explicit command-line examples (PowerShell, Bash, etc.) are given, but the toolkit's primary implementation is PowerShell, which is more native to Windows environments.
Recommendations
- Explicitly mention that the ARM TTK toolkit can be run on Linux and macOS using PowerShell Core, and provide installation/running instructions for those platforms.
- Wherever possible, provide Bash or Azure CLI equivalents for any PowerShell scripts or references.
- When linking to platform-specific documentation (e.g., Custom Script Extensions), list Linux and Windows links together or in alphabetical order, rather than Windows first.
- If referencing scripts or tools with a .ps1 extension, clarify their cross-platform compatibility.
- Consider including a section or note about cross-platform usage and any known limitations or requirements for non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/includes/signalr-add-role-assignments.md
...azure-signalr/includes/signalr-add-role-assignments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the list of role assignment methods. PowerShell is more commonly associated with Windows environments, while Azure CLI is cross-platform and widely used on Linux. No explicit Linux examples or Linux-specific tools are mentioned, and the main walkthrough is portal-based, which is platform-neutral. However, the ordering of PowerShell before CLI subtly prioritizes Windows tooling.
Recommendations
- List Azure CLI before Azure PowerShell in the role assignment methods, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that both Azure CLI and PowerShell are available on all major platforms, including Linux, macOS, and Windows.
- Where possible, provide example commands for both Azure CLI and PowerShell, or link to example sections for each.
- If scripting examples are added in the future, ensure parity by providing both CLI and PowerShell versions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-concept-serverless-development-config.md
...gnalr/signalr-concept-serverless-development-config.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide explicit Windows-only commands or PowerShell-heavy content, but it does show bias by omitting Linux-specific instructions or examples, especially in areas like CORS configuration and local development. The instructions for enabling CORS in the cloud reference Azure portal UI steps that are the same for both OSes, but the note about Linux Consumption plan only mentions a limitation without providing a Linux workaround or parity guidance. There are no CLI or shell examples for Linux users, and the local development example assumes use of local.settings.json, which is cross-platform but lacks explicit Linux context. Overall, the documentation assumes a Windows-centric or portal-centric workflow and does not provide Linux-specific parity or alternatives.
Recommendations
- Add explicit Linux CLI (e.g., Azure CLI, Bash) examples for configuring CORS and deploying Azure Functions.
- When mentioning limitations for Linux plans (e.g., CORS not available in Linux Consumption), provide clear Linux-friendly workarounds or alternatives, such as using Azure CLI or API Management with step-by-step Linux instructions.
- Include notes or examples for common Linux development environments (e.g., VS Code on Linux, Bash terminals) where relevant.
- Ensure that all configuration steps (such as editing local.settings.json) clarify that the process is the same on Linux and Windows, or highlight any differences.
- Where possible, provide parity in code and deployment examples for both Windows and Linux users, including references to Linux-specific documentation or tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-quickstart-azure-functions-csharp.md
...e-signalr/signalr-quickstart-azure-functions-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While most command-line instructions use cross-platform tools (e.g., Azure Functions Core Tools, .NET CLI) and are shown as Bash commands, the prerequisites and setup sections reference Windows or Windows-first resources. For example, the Azure Functions Core Tools prerequisite links to a page with Windows as the first tab, and there is no explicit mention or example of Linux-specific instructions or troubleshooting. The Azure Storage Emulator is mentioned as an option, but Azurite (the cross-platform emulator) is only referenced via a link, not directly in the instructions. No Linux-specific installation or usage guidance is provided.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites.
- Provide direct links to Linux/macOS installation instructions for Azure Functions Core Tools and .NET SDK, not just Windows.
- When referencing storage emulators, mention Azurite as the default/cross-platform option, and provide a direct example of how to install and run it on Linux/macOS.
- If there are any platform-specific caveats (e.g., file permissions, path separators), call them out in the relevant steps.
- Consider adding a 'Platform notes' section or callouts for any steps that differ between Windows and Linux/macOS.
- Ensure all screenshots and UI references are either platform-neutral or have Linux/macOS equivalents where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-signalr/signalr-howto-scale-multi-instances.md
...s/azure-signalr/signalr-howto-scale-multi-instances.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples for configuring multiple endpoints using the 'dotnet user-secrets set' command, but only shows the syntax in Windows-style (cmd) and does not mention or provide equivalent Linux/macOS shell examples. There is also no mention of Linux-specific configuration files or patterns (such as environment variables or .bashrc), and the ordering of examples and instructions implicitly assumes a Windows environment.
Recommendations
- For every command-line example using 'dotnet user-secrets set', provide both Windows (cmd) and Linux/macOS (bash) syntax, or clarify that the command works cross-platform.
- Explicitly mention that 'dotnet user-secrets' is supported on Linux/macOS and provide any necessary prerequisites or differences (such as using 'export' for environment variables).
- When referencing configuration files (like 'web.config'), also mention or provide examples for Linux-friendly configuration approaches (such as environment variables or appsettings.json).
- Add a section or callout explaining how to perform all configuration steps on Linux, including any differences in file paths, environment variable syntax, or command-line usage.
- Ensure that any references to Azure portal configuration (such as replacing ':' with '__') are clearly explained for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/configure.md
...e-docs/blob/main//articles/azure-sql-edge/configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains a Linux-oriented approach (e.g., file paths, use of bash), but in sections providing command-line examples, PowerShell/Windows syntax is consistently presented immediately after bash, and sometimes without clear distinction or context. The PowerShell examples are not always necessary, and the order (bash first, then PowerShell) could suggest a slight Windows-first bias. There are also notes and caveats specific to Docker on Windows, but no equivalent depth for Linux, which may reinforce a perception of Windows primacy.
Recommendations
- Clearly label command examples as 'Linux/macOS (bash)' and 'Windows (PowerShell)' to avoid confusion and ensure parity.
- Consider whether PowerShell examples are necessary for every scenario, especially when the primary deployment target is Linux-based containers.
- Provide equivalent troubleshooting notes and caveats for Linux environments, not just for Windows and macOS.
- If both bash and PowerShell examples are included, alternate their order in different sections or group them under clearly marked subheadings.
- Explicitly state the intended audience/platform for each example to help users quickly find relevant information.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/deploy-dacpac.md
...cs/blob/main//articles/azure-sql-edge/deploy-dacpac.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references 'SQLPackage.exe' and 'SQL Client Tools' as the manual fallback for DACPAC/BACPAC deployment, which are primarily Windows-based tools. There are no explicit examples or instructions for performing these operations on Linux or with cross-platform tools, and no mention of Linux command-line equivalents or usage patterns.
Recommendations
- Include instructions and examples for using sqlpackage on Linux (e.g., via the .NET Core cross-platform version).
- Mention and provide examples for using sqlcmd or Azure Data Studio on Linux/macOS.
- Clarify that 'SQLPackage' is available cross-platform and provide download/installation links for Linux.
- Avoid referencing only Windows-specific tools (e.g., 'SQLPackage.exe'); instead, use 'sqlpackage' and clarify platform compatibility.
- Add Linux shell command examples for uploading files to Azure Blob Storage (e.g., using Azure CLI or azcopy).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/performance-best-practices.md
.../articles/azure-sql-edge/performance-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page predominantly presents platform-agnostic guidance but demonstrates subtle Windows bias by referencing SQL Server documentation and best practices that are historically Windows-centric, and by deferring Linux-specific configuration advice to a single, brief section at the end. There are no Linux-specific examples or commands, and the only mention of Linux is a link to another page. No PowerShell or Windows command-line examples are present, but the structure and references implicitly prioritize Windows knowledge and patterns.
Recommendations
- Provide explicit Linux-based configuration examples, such as sample Docker run commands for memory limits and file system tuning.
- Include Linux-specific best practices inline, not just as a link, such as recommended kernel parameters or file system settings for SQL Edge.
- Balance references to SQL Server documentation with links to equivalent Linux-focused resources.
- Add example configuration snippets for mssql.conf as it would appear on a Linux host.
- Consider a dedicated section comparing and contrasting Windows and Linux deployment/configuration nuances for Azure SQL Edge.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/tutorial-renewable-energy-demo.md
...icles/azure-sql-edge/tutorial-renewable-energy-demo.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation instructs users to 'open a command prompt' without specifying or including Linux (or macOS) terminal alternatives. There are no Linux-specific instructions or examples, and the navigation paths use backslashes, which are Windows-specific. This suggests a Windows-first approach and omits guidance for Linux users.
Recommendations
- Explicitly mention both Windows and Linux (and optionally macOS) in setup instructions.
- Use neutral terms like 'terminal' instead of 'command prompt', or specify both (e.g., 'open a command prompt or terminal').
- Provide both Windows (backslash) and Linux/macOS (forward slash) path examples, or use platform-agnostic notation.
- If there are platform-specific steps in the README.md, summarize or link to both sets of instructions here.
- Consider including a note that the demo is cross-platform and works on both Windows and Linux, if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-sql-edge/deploy-kubernetes.md
...lob/main//articles/azure-sql-edge/deploy-kubernetes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references SQL Server Management Studio (SSMS) as the tool for connecting to Azure SQL Edge, which is a Windows-only application. There are no examples or mentions of Linux-native tools (such as sqlcmd, Azure Data Studio, or other cross-platform clients) for connecting to the SQL Edge instance. This creates a bias toward Windows users and omits guidance for Linux or macOS users.
Recommendations
- Include examples of connecting to Azure SQL Edge using cross-platform tools such as Azure Data Studio or sqlcmd, which are available on Linux, macOS, and Windows.
- When mentioning SSMS, clarify that it is a Windows-only tool and suggest alternatives for Linux/macOS users.
- Provide sample connection commands for Linux/macOS terminals (e.g., using sqlcmd or Azure Data Studio) alongside or before SSMS instructions.
- Review all tool references to ensure that Linux and macOS users are not excluded from any step in the workflow.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/architecture-hub-and-spoke.md
...n//articles/azure-vmware/architecture-hub-and-spoke.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias, particularly in the 'Jump box and Azure Bastion' section, where only Windows 10 or Windows Server are mentioned as examples for the jump box VM. There are no references to Linux-based jump boxes or examples of using SSH (except as a feature of Bastion), and no Linux-specific guidance is provided. The documentation assumes Windows environments for management and access, omitting Linux alternatives.
Recommendations
- When describing the jump box, mention both Windows and Linux VM options (e.g., Ubuntu, CentOS) as supported and common choices.
- Provide examples or references for connecting to the jump box using SSH for Linux VMs, in addition to RDP for Windows.
- Clarify that Azure Bastion supports both RDP (for Windows) and SSH (for Linux), and provide links to relevant documentation for both scenarios.
- In sections discussing DNS and identity, briefly mention Linux-compatible solutions (e.g., Samba for AD integration, BIND for DNS) where appropriate.
- Review all example scenarios and ensure parity by including Linux-based workflows or at least acknowledging their support.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/arc-enable-guest-management.md
...//articles/azure-vmware/arc-enable-guest-management.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing VMware Tools (which is often associated with Windows VM management) and providing no explicit examples or instructions for Linux VMs. There are no Linux-specific commands, troubleshooting steps, or considerations, and the steps assume a GUI-driven workflow typical of Windows-centric environments. The only CLI example uses Azure CLI, which is cross-platform, but there are no Linux shell or PowerShell examples, nor any mention of Linux guest agent requirements or differences.
Recommendations
- Add explicit instructions or notes for enabling guest management and installing extensions on Linux VMs, including any differences in prerequisites or troubleshooting steps.
- Include Linux-specific examples or considerations, such as verifying VMware Tools on Linux, or handling Linux guest credentials.
- Clarify that the process applies equally to both Windows and Linux VMs, or highlight any differences.
- If possible, provide both GUI and CLI (shell, PowerShell) workflows for parity.
- Reference Linux documentation or troubleshooting guides where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/azure-security-integration.md
...n//articles/azure-vmware/azure-security-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias, especially in the example for creating analytics rules, which focuses solely on detecting failed sign-ins to Windows servers. There are no equivalent examples or queries for Linux VMs, nor are there instructions or screenshots showing Linux-specific integration or threat detection. The documentation assumes a Windows-centric environment, despite Azure VMware Solution supporting both Windows and Linux VMs.
Recommendations
- Provide equivalent Linux-focused examples, such as analytics rules for failed SSH logins or suspicious sudo activity.
- Include screenshots and step-by-step instructions for integrating Linux VMs with Defender for Cloud and Microsoft Sentinel.
- Mention Linux explicitly alongside Windows when discussing supported operating systems and threat detection scenarios.
- Offer sample KQL queries for common Linux security events (e.g., authentication failures, privilege escalation attempts).
- Clarify in the prerequisites and throughout the guide that both Windows and Linux VMs are supported and provide parity in coverage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/bitnami-appliances-deployment.md
...articles/azure-vmware/bitnami-appliances-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by instructing users to connect to the VM via RDP and linking only to Windows-specific VM connection instructions. The guidance for accessing the VM and vCenter is oriented toward Windows workflows, with no mention of Linux or cross-platform alternatives for remote access or management.
Recommendations
- Provide instructions for connecting to the VM using SSH from Linux/macOS, in addition to RDP for Windows.
- Include links to both Windows and Linux/macOS documentation for connecting to Azure VMs.
- Mention cross-platform tools (e.g., VMware Remote Console, SSH clients) and provide examples for both Windows and Linux environments.
- Ensure that all steps referencing remote access or management tools include Linux equivalents or alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-authenticate-client.md
...//articles/digital-twins/how-to-authenticate-client.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only .NET (C#) code samples and references to Visual Studio and the dotnet CLI for package management, which are primarily associated with Windows development environments. There are no examples or instructions for Linux or cross-platform development environments, nor are there any mentions of Linux-specific tools or workflows. This creates a bias towards Windows and .NET developers, potentially excluding users on Linux or those using other languages/platforms.
Recommendations
- Provide equivalent code samples in other supported languages (e.g., Python, Java, JavaScript), especially those commonly used on Linux.
- Include instructions for installing SDK packages using cross-platform tools (e.g., pip for Python, npm for JavaScript, Maven/Gradle for Java).
- Mention and demonstrate authentication flows and environment variable setup on Linux/macOS (e.g., using bash shell, export commands, etc.).
- Clarify that the Azure.Identity library and SDKs are cross-platform, and provide explicit guidance for non-Windows environments.
- Avoid referencing only Windows-specific tools (like Visual Studio) or, if mentioned, provide alternatives for Linux (e.g., VS Code, JetBrains Rider, command-line usage).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/deploy-azure-vmware-solution.md
.../articles/azure-vmware/deploy-azure-vmware-solution.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a validation step that specifically references creating and using a Windows virtual machine for connectivity checks, with a direct link to Windows VM creation instructions. There are no equivalent instructions or references for creating or using a Linux virtual machine, nor are there examples or guidance for Linux users. This may lead Linux users to feel unsupported or unclear about how to perform the same validation steps.
Recommendations
- Include parallel instructions and links for creating and using a Linux virtual machine in Azure for connectivity validation.
- Provide examples or screenshots that show both Windows and Linux VM network interface settings in the Azure portal.
- Explicitly mention that either Windows or Linux VMs can be used for validation, and provide guidance for both.
- Ensure that any references to signing in, network diagnostics, or tool usage are platform-neutral or have platform-specific alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/deploy-traffic-manager-balance-workloads.md
...ure-vmware/deploy-traffic-manager-balance-workloads.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the use of Microsoft IIS Servers as backend pool members and does not provide any examples or guidance for deploying or verifying Linux-based workloads. All references to backend servers are Windows-centric, and there are no Linux alternatives or parity in examples, which may lead users to believe that only Windows/IIS is supported or recommended.
Recommendations
- Include examples of configuring Linux-based backend servers (e.g., Apache, Nginx) in the backend pool.
- Explicitly state that backend pool members can be any OS, not just Windows/IIS.
- Provide screenshots or command-line examples for verifying backend pool membership and connectivity from both Windows and Linux VMs.
- Mention Linux-based verification steps (e.g., using curl or wget from a Linux VM to test endpoint availability).
- Clarify that the Traffic Manager and Application Gateway integration is OS-agnostic and works with both Windows and Linux workloads.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/integrate-azure-native-services.md
...ticles/azure-vmware/integrate-azure-native-services.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally describes Azure native monitoring and management services in a platform-neutral way, but there is a subtle Windows bias. Windows-specific monitoring details (such as registry and files) are mentioned before Linux equivalents (daemons), and there are no concrete Linux command-line examples for installing or managing extensions. The only Linux-specific guidance is a workaround for sudo prompts, but no Linux-centric monitoring or management workflows are detailed.
Recommendations
- Provide explicit Linux examples for installing and managing extensions, such as using the Azure CLI or relevant Linux commands.
- List Linux monitoring capabilities (e.g., log collection from syslog, journald, or specific Linux services) alongside Windows features, and not as an afterthought.
- Include Linux-first or at least parallel instructions and screenshots where possible, especially for common tasks like enabling guest management or configuring agents.
- Mention Linux tools and patterns (e.g., systemd, cron, logrotate) where relevant, to ensure Linux administrators see their environment reflected.
- Ensure that documentation sections describing monitoring or management features do not default to Windows terminology or order (e.g., mention Linux daemons before or alongside Windows registry/files).