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 651-675 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-identity-source-vcenter.md
...cles/azure-vmware/configure-identity-source-vcenter.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows Server Active Directory as the external identity source, with all examples, instructions, and screenshots referencing Windows tools and workflows. There are no examples or guidance for integrating with Linux-based LDAP servers or using Linux tools. The steps for certificate management, DNS configuration, and identity source setup are all described using Windows-centric tools (MMC, Windows Server AD, Azure portal) and PowerShell-like cmdlets, with no mention of Linux equivalents or cross-platform alternatives.
Recommendations
- Add parallel instructions and examples for integrating with generic (Linux-based) LDAP servers such as OpenLDAP, including how to export certificates and manage users/groups.
- Include Linux command-line examples (e.g., using openssl, ldapsearch, or certtool) for certificate verification and export.
- Provide guidance on configuring DNS and identity sources when the LDAP server is not Windows-based.
- Clarify which steps are specific to Windows Server Active Directory and which are applicable to any LDAP-compliant directory.
- Add screenshots and walkthroughs for Linux environments where relevant.
- Mention and link to documentation for integrating with non-Windows LDAP sources, if supported.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-dns-azure-vmware-solution.md
...es/azure-vmware/configure-dns-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing DNS verification examples exclusively using PowerCLI (a PowerShell-based tool), with no equivalent Linux or cross-platform CLI examples. The only command-line instructions are in PowerShell, and there is no mention of Linux-native tools (such as dig or nslookup from a Linux shell), nor any guidance for users operating from non-Windows environments.
Recommendations
- Provide equivalent Linux-based examples for verifying DNS resolution, such as using dig or nslookup from a Linux shell.
- Include cross-platform instructions or note how users on macOS or Linux can perform similar verification steps.
- Mention and demonstrate the use of REST API calls (e.g., via curl) for interacting with the NSX-T Policy API, which is platform-agnostic.
- Clarify that PowerCLI is a Windows-centric tool and suggest alternatives for users on other operating systems.
- Ensure that screenshots and UI instructions do not assume a Windows environment unless strictly necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-vmware-cloud-director-service-azure-vmware-solution.md
...re-vmware-cloud-director-service-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows/Azure-centric bias by exclusively referencing the Azure portal and Windows-based management patterns, with no mention of Linux tools, CLI alternatives, or cross-platform workflows. All instructions and screenshots are based on the Azure portal UI, and there are no PowerShell or CLI commands, but also no Linux shell or cross-platform examples. The documentation assumes the user is operating in a Windows/Azure environment, omitting Linux-native or cross-platform approaches for tasks such as credential retrieval, OVA deployment, or network configuration.
Recommendations
- Include equivalent instructions for performing key tasks (such as credential retrieval, OVA deployment, and network configuration) using cross-platform tools like Azure CLI, VMware CLI tools (ovftool), or REST APIs, which can be run on Linux, macOS, or Windows.
- Provide example commands for OVA deployment using ovftool or govc, which are commonly used on Linux systems.
- Mention how to retrieve VMware credentials and manage NSX/vCenter from the command line or via API, not just through the Azure portal UI.
- Add notes or sections highlighting any differences or additional steps for users working from Linux or macOS environments.
- Where screenshots are used, consider including CLI output or cross-platform tool screenshots in addition to portal UI images.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/configure-virtual-trusted-platform-module.md
...re-vmware/configure-virtual-trusted-platform-module.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific security features (such as BitLocker and credential protection), mentioning Windows operating systems before Linux in prerequisites, and focusing on Windows-centric terminology in the VBS section. There are no Linux-specific examples or equivalent Linux security tooling mentioned, and Linux support is only briefly acknowledged.
Recommendations
- Provide Linux-specific examples of vTPM usage, such as using LUKS/dm-crypt for disk encryption or Secure Boot with Linux distributions.
- Mention Linux security features (e.g., measured boot, IMA/EVM, SELinux) alongside Windows features like BitLocker and credential protection.
- List supported guest OSes in a neutral or alternating order (e.g., 'Linux, Windows Server 2008 and later, Windows 7 and later') or provide separate guidance for each.
- In the VBS section, clarify applicability to both Windows and Linux, or explicitly state if VBS is Windows-only.
- Include links to Linux documentation or guides for configuring vTPM and Secure Boot in popular distributions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/install-cloud-backup-virtual-machines.md
.../azure-vmware/install-cloud-backup-virtual-machines.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation focuses exclusively on installation and management via the Azure portal and VMware vSphere client, both of which are GUI-driven and commonly associated with Windows environments. There are no Linux CLI examples, nor are Linux-native tools or workflows mentioned. The documentation assumes usage of GUI tools and does not provide parity for users who may prefer or require Linux-based or command-line installation and management methods.
Recommendations
- Provide equivalent CLI instructions using Azure CLI, PowerShell Core (cross-platform), or REST API calls that can be executed from Linux systems.
- Include examples for managing the solution via SSH or Linux shell where possible, especially for backup/restore operations.
- Mention and document any Linux-compatible tools or scripts for automation.
- Clarify whether the solution is platform-agnostic or if there are limitations for Linux-only administrators.
- Add a section or callout for Linux users, highlighting any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/manage-arc-enabled-azure-vmware-solution.md
...ure-vmware/manage-arc-enabled-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows-based Management VM instructions before Linux-based ones. The activation command for the virtual environment is shown for both platforms, but the Windows example is listed first, and the Linux command is missing a closing backtick/quote, suggesting less attention to Linux users. No Linux-specific tooling or shell examples are provided beyond the activation command, and there is no mention of Linux-specific troubleshooting or environment considerations. All CLI examples use az CLI, which is cross-platform, but the overall flow and order favor Windows users.
Recommendations
- Alternate the order of Windows and Linux instructions or present them side-by-side to avoid Windows-first bias.
- Ensure Linux commands are complete, accurate, and receive equal attention as Windows commands.
- Include Linux-specific notes or troubleshooting tips where relevant.
- Explicitly state that all az CLI commands work identically on both Windows and Linux, and provide shell-specific guidance if needed.
- Consider including screenshots or terminal output from both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/deploy-vmware-cloud-director-availability-in-azure-vmware-solution.md
...e-cloud-director-availability-in-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows/Azure-centric bias by exclusively referencing Azure portal features (Run commands) and workflows, which are inherently Windows/PowerShell-oriented. There are no Linux CLI, shell, or cross-platform automation examples. The documentation does not mention or provide parity for Linux-based deployment or management approaches, nor does it reference Linux-native tools or scripting patterns. The focus is entirely on Azure portal and Run commands, which are typically accessed via Windows-centric environments.
Recommendations
- Provide equivalent Linux-based deployment instructions, such as using Azure CLI or shell scripts, for installing and managing VMware Cloud Director Availability.
- Include examples of automating deployments using cross-platform tools (e.g., Bash scripts, Ansible, Terraform) alongside or instead of Run commands.
- Explicitly mention whether Run commands can be invoked from Linux environments, and if so, provide sample commands for Linux terminals.
- Reference and link to any available Linux-native tools or APIs for managing VMware Cloud Director Availability, if applicable.
- Ensure that screenshots and step-by-step instructions are not limited to Azure portal UI, but also cover command-line and automation options accessible from Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/deploy-arc-for-azure-vmware-solution.md
...s/azure-vmware/deploy-arc-for-azure-vmware-solution.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash) examples for running the installation scripts, but the Windows example is presented first and with more detail (e.g., explicit note about execution policy). There is a slight emphasis on Windows tools and conventions, such as referencing PowerShell's execution policy and using Windows-style file paths in JSON examples. Linux instructions are present but less detailed, and there is no mention of Linux-specific troubleshooting or considerations.
Recommendations
- Present Linux and Windows examples in parallel tabs or with equal prominence, or alternate which OS is shown first.
- Provide Linux-specific troubleshooting notes, such as handling permissions, shell differences, or common errors.
- Use OS-agnostic file path examples in JSON (e.g., /home/user/cert.crt for Linux, C:\Users\user\cert.crt for Windows), or show both.
- Mention any dependencies or prerequisites for both Windows and Linux environments (e.g., required shell, package managers, or permissions).
- Ensure that all script instructions (such as extracting files, running scripts, or configuring proxies) are equally detailed for both platforms.
- Avoid assuming PowerShell as the default scripting environment; clarify when bash or sh is equally supported.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/deploy-zerto-disaster-recovery.md
...rticles/azure-vmware/deploy-zerto-disaster-recovery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, particularly in its discussion of the Zerto Cloud Appliance (ZCA), which is described as a Windows-only VM. The ZCA's core services (ZVM and VRA) are both Windows services, and no Linux alternatives or equivalents are mentioned for this component. While the core Zerto management and replication appliances (ZVMA and vRA) are Linux-based, the documentation gives more detailed attention to the Windows-based ZCA, especially in the context of Azure VM disaster recovery. There are no command-line examples or scripts, but the lack of Linux options for ZCA and the explicit mention of Windows services without Linux parity is a notable bias.
Recommendations
- If Zerto supports Linux-based alternatives for ZCA or its services, document them alongside or before the Windows options.
- Where possible, clarify whether ZCA functionality is strictly limited to Windows, or if Linux-based deployment is on the roadmap.
- Provide parity in technical detail for both Linux and Windows components, including architecture diagrams and operational guidance.
- If scripts or command-line instructions are added in the future, ensure both PowerShell (Windows) and Bash (Linux) examples are provided.
- Explicitly state platform limitations and recommend best practices for Linux users where Windows-only tools are required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/native-first-party-principle-security.md
.../azure-vmware/native-first-party-principle-security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation prioritizes Windows-centric tools and workflows. The PowerShell method is presented before the cross-platform Azure CLI, and there are no explicit Linux/bash examples or guidance. The use of Azure PowerShell commands and terminology assumes a Windows environment, which may disadvantage Linux or macOS users.
Recommendations
- Present Azure CLI (cross-platform) instructions before PowerShell, as CLI is available on Windows, Linux, and macOS.
- Include explicit bash/Linux shell examples and clarify that Azure CLI commands work on all major platforms.
- Add notes or sections for Linux/macOS users, such as how to install Azure CLI or use shell scripting.
- Avoid assuming PowerShell as the default scripting environment; mention both PowerShell and bash where relevant.
- Where possible, provide parity in troubleshooting or verification steps for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/migrate-sql-server-standalone-cluster.md
.../azure-vmware/migrate-sql-server-standalone-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows Server and Microsoft SQL Server running on Windows, with no mention of Linux-based SQL Server deployments or migration scenarios. All tested configurations, prerequisites, and validation steps assume a Windows environment. Tools and management patterns (e.g., SQL Server Management Studio, Windows Server Failover Clustering) are Windows-centric, and there are no examples or guidance for Linux-based SQL Server instances.
Recommendations
- Include explicit mention of whether Linux-based SQL Server instances are supported for migration using VMware HCX, and if so, provide guidance or caveats.
- Add tested configuration examples for SQL Server on Linux (e.g., Ubuntu, Red Hat) and clarify any differences in the migration process.
- Provide Linux-specific instructions for verifying SQL Server and database accessibility post-migration (e.g., using sqlcmd or Azure Data Studio on Linux).
- Reference Linux-based SQL Server documentation and best practices in the 'More information' section.
- If Linux is not supported, clearly state this limitation early in the documentation to set user expectations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/migrate-sql-server-failover-cluster.md
...es/azure-vmware/migrate-sql-server-failover-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows Server Failover Clustering and SQL Server on Windows, with all examples, screenshots, and tools (such as Failover Cluster Manager and SQL Server Management Studio) being Windows-specific. There is no mention of Linux-based SQL Server clusters, Linux failover solutions (e.g., Pacemaker), or cross-platform migration considerations. The prerequisites, migration steps, and troubleshooting are all tailored for Windows environments, and Linux alternatives are neither referenced nor suggested.
Recommendations
- Add a section or parallel guide for migrating SQL Server clusters running on Linux (e.g., using Pacemaker or Linux clustering tools).
- Include Linux-based examples, such as using command-line tools (e.g., systemctl, pcs) and SQL Server tools available on Linux.
- Reference Linux documentation for SQL Server clustering and migration in the 'More information' section.
- Clarify in the introduction that the guide is specific to Windows clusters, and provide links to Linux migration resources if available.
- Where possible, use neutral terminology (e.g., 'Failover Cluster Manager or equivalent tool') and describe steps for both platforms.
- Provide parity in troubleshooting and validation steps for Linux-based SQL Server clusters.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/tutorial-access-private-cloud.md
...articles/azure-vmware/tutorial-access-private-cloud.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes creating and using a Windows VM as the jump box for accessing Azure VMware Solution resources. All instructions, screenshots, and references are Windows-specific, with no mention of Linux as an alternative. There are no Linux VM creation steps, connection instructions, or examples for using Linux-based tools to access vCenter Server or NSX Manager.
Recommendations
- Add parallel instructions for creating a Linux VM as a jump box, including recommended Linux distributions.
- Provide steps for connecting to the Linux VM (e.g., SSH instructions) and accessing vCenter Server and NSX Manager from a Linux environment (using browsers or CLI tools).
- Include screenshots of the process from a Linux desktop environment.
- Mention both Windows and Linux options in checklists and introductory sections to signal platform parity.
- Link to both Windows and Linux VM connection documentation in the 'connect to a virtual machine' reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/using-run-command.md
.../blob/main//articles/azure-vmware/using-run-command.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing PowerShell cmdlets as the mechanism for Run Command operations, without mentioning or providing examples for Linux/Unix shells or tools. There are no Linux command-line examples, nor is there any discussion of how Run Command might be used with Linux-based VMs or scripts. The terminology and screenshots are also oriented towards Windows-centric workflows.
Recommendations
- Include examples of using Run Command with Linux/Unix shell scripts or commands, if supported.
- Clarify whether Run Command is limited to PowerShell or Windows VMs, or if it can be used with Linux VMs as well.
- If Linux support is available, provide equivalent bash or shell script examples alongside PowerShell cmdlets.
- Explicitly mention any platform limitations or parity in the documentation introduction.
- Add references to Linux tools or workflows where applicable, and ensure screenshots or UI descriptions are not exclusively Windows-centric.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/use-hcx-run-commands.md
...ob/main//articles/azure-vmware/use-hcx-run-commands.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references PowerShell cmdlets and Windows-centric tooling (e.g., 'Run Command panel', 'cmdlets' with PowerShell-style naming), with no mention of Linux command-line equivalents, Bash scripts, or cross-platform alternatives. All examples and instructions are tailored to a Windows/PowerShell environment, and there is no guidance for users operating from Linux or macOS systems.
Recommendations
- Provide equivalent Bash or shell script examples for each operation, or clarify if such cross-platform alternatives are not available.
- Explicitly state whether the Run Command functionality is accessible via Azure CLI, REST API, or other cross-platform tools, and provide usage examples.
- Add a section outlining how Linux or macOS users can perform these tasks, including any prerequisites or limitations.
- If the functionality is inherently tied to PowerShell, clarify this early in the documentation and suggest workarounds (such as using PowerShell Core on Linux/macOS) where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/protect-azure-vmware-solution-with-application-gateway.md
...protect-azure-vmware-solution-with-application-gateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All configuration examples for backend web servers use Windows Server 2016 with IIS, and all setup commands are provided exclusively in PowerShell. There are no examples or instructions for deploying or configuring Linux-based web servers (e.g., Ubuntu with Apache or Nginx), nor are Linux command-line equivalents (such as Bash commands) provided. The documentation implicitly assumes a Windows environment for backend pools, which may not reflect the diversity of customer environments.
Recommendations
- Add parallel examples using Linux VMs (e.g., Ubuntu or CentOS) as backend servers, including steps to install and configure Apache or Nginx.
- Provide Bash command equivalents for all PowerShell commands, such as using apt/yum for package installation and echo/touch for file creation.
- Explicitly state that both Windows and Linux VMs are supported as backend pools, and link to relevant documentation for Linux web server setup.
- Balance the order of examples so that Linux and Windows are presented equally, or alternate which OS is shown first in different sections.
- Include screenshots or CLI snippets from Linux environments (e.g., SSH terminal, Apache/Nginx default pages) to illustrate parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/manage-event-delivery.md
...lob/main//articles/event-grid/manage-event-delivery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring dead-letter and retry policies in Azure Event Grid. However, there is a notable bias toward Windows environments: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. There are also references to installing Azure PowerShell, which is primarily used on Windows. No explicit Linux shell (bash) or scripting examples are provided, and there is no mention of Linux-specific considerations or tools. The sample application referenced is for .NET, which is historically Windows-focused, though now cross-platform.
Recommendations
- Add explicit bash or shell script examples alongside PowerShell, especially for common tasks like variable assignment and command chaining.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- When referencing PowerShell, note that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS as well as Windows.
- Include Linux/macOS-specific notes or troubleshooting tips where relevant (e.g., file path differences, authentication nuances).
- Consider referencing or linking to sample applications in languages and frameworks popular on Linux (e.g., Python, Node.js) in addition to .NET.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/howto-move-across-regions.md
...articles/azure-web-pubsub/howto-move-across-regions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions for moving an Azure Web PubSub resource using the Azure Portal and Azure PowerShell. All command-line examples use Azure PowerShell, which is most commonly used on Windows, and there are no examples using Azure CLI, Bash, or Linux-native tools. The use of 'notepad' as the editor in the PowerShell example further reinforces a Windows-centric approach. There are no instructions or examples for Linux or cross-platform users, and PowerShell is presented as the only scripting option.
Recommendations
- Add equivalent Azure CLI (az) command examples for exporting, editing, and deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Replace or supplement 'notepad' with cross-platform editors (e.g., 'nano', 'vim', or 'code') or use a generic instruction like 'open the file in your preferred text editor'.
- Explicitly mention that PowerShell Core is available cross-platform, or provide Bash script equivalents.
- Reorder or parallelize instructions so that Azure CLI and PowerShell examples are presented together, or allow users to select their preferred platform.
- Include a note or section for Linux/macOS users, ensuring parity in guidance and tool recommendations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/quickstart-use-sdk.md
.../main//articles/azure-web-pubsub/quickstart-use-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Bash and Azure PowerShell examples for most CLI steps, but consistently lists Bash first and PowerShell second. However, there are several signs of Windows bias: PowerShell is presented as a primary shell alongside Bash, and some instructions (such as activating Python virtual environments) only show the Bash/Linux command, with no Windows/PowerShell equivalent. There is also an assumption that users have access to both Bash and PowerShell, which is not always the case on Linux or macOS. The cleanup section contains a typo in the PowerShell variable name, and the documentation does not provide explicit Windows command prompts or CMD examples, nor does it address differences in environment variable syntax between shells.
Recommendations
- Explicitly state which steps are for Linux/macOS (Bash) and which are for Windows (PowerShell), and clarify that Bash is available on Windows via WSL or Git Bash.
- Provide Windows CMD and/or PowerShell equivalents for all Bash commands, especially for Python virtual environment activation (e.g., `env\Scripts\activate` for Windows).
- Ensure that environment variable syntax is correct for each shell (e.g., `$env:connection_string = "..."` for PowerShell, `set connection_string=...` for CMD, `export connection_string=...` for Bash).
- Consider including a table summarizing the shell differences and how to adapt commands for each platform.
- Fix the typo in the PowerShell cleanup command (`$ResourceGroup` should match earlier variable names).
- Where possible, provide cross-platform guidance or links to official documentation on running Bash on Windows and PowerShell on Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/socket-io-serverless-tutorial-python.md
...ure-web-pubsub/socket-io-serverless-tutorial-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows command-line conventions (such as backslashes in paths), using Windows-centric tools (like Azurite with a Windows-style debug log path), and omitting explicit Linux/macOS equivalents or clarifications. While most commands are cross-platform, the documentation implicitly assumes a Windows environment and does not provide Linux-specific instructions or examples.
Recommendations
- Explicitly mention that all CLI commands work on Linux/macOS as well as Windows, and provide any necessary differences (e.g., path separators, environment variable syntax).
- For Azurite, show both Windows and Linux/macOS command examples (e.g., use 'azurite -l azurite -d azurite/debug.log' for Linux/macOS).
- Clarify that the Azure Functions Core Tools and Azurite are cross-platform, and provide installation links or instructions for Linux/macOS.
- If referencing file paths (such as in 'local.settings.json'), note the default locations on both Windows and Linux/macOS.
- Add a note or tabbed instructions for Linux/macOS users where there are differences, especially in commands or file handling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/tutorial-build-chat.md
...main//articles/azure-web-pubsub/tutorial-build-chat.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides cross-platform instructions, but there are subtle signs of Windows bias. In environment variable setup, both Bash (Linux/macOS) and Windows CMD examples are given, but the Windows example is shown second, which is good. However, there is no explicit PowerShell example, which is often seen in Microsoft docs. The Azure CLI is used throughout, which is cross-platform, but there are no explicit Linux-specific instructions or troubleshooting tips. The documentation assumes familiarity with Windows-centric patterns (such as 'SET' for environment variables and referencing localhost as 127.0.0.1), and does not mention Linux-specific tools or issues (e.g., systemd, firewall, SELinux, etc.). The use of the awps-tunnel tool is cross-platform, but no Linux-specific installation or permission notes are provided. There is a slight 'missing_linux_example' bias in that some commands (like environment variable setup) do not mention PowerShell, and there is no explicit mention of Linux desktop environments or distributions.
Recommendations
- Add explicit PowerShell examples for setting environment variables, or clarify that the Bash example works for Linux/macOS and the CMD example is for Windows.
- Include troubleshooting notes for common Linux issues (e.g., port permissions, firewall, SELinux) when running local servers.
- Mention Linux distributions explicitly when discussing prerequisites or environment setup.
- Provide guidance for running the awps-tunnel tool on Linux, including any permissions or dependency notes.
- Consider adding a table or section summarizing cross-platform differences, especially for environment setup and running servers.
- If possible, include screenshots or terminal outputs from both Windows and Linux environments to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/back-up-file-data.md
...e-docs/blob/main//articles/backup/back-up-file-data.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (such as Volume Shadow Copy Service, Data Deduplication, and the MABS console UI), and does not provide any Linux-specific instructions, examples, or parity guidance. There are no examples or clarifications for backing up or recovering data from Linux machines, nor is there mention of Linux agent installation or compatibility.
Recommendations
- Add explicit instructions and examples for backing up and recovering file data from Linux servers and clients, including any differences in agent installation and management.
- Clarify whether the MABS protection agent supports Linux, and if so, provide a section on deploying and managing the agent on Linux systems (including command-line examples).
- Include information about Linux-specific backup considerations (such as supported filesystems, snapshot mechanisms, and restore procedures).
- When referencing features like Data Deduplication or VSS, note their Windows-specific nature and provide Linux equivalents or clearly state if such features are unavailable.
- Ensure that all UI or wizard steps that differ for Linux machines are documented, or clarify if the process is identical.
- Add troubleshooting and FAQ sections for common Linux backup/recovery scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/back-up-managed-disks-tutorial.md
...ain//articles/backup/back-up-managed-disks-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation primarily focuses on Azure Portal UI steps and, where automation is mentioned, references PowerShell before CLI. There are no explicit Linux-specific examples or guidance, and PowerShell is mentioned before CLI in scripting contexts. The documentation does not provide parity for Linux users who may prefer Bash/CLI or scripting examples, nor does it mention Linux-specific considerations or tools.
Recommendations
- When referencing automation or scripting, mention Azure CLI before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux users.
- Provide explicit Bash/Azure CLI script examples for common tasks, not just PowerShell.
- Include Linux-specific notes or considerations where relevant (e.g., how to run CLI commands on Linux, or differences in authentication).
- Ensure that all links to scripting guides (such as backup/restore) are presented with equal prominence for both PowerShell and CLI.
- If screenshots or UI steps are OS-agnostic, clarify that the process is the same regardless of client OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-about-mars.md
.../blob/main//articles/backup/backup-azure-about-mars.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for the MARS Agent is heavily Windows-centric. All backup and recovery scenarios, process descriptions, and technical details refer exclusively to Windows systems, tools, and features (e.g., VSS, USN journal, Windows volumes, system state). There are no examples, instructions, or references for Linux systems or tools, and the documentation does not clarify if Linux is unsupported or simply omitted.
Recommendations
- Explicitly state the supported operating systems for the MARS Agent at the beginning of the documentation. If Linux is not supported, make this clear to avoid confusion.
- If Linux support is available or planned, add equivalent Linux examples, tools, and process descriptions alongside Windows instructions.
- Where Windows-specific technologies (like VSS, USN journal, system state) are mentioned, provide Linux equivalents or note their absence.
- Ensure that diagrams, tables, and process flows include Linux scenarios if supported, or clarify their Windows-only applicability.
- Consider adding a comparison table summarizing feature parity (or lack thereof) between Windows and Linux for Azure Backup solutions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-alternate-dpm-server.md
...//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 Data Protection Manager (DPM), which are Windows-only tools. All instructions, screenshots, and terminology are specific to the Windows ecosystem, with no mention of Linux-based recovery workflows, tools, or examples. There is no guidance for Linux administrators or parity in cross-platform scenarios.
Recommendations
- Include information on how Linux workloads can be protected and recovered using Azure Backup, if supported.
- If Linux recovery is not supported via Azure Backup Server/DPM, clearly state this limitation early in the documentation.
- Provide links or references to Linux-specific backup and recovery documentation within Azure Backup, such as for Azure Backup for Linux VMs or file recovery from Linux machines.
- Add a comparison table or section outlining platform support and differences in recovery workflows between Windows and Linux.
- If any command-line or scripting examples are included, provide both PowerShell (Windows) and Bash (Linux) equivalents where applicable.