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 1676-1700 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-query-graph.md
...lob/main//articles/digital-twins/how-to-query-graph.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides a tip specifically for Cloud Shell users about escaping the '$' character, but does not clarify whether this applies to Bash or PowerShell, nor does it provide equivalent Linux/Bash guidance. Additionally, the only SDK code examples are in C# (.NET), which is more commonly associated with Windows environments, and there are no examples for cross-platform languages (e.g., Python, JavaScript). There is no mention of Linux-specific tools or command-line usage, nor are Linux/Bash examples provided for running queries or interacting with the API.
Recommendations
- Clarify whether the Cloud Shell tip applies to Bash, PowerShell, or both, and provide explicit instructions for both environments.
- Add examples for running queries using cross-platform SDKs, such as Python or JavaScript, which are widely used on Linux.
- Include curl or HTTPie command-line examples for invoking the Query API directly from Linux/macOS terminals.
- If mentioning .NET/C# examples, balance by providing equivalent code snippets in other languages that are popular on Linux.
- Explicitly mention any platform-specific considerations for running queries or using SDKs on Linux vs. Windows.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md
...led-azure-vmware-solution-vsphere-resources-from-azure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows uninstall instructions before Linux, and the Windows uninstall steps use GUI-based tools (Control Panel), which are specific to Windows. While Linux instructions are present and reasonably detailed, the ordering and initial focus on Windows can be seen as a subtle Windows bias.
Recommendations
- Present Linux and Windows uninstall instructions in parallel or start with Linux to avoid implicit prioritization.
- For each step that has both Windows and Linux procedures, provide both side-by-side or in a tabbed format.
- Where possible, provide command-line alternatives for Windows (e.g., PowerShell or CMD commands to uninstall the agent), as is done for Linux, to ensure parity for automation and scripting.
- Explicitly mention that both Windows and Linux are supported at the beginning of relevant sections.
- Review other sections for similar ordering or tool biases and ensure equal treatment of both platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/sql-server-hybrid-benefit.md
...in//articles/azure-vmware/sql-server-hybrid-benefit.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
Although the page title and description mention Linux subscriptions, the content and examples focus exclusively on Windows Server and SQL Server scenarios. There are no concrete examples, instructions, or references for Linux workloads or how Azure Hybrid Benefit applies to Linux subscriptions. All migration and configuration guidance is centered on Windows-based technologies.
Recommendations
- Add specific examples and scenarios for applying Azure Hybrid Benefit to Linux subscriptions, such as supported Linux distributions and how to activate the benefit.
- Include migration guides or references for Linux workloads (e.g., migrating RHEL, SUSE, or Ubuntu VMs to Azure VMware Solution).
- Provide parity in 'Next steps' links by including Linux-focused documentation, such as configuring Linux clustering or license mobility for Linux VMs.
- Clarify in the main text how Azure Hybrid Benefit applies to Linux, including any differences or prerequisites compared to Windows/SQL Server.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/netapp-files-with-azure-vmware-solution.md
...zure-vmware/netapp-files-with-azure-vmware-solution.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Linux and Windows VMs in prerequisites and describes that Azure NetApp Files supports both SMB (Windows) and NFS (Linux) protocols. However, when it comes to practical guidance, there are no concrete examples or command lines for mounting shares on either platform. The only mention of mounting is for NFS on Linux, and even then, it is vague ('using the command lines or /etc/fstab entries') without providing actual commands or step-by-step instructions. There are no examples or instructions for mapping SMB shares on Windows VMs. The order of mention generally places Windows (SMB) before Linux (NFS), and the SMB share section is described before NFS in the 'Verify preconfigured Azure VMware Solution VM share mapping' section.
Recommendations
- Provide explicit, step-by-step examples for mounting NFS shares on Linux VMs, including sample mount commands and /etc/fstab entries.
- Add equivalent, detailed instructions for mapping SMB shares on Windows VMs, such as using 'net use' or mapping via File Explorer.
- Ensure that both Linux and Windows procedures are presented with equal detail and prominence, ideally in parallel sections or side-by-side.
- Avoid always listing Windows/SMB first; consider alternating or presenting both platforms together to reinforce parity.
- Include troubleshooting tips for both Linux and Windows clients to further support cross-platform usage.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-vmware/tutorial-configure-networking.md
...articles/azure-vmware/tutorial-configure-networking.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure Portal (GUI) instructions and does not provide any command-line examples for either Windows (PowerShell) or Linux (CLI). However, there is an implicit Windows bias because Azure documentation often defaults to PowerShell or Windows-centric tools when command-line examples are given, and this page does not proactively provide parity for Linux users (e.g., Azure CLI, Bash). Additionally, the absence of any mention of Linux tools or CLI commands means Linux users are left without direct guidance.
Recommendations
- Add Azure CLI (cross-platform) command-line examples for all major steps, such as creating virtual networks, gateways, and ExpressRoute connections.
- Explicitly mention that all steps can be performed using Azure CLI on Linux, macOS, or Windows, and provide links to relevant CLI documentation.
- If PowerShell examples are added in the future, ensure that equivalent Azure CLI/Bash examples are provided alongside.
- Consider including a section or callout for Linux/macOS users, highlighting any differences or additional considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-parse-models.md
...ob/main//articles/digital-twins/how-to-parse-models.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on the .NET parser library and provides only C# code examples, which are most commonly associated with Windows development. There are no examples or guidance for using the parser on Linux or with cross-platform tools, nor are alternative languages or environments mentioned. This creates a Windows-first impression and omits Linux parity.
Recommendations
- Include examples of using the DTDL parser library on Linux, such as with .NET Core/5+/6+ on Ubuntu or other distributions.
- Explicitly mention that the .NET parser library is cross-platform and provide instructions for installing .NET on Linux.
- Add code samples or command-line instructions that demonstrate usage on Linux (e.g., using dotnet CLI on Linux terminals).
- If possible, provide examples in additional languages supported by the DTDL parser (if available), or mention alternatives for non-Windows environments.
- Clarify that the C# code and .NET tools work on macOS and Linux as well as Windows, to avoid the impression of Windows exclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-send-twin-to-twin-events.md
...icles/digital-twins/how-to-send-twin-to-twin-events.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Summary
The documentation consistently lists Visual Studio (a Windows-centric IDE) before Visual Studio Code and Azure CLI in instructions for creating and publishing Azure Functions projects. There is a notable emphasis on Visual Studio workflows, and while cross-platform tools like VS Code and Azure CLI are mentioned, they are always secondary. There are no explicit Linux-only examples or guidance, and no mention of Linux-specific tools or shell environments.
Recommendations
- Alternate the order of instructions so that cross-platform tools like Azure CLI and Visual Studio Code are listed before Visual Studio, or present all options in parallel without preference.
- Explicitly mention that all CLI and VS Code instructions work on Linux and macOS, not just Windows.
- Add Linux shell (bash) command examples where relevant, especially for package management and project setup.
- Include a section or note highlighting Linux/macOS compatibility and any platform-specific considerations.
- Provide links to Linux/macOS-specific setup guides for Azure Functions development, if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/how-to-manage-model.md
...ob/main//articles/digital-twins/how-to-manage-model.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides code examples and instructions primarily for the .NET SDK (C#) and references to Visual Studio Code, but does not include any platform-specific command-line examples (such as PowerShell or Bash). However, it lacks Linux-specific or cross-platform command-line examples, such as Bash scripts or CLI usage from a Linux perspective. The documentation also references Visual Studio Code, which is cross-platform, but does not mention any Linux-specific tools or workflows. REST API and Azure CLI are mentioned, but no concrete CLI or shell examples are provided. The overall focus is on .NET/C# and general instructions, which can be interpreted as a subtle Windows-first bias due to the prevalence of .NET in Windows environments and the absence of Linux-oriented examples.
Recommendations
- Add explicit Bash or shell script examples for model management tasks (upload, retrieve, delete) using Azure CLI or curl, demonstrating usage on Linux.
- Provide equivalent code snippets in Python (using the Azure SDK for Python), which is popular on Linux, alongside the C# examples.
- Include instructions or examples for using the REST API with curl or httpie, common tools on Linux systems.
- Mention and demonstrate the use of cross-platform editors (such as nano, vim, or emacs) for editing DTDL JSON files, in addition to Visual Studio Code.
- Clarify that all SDK and CLI instructions are cross-platform, and explicitly state support for Linux and macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/tutorial-pub-sub-messages.md
...articles/azure-web-pubsub/tutorial-pub-sub-messages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally provides cross-platform instructions, but there are subtle Windows biases. Windows command shell alternatives are mentioned before or instead of Linux equivalents in some places, and Windows-specific tools or terminology (e.g., cmd.exe, 'set' vs 'export') are referenced. However, Linux/Bash instructions are present and primary in most code samples.
Recommendations
- When mentioning shell commands, present Bash/Linux and Windows alternatives side-by-side, or use tabs for each platform.
- Avoid stating 'You can use the Windows cmd.exe command shell instead of a Bash shell' at the top—clarify that all commands are cross-platform and provide explicit instructions for both where differences exist.
- In code sample run instructions, always show both 'export' (Linux/macOS) and 'set' (Windows) commands, or use tabs for each.
- For directory creation and navigation, prefer Bash syntax or provide both Bash and Windows (cmd.exe) equivalents in parallel.
- Ensure that all references to environment setup, activation of virtual environments, and dependency installation are equally clear for both Linux and Windows users.
- Consider adding a short section or table summarizing command differences between platforms for quick reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/azure-web-pubsub/tutorial-subprotocol.md
...ain//articles/azure-web-pubsub/tutorial-subprotocol.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally provides cross-platform instructions, with shell commands and code samples for C#, JavaScript, Python, and Java. However, in several places, Windows-specific tools (such as 'dir /s /b') are mentioned alongside or before their Linux equivalents ('ls -R'), and the documentation sometimes lists the Windows command first. There is also a reference to the .NET Secret Manager tool, which is specific to .NET Core and more common on Windows, though it is available cross-platform. No PowerShell-specific examples or exclusive Windows-only steps are present, and Linux examples are generally included, but Windows commands are sometimes prioritized or mentioned first.
Recommendations
- When listing equivalent commands (e.g., 'ls -R' and 'dir /s /b'), present the Linux/Unix command first or give both equal prominence, possibly in a table or side-by-side format.
- Clarify that .NET Secret Manager is available cross-platform, or provide alternative environment variable instructions for Linux/macOS users.
- Where possible, avoid phrases like 'Or call ... when you are using CMD under Windows' and instead use a neutral phrasing such as 'On Windows, use ...; on Linux/macOS, use ...'.
- If referencing Windows tools or patterns, always ensure the Linux/macOS equivalent is provided with equal detail and visibility.
- Consider adding explicit notes or tabs for Linux/macOS setup steps where platform-specific differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/azure-kubernetes-service-cluster-backup-using-cli.md
...p/azure-kubernetes-service-cluster-backup-using-cli.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is primarily focused on Azure CLI, which is cross-platform, but there is evidence of Windows bias in the use of PowerShell-style syntax for multi-line commands and the mention of Azure PowerShell as an alternative before any Linux-specific alternatives. The documentation uses backticks (`) for line continuation in command examples, which is a PowerShell/Windows convention and not compatible with Bash or other Unix shells. There are no Linux- or Bash-specific command examples or notes, and the only alternative tooling mentioned is Azure PowerShell, with no mention of Bash scripting or Linux-native tools.
Recommendations
- Provide Bash-compatible command examples for multi-line commands, using backslash (\) for line continuation instead of PowerShell backticks.
- When mentioning alternative tooling, include Bash or Linux-native options (if available), not just Azure PowerShell.
- Add notes or callouts clarifying any platform-specific syntax differences, especially for users on Linux or macOS.
- Ensure that all command examples are tested and work in Bash as well as PowerShell, or provide separate examples for each shell where necessary.
- Consider including a section or appendix on cross-platform usage tips for Azure CLI, highlighting differences between Windows (PowerShell/CMD) and Linux/macOS (Bash/zsh).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md
...rotection-use-rest-api-create-update-postgresql-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits a Windows bias by referencing PowerShell objects as the default representation for backup policy configuration. The only concrete example of a policy object is described as 'the default PowerShell object,' and PowerShell is mentioned as the primary way to conceptualize or instantiate backup policies. There are no references to Linux-native tools, shell commands, or cross-platform CLI usage, and no examples are provided for Linux or bash environments.
Recommendations
- Remove references to 'default PowerShell object' unless specifically discussing PowerShell usage. Instead, describe the policy object in a platform-neutral way.
- Add equivalent examples or explanations for Linux users, such as using curl or HTTPie to interact with the REST API.
- If scripting examples are provided, include both PowerShell and bash/curl equivalents to ensure parity.
- Clarify that the REST API can be used from any platform and provide sample commands for both Windows and Linux environments.
- Avoid implying that PowerShell is the default or only way to interact with the API; instead, present it as one of several options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-database-postgresql-troubleshoot.md
...ackup/backup-azure-database-postgresql-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Portal GUI steps and Azure CLI, with no mention of platform-specific tools or scripts. However, there is a subtle Windows bias: all screenshots and navigation instructions are based on the Azure Portal web interface, which is often more familiar to Windows users. There are no Linux-specific command-line examples (e.g., Bash scripts), nor is there any mention of Linux-native tools or workflows. Additionally, no PowerShell examples are present, but the absence of Linux/Bash parity (such as using az CLI in Bash or automation via shell scripts) suggests a lack of Linux-focused guidance.
Recommendations
- Add explicit Bash shell/terminal examples for relevant Azure CLI commands, demonstrating usage on Linux systems.
- Include notes or sections on how to perform key steps (e.g., role assignment, secret management) using Linux-native tools or scripts.
- Provide parity by showing both Azure Portal (GUI) and command-line (CLI) workflows, making it clear that all steps can be performed from Linux environments.
- If screenshots are used, consider including examples from both Windows and Linux environments (e.g., terminal windows, browser on Linux).
- Clarify that all CLI instructions are cross-platform and can be run on Linux, Mac, or Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-database-postgresql-overview.md
...es/backup/backup-azure-database-postgresql-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page does not display overt Windows bias in the form of PowerShell-heavy examples or Windows-first ordering, but it does show a lack of Linux parity by omitting command-line (psql, bash) examples and focusing exclusively on the pgAdmin GUI tool for database operations. There are no examples or references to Linux-native tools or workflows, which may disadvantage users who prefer or require CLI-based or Linux-native approaches.
Recommendations
- Include equivalent command-line examples using psql for granting privileges and managing users/databases, alongside the pgAdmin GUI instructions.
- Explicitly mention that all steps can be performed on Linux, and provide sample bash/psql commands where appropriate.
- Reference Linux-native tools (such as psql, or even Azure CLI on Linux) in addition to or instead of GUI-based tools.
- Add a section or callout for Linux/macOS users, clarifying any differences or additional steps required.
- Ensure screenshots and instructions are not solely focused on GUI tools that are more commonly used on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-encryption.md
...e-docs/blob/main//articles/backup/backup-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates subtle Windows bias by mentioning BitLocker (a Windows encryption tool) before DM-Crypt (the Linux equivalent) when describing Azure Disk Encryption. BitLocker is referenced by name, while DM-Crypt is mentioned secondarily. No Linux-specific examples or commands are provided, and the only detailed tool references are for Windows technologies.
Recommendations
- Present Linux and Windows encryption tools with equal prominence, e.g., 'ADE uses BitLocker for Windows VMs and DM-Crypt for Linux VMs' or list them together.
- Where possible, provide explicit examples or references for both Windows (BitLocker) and Linux (DM-Crypt) scenarios.
- Include links to documentation for both BitLocker and DM-Crypt to ensure parity.
- Review the order of presentation to avoid consistently listing Windows tools or workflows before Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-sql-manage-cli.md
...b/main//articles/backup/backup-azure-sql-manage-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the SQL Server instance is running on a Windows VM, as evidenced by the use of SQL Server (which is most commonly deployed on Windows in Azure VMs) and the use of resource/container names like 'mssqlserver' and 'testSQLVM'. There are no examples or notes addressing Linux-based SQL Server VMs, nor any mention of Linux-specific considerations, tools, or differences. All CLI examples use generic Azure CLI commands, but the context and naming conventions are Windows-centric, and there is no guidance for users managing SQL Server on Linux VMs.
Recommendations
- Explicitly state whether the instructions apply to both Windows and Linux SQL Server VMs, or clarify any limitations.
- Add a section or note describing any differences or prerequisites for managing SQL Server on Linux VMs (e.g., supported distributions, agent installation, firewall considerations).
- Provide at least one example using a Linux-based SQL Server VM, including naming conventions and any Linux-specific steps.
- If there are no differences, explicitly mention that the Azure CLI commands work identically for both Windows and Linux SQL Server VMs.
- Include links to documentation about running SQL Server on Linux in Azure VMs for further reference.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/includes/digital-twins-validate.md
...icles/digital-twins/includes/digital-twins-validate.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation focuses exclusively on a .NET/NuGet-based validation tool and C# code samples, which are more commonly associated with Windows development environments. There is no mention of Linux-compatible tools, alternative languages, or cross-platform usage instructions.
Recommendations
- Include instructions or examples for using the DTDLParser library on Linux (e.g., with .NET Core/.NET 6+ on Linux).
- Mention how to install and use the NuGet package manager on Linux systems.
- Provide sample code or command-line usage in languages and environments common on Linux (such as Python, Node.js, or Bash), or reference any available cross-platform tools.
- Explicitly state the cross-platform compatibility of the DTDLParser library, if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-rm-template-samples.md
...ob/main//articles/backup/backup-rm-template-samples.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists several Azure Resource Manager and Bicep templates for backup scenarios, but it demonstrates a Windows bias by specifically highlighting a 'Deploy Windows Server VM with backup enabled' template, while not providing an equivalent example for Linux VMs. There are no Linux-specific backup scenarios or templates mentioned, and the only OS-specific example is for Windows.
Recommendations
- Add examples and templates for deploying and backing up Linux VMs, such as 'Deploy Ubuntu VM with backup enabled' or similar.
- Ensure parity by including both Windows and Linux scenarios wherever OS-specific templates are provided.
- Review all sections for OS-specific language and provide Linux alternatives where appropriate.
- Consider adding a general note clarifying that templates can be adapted for both Windows and Linux, with links to relevant Linux documentation or templates.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/backup-azure-vms-enhanced-policy.md
...n//articles/backup/backup-azure-vms-enhanced-policy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell (Windows-centric) instructions and examples before CLI (cross-platform) equivalents. The PowerShell section is significantly more comprehensive, with step-by-step breakdowns and explanations, while the CLI section is more concise and lacks equivalent depth. There are no Linux-specific examples or references, and the documentation implicitly assumes familiarity with PowerShell and Windows tools.
Recommendations
- Provide equally detailed Azure CLI examples and explanations for all steps, matching the depth of the PowerShell section.
- Explicitly mention that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Add Bash shell usage examples where appropriate, especially for scripting or automation scenarios.
- Ensure that screenshots and UI references do not assume a Windows environment (e.g., avoid showing only Windows-style file paths or interfaces).
- Include a note or section for Linux users, highlighting any differences or considerations when using CLI or REST API.
- If PowerShell is required, clarify that PowerShell Core is available cross-platform and provide installation links for Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/digital-twins/includes/digital-twins-tutorial-sample-configure.md
...ns/includes/digital-twins-tutorial-sample-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation uses Windows-style path separators (backslashes) when referencing directories (e.g., 'digital-twins-samples-main\AdtSampleApp\SampleClientApp'), and does not provide Linux/macOS path equivalents. There are no explicit Linux or cross-platform instructions or examples.
Recommendations
- Provide both Windows (backslash) and Linux/macOS (forward slash) path examples when referencing directories.
- Explicitly mention that the instructions apply to all platforms, or note any platform-specific differences.
- If relevant, include Linux/macOS-specific steps or screenshots alongside Windows ones.
- Use neutral language such as 'navigate to digital-twins-samples-main/AdtSampleApp/SampleClientApp (on Linux/macOS) or digital-twins-samples-main\AdtSampleApp\SampleClientApp (on Windows)'.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/blob-backup-configure-tutorial.md
...ain//articles/backup/blob-backup-configure-tutorial.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 'Related content' section, and by referencing PowerShell-specific restore documentation. There are no explicit Linux or cross-platform command-line examples in the main tutorial, and the focus on PowerShell may suggest a preference for Windows tooling.
Recommendations
- List Azure CLI before or alongside Azure PowerShell in all sections to avoid implying a Windows-first approach.
- Ensure that all example commands and linked guides are provided for both Azure CLI (cross-platform) and Azure PowerShell.
- Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide parity in examples and walkthroughs.
- Wherever possible, include bash or shell script examples in addition to PowerShell.
- Audit included files (such as blob-backup-azure-portal-create-policy.md) to ensure they do not contain Windows-specific instructions or screenshots.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/create-manage-backup-vault.md
...ob/main//articles/backup/create-manage-backup-vault.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively describes how to create and delete Backup vaults using the Azure Portal, which is a graphical interface commonly associated with Windows environments. There are no CLI, PowerShell, or Bash examples provided, nor are there instructions for Linux users or those preferring command-line tools. This omission can be considered a 'missing_linux_example' and a subtle 'windows_first' bias, as the portal is often the default for Windows users.
Recommendations
- Add equivalent instructions for creating and deleting Backup vaults using Azure CLI (az), which is cross-platform and widely used on Linux.
- Include PowerShell examples for parity, but ensure CLI/Bash examples are presented alongside or before them.
- Provide links or references to REST API documentation for users who prefer automation or non-portal workflows.
- Explicitly mention that the Azure Portal is accessible from any OS, but highlight command-line alternatives for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/offline-backup-overview.md
.../blob/main//articles/backup/offline-backup-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references Microsoft Azure Backup Server (MABS), System Center Data Protection Manager (DPM), DPM-A, and the MARS Agent, all of which are Windows-based backup solutions. There are no mentions of Linux backup agents, Linux-compatible workflows, or examples for Linux environments. This suggests a bias toward Windows platforms and tools, with no guidance for Linux users.
Recommendations
- Explicitly state whether Linux-based backup agents or workflows are supported or not for offline backup scenarios.
- If Linux support exists, include equivalent Linux agent names, supported distributions, and step-by-step instructions or references for Linux environments.
- Provide examples or workflows that demonstrate how to perform offline backup from Linux servers, including any required tools or utilities.
- If Linux is not supported, clarify this limitation early in the documentation to set user expectations.
- Consider adding a comparison table row for OS/platform support to highlight any differences between Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/modify-vm-policy-cli.md
...ocs/blob/main//articles/backup/modify-vm-policy-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a file path example (C:\temp2\Policy.json) that is Windows-specific and does not mention or show a Linux/macOS equivalent. There are no Linux/Unix shell examples or file path formats, which may confuse or exclude users on non-Windows platforms.
Recommendations
- Include both Windows and Linux/macOS file path examples when referencing files (e.g., C:\temp2\Policy.json and /tmp/Policy.json).
- Add a note or section clarifying that the Azure CLI commands work cross-platform and provide examples for both environments.
- Where file manipulation is required, provide example commands for both PowerShell (Windows) and Bash (Linux/macOS) to save and edit JSON files.
- Avoid using only Windows-style paths in CLI examples; use generic or dual examples to ensure inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/backup/move-to-azure-monitor-alerts.md
.../main//articles/backup/move-to-azure-monitor-alerts.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments by referencing PowerShell and the Azure portal, but does not provide any Linux-specific examples or mention Linux command-line tools. The only command-line interface mentioned is PowerShell, and there are no CLI or REST API instructions, nor any Linux shell examples. The notification configuration is stated as only available via the Azure portal, with explicit mention that PS/CLI/REST API/ARM Template clients are not supported, which may disadvantage Linux users who prefer non-GUI workflows.
Recommendations
- Provide equivalent instructions or examples using Azure CLI (az), which is cross-platform and widely used on Linux.
- Include references to REST API and ARM Template methods for configuration, if/when they become available.
- Explicitly mention the parity (or lack thereof) for Linux users, and provide workarounds or alternatives where possible.
- If certain features are only available via the Azure portal, clarify if this is a temporary limitation and link to relevant feature requests or roadmap items.
- Add Linux shell (bash) examples for any command-line operations, even if only for related tasks (e.g., querying alerts, exporting data).