Sap
254
Total Pages
133
Linux-Friendly Pages
121
Pages with Bias
47.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
639 issues found
Showing 526-550 of 639 flagged pages
Sap
High availability for SAP HANA on Azure VMs on SLES
...n/articles/sap/workloads/sap-hana-high-availability.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is focused on deploying SAP HANA high availability on SUSE Linux Enterprise Server VMs in Azure. While the content and examples are almost entirely Linux-centric, there is evidence of Windows bias in the ordering and references within the SAP Notes section. Specifically, Windows is mentioned before Linux when listing supported OS and kernel versions, and Windows is referenced in the context of SAP kernel requirements. Additionally, the documentation references both Linux and Windows in the context of SAP kernel versions, even though the rest of the guide is exclusively for Linux. There are no PowerShell-heavy sections, and all technical examples, commands, and procedures are Linux-native (bash, crm, Pacemaker, etc.), with no missing Linux examples or preference for Windows tools in the actual deployment steps.
Recommendations
- Reorder SAP Notes and references so that Linux is mentioned before Windows, especially in lists and introductory sections, to reflect the Linux focus of the guide.
- Remove or minimize references to Windows kernel versions and requirements unless strictly necessary for context.
- Ensure that all examples, recommendations, and references are Linux-first and Linux-specific, unless the documentation is intended to be cross-platform.
- If Windows is mentioned for completeness, clearly separate Windows-specific information into its own section or appendix, rather than mixing it with Linux guidance.
Create Pull Request
Sap
High availability of SAP HANA scale-up with Azure NetApp Files on RHEL | Microsoft Docs
...ads/sap-hana-high-availability-netapp-files-red-hat.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is focused on SAP HANA high availability on RHEL (Linux) and provides Linux-centric instructions and examples throughout. However, there is minor evidence of Windows bias: Windows is mentioned in the prerequisites before Linux, and the documentation references SAP kernel version requirements for both Windows and Linux, listing Windows first. Additionally, the metadata includes 'devx-track-azurepowershell', and PowerShell instructions for load balancer configuration are included alongside Azure CLI and portal methods, even though the main scenario is Linux-based. No Linux examples are missing, and all technical steps and code samples are tailored for Linux/RHEL environments.
Recommendations
- In prerequisite sections, list Linux before Windows when the documentation is Linux-focused.
- Remove or de-emphasize PowerShell instructions unless they are directly relevant to Linux VM management; consider providing Bash or Azure CLI examples as primary options.
- Ensure that any references to Windows tools or patterns are clearly marked as out-of-scope for Linux deployments, or move them to a separate section for cross-platform scenarios.
- Review metadata tags to ensure Linux-centric documentation does not unnecessarily track Windows/PowerShell tooling unless required for hybrid environments.
Sap
Azure VMs high availability for SAP NetWeaver | Microsoft Docs
...les/sap/workloads/sap-high-availability-guide-start.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation consistently lists Windows/WSFC options before Linux equivalents in all major sections, and uses Windows-specific terminology and tooling (e.g., Windows Server Failover Cluster, shared disk, file share) as primary examples. While Linux options are present and covered, the ordering and emphasis suggest a Windows-first perspective. There is also a heavier focus on Windows-specific clustering technologies and visual assets, with Linux alternatives presented after.
Recommendations
- Alternate the order of Windows and Linux examples in each section, or group by scenario rather than OS, to avoid implicit prioritization.
- Ensure Linux clustering tools (e.g., Pacemaker, Corosync, SUSE HA, RHEL HA) are described with equal detail and visual representation as Windows tools.
- Add explicit statements that both Windows and Linux are equally supported and provide guidance for choosing between them based on workload or organizational preference.
- Include more cross-platform or Linux-first examples and diagrams, especially in introductory and summary sections.
- Review and balance the use of OS-specific icons and terminology to avoid reinforcing a Windows-centric view.
Sap
Virtual Machine Scale Sets for SAP workload
...oads/virtual-machine-scale-set-sap-deployment-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Virtual Machine Scale Sets for SAP workloads, but the PowerShell tab is present and detailed, which is a Windows-centric tool. There is no explicit Linux shell scripting example (e.g., Bash), and the CLI examples use variable syntax that is more familiar to Windows/PowerShell users than to Linux users. The documentation mentions support for both Windows and Linux VMs, but the configuration and scripting guidance leans toward Windows tools and patterns.
Recommendations
- Add explicit Bash shell examples for Linux users, using standard Bash variable syntax and command chaining.
- Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide guidance for installing and using Azure CLI on Linux.
- Where PowerShell is shown, also provide equivalent Bash scripts for parity.
- Include Linux-specific considerations or troubleshooting tips if any exist for SAP workloads on Azure VMSS.
- Review variable usage in CLI examples to ensure they are accessible and familiar to Linux users (e.g., use $RGName in PowerShell, but RGNAME in Bash).
Sap
Troubleshoot the Azure VM Extension for SAP | Microsoft Docs
.../sap/workloads/vm-extension-for-sap-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows troubleshooting steps before Linux, and refers to Windows-specific paths and tools (e.g., C:\Packages\Plugins\..., Windows process names) before their Linux equivalents. While Linux sections are present and reasonably complete, the ordering and initial focus on Windows may signal a subtle Windows bias.
Recommendations
- Alternate the order of Windows and Linux troubleshooting sections, or present them in parallel to avoid always prioritizing Windows.
- When referencing log file paths, process names, or installation directories, present both Windows and Linux equivalents side-by-side where possible.
- Ensure that all troubleshooting steps and error code solutions are equally detailed for both platforms.
- Consider using neutral language and structure (e.g., 'On Windows...' / 'On Linux...') to reinforce parity.
- If scripts or tools are mentioned, provide both PowerShell (Windows) and Bash (Linux) examples where applicable.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/archived-hli-docs/hana-certification.md
...arge-instances/archived-hli-docs/hana-certification.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page mentions Windows-centric tools and patterns, such as RDP servers and Active Directory, before or without mentioning Linux equivalents. While the solution itself is based on Linux (SUSE/Red Hat), examples and references to connectivity and management (e.g., RDP servers, Active Directory) are Windows-oriented, and there are no Linux-specific examples for remote access or directory services.
Recommendations
- Include Linux-native remote access examples, such as SSH jump hosts, alongside or before RDP servers.
- Mention Linux alternatives to Active Directory, such as LDAP or integration with Azure AD via Linux.
- Provide examples of Linux-based management and monitoring tools for SAP HANA on Azure.
- Ensure parity in documentation by listing both Windows and Linux approaches for common administrative tasks.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-ibm-db2.md
...ocs/blob/main/articles/sap/monitor/provider-ibm-db2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Azure portal and PowerShell quickstart as the only options for creating the Azure Monitor for SAP solutions resource, with no mention of Linux CLI or Bash alternatives. There are no Linux-specific instructions, examples, or tool references, and the workflow assumes a Windows-centric approach to Azure resource management.
Recommendations
- Include Azure CLI (az) commands for creating and managing the Azure Monitor for SAP solutions resource, as these are cross-platform and commonly used on Linux.
- Provide Bash or shell script examples alongside PowerShell, where applicable.
- Explicitly mention Linux support and provide steps for Linux users, such as using the Azure portal from a Linux browser or using CLI tools.
- Reference documentation for Linux environments and tools, ensuring parity with Windows instructions.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration-services.md
...in/articles/sap/workloads/rise-integration-services.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation repeatedly references the SAP .NET connector and the on-premises data gateway, both of which are Windows-centric technologies. There are no explicit examples, instructions, or mentions of Linux-based integration runtimes, connectors, or gateway deployments, despite the page targeting both Linux and Windows virtual machines. This creates a bias toward Windows tooling and leaves Linux users without clear guidance.
Recommendations
- Include examples and instructions for deploying self-hosted integration runtime and on-premises data gateway on Linux VMs.
- Mention Linux-compatible SAP connectors (e.g., SAP Java Connector, ODBC/JDBC) and provide guidance for their use.
- Clarify whether the on-premises data gateway and SAP .NET connector are supported on Linux, and if not, suggest Linux alternatives.
- Add Linux-specific architecture diagrams and workflow examples to match the Windows-centric ones.
- Ensure parity in troubleshooting and operational guidance for both Linux and Windows environments.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-webapp.md
.../blob/main/articles/sap/automation/configure-webapp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for app registration, but the Windows example appears after the Linux example, and both are given equal prominence. There is no exclusive use of Windows tools or patterns, and Linux instructions are present and complete. However, the PowerShell example is slightly more verbose and uses Windows-specific syntax, which may indicate a mild bias towards Windows users. The rest of the documentation is platform-neutral and does not favor Windows tools or patterns.
Recommendations
- Ensure that both Linux and Windows examples are equally detailed and accurate.
- Consider providing a short summary or table comparing the commands for both platforms at the top of the section for quick reference.
- Explicitly mention cross-platform compatibility for Azure CLI commands to reinforce parity.
- Review variable naming and file handling for consistency between platforms (e.g., manifest file path usage).
- If possible, add macOS-specific notes or examples to further broaden platform support.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-system.md
.../blob/main/articles/sap/automation/configure-system.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral and focuses on Azure infrastructure and SAP deployment automation, with a strong emphasis on Linux-based deployments (SUSE, RHEL). However, there is some evidence of Windows bias: Windows failover clustering is mentioned as a high-availability option before Pacemaker, and Windows license types are listed in the licensing section. There are no explicit PowerShell examples or Windows-only configuration patterns, but Windows is referenced alongside Linux in certain contexts, sometimes appearing first or as an alternative to Linux tools.
Recommendations
- When mentioning high-availability options, list Pacemaker (Linux) before Windows failover clustering, or present both equally.
- In licensing sections, list Linux license types first or present all options in alphabetical order.
- If Windows-specific options (e.g., failover clustering) are mentioned, ensure equivalent Linux options (e.g., Pacemaker) are described with equal detail and prominence.
- Add explicit examples for both Linux and Windows configurations where relevant, or clarify when a feature is platform-specific.
- Review all tool and pattern references to ensure Linux and Windows are treated with parity, and avoid implying Windows is the default or primary platform.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/deploy-system.md
...ocs/blob/main/articles/sap/automation/deploy-system.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Windows and Linux deployment instructions in parallel, but the Windows example uses a custom PowerShell cmdlet (New-SAPSystem), while the Linux example uses a shell script. The Windows instructions are listed before Azure DevOps, and both platforms receive similar coverage. However, the use of a specialized PowerShell cmdlet for Windows may suggest a more streamlined or supported experience on Windows. There is no explicit mention of Linux-specific tools or parity for the PowerShell cmdlet functionality.
Recommendations
- Clarify whether the PowerShell cmdlet (New-SAPSystem) has a direct Linux equivalent or provide a cross-platform CLI tool for parity.
- Ensure that both Linux and Windows instructions use similarly supported and documented automation methods (e.g., both using scripts or both using platform-native commands).
- If the PowerShell cmdlet offers additional features or ease of use, consider providing a Bash or Python wrapper for Linux users.
- Explicitly mention any differences in deployment experience or tooling between Windows and Linux, and provide guidance for Linux users to achieve equivalent functionality.
- Consider listing Linux instructions before Windows to avoid implicit prioritization.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/run-ansible.md
...-docs/blob/main/articles/sap/automation/run-ansible.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux and Windows examples for all major steps, using tabbed sections for parity. However, there is evidence of Windows bias in the ordering and tool references: Windows tasks and tooling (such as DSC modules and Windows Failover Clustering) are listed before their Linux equivalents (such as Pacemaker), and Windows-specific configuration modules are named explicitly while Linux equivalents are described more generically. In some cases, Windows tooling is mentioned in more detail than Linux alternatives.
Recommendations
- Ensure that Linux and Windows instructions are presented in a consistent order (e.g., Linux first if it is the more common SAP platform).
- Provide equivalent detail for Linux tooling (e.g., list specific Linux configuration modules or packages used, such as 'lvm2', 'systemd', 'sudolog', etc., similar to the Windows DSC modules).
- Where possible, mention Linux high-availability solutions (e.g., Pacemaker) before or alongside Windows solutions, and provide links or references for both.
- Review all task lists to ensure that Linux and Windows steps are described with equal specificity and clarity.
- Consider adding a summary table comparing Linux and Windows approaches for key configuration steps to help users understand platform differences and parity.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/manual-deployment.md
...blob/main/articles/sap/automation/manual-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform and uses Bash/Azure CLI examples suitable for Linux and Azure Cloud Shell. However, there is evidence of Windows bias in the SSH client instructions, where PuTTY (a Windows SSH client) is mentioned as the example, and conversion to .ppk format is described. No Linux SSH client (e.g., OpenSSH, ssh command) is referenced in this section. Additionally, the file upload/download instructions reference the Azure Cloud Shell menu, which is more familiar to Windows users, and do not mention equivalent Linux command-line alternatives (e.g., scp, rsync).
Recommendations
- Include instructions for using Linux-native SSH clients (e.g., OpenSSH) alongside PuTTY, and provide examples for both platforms.
- Mention how to use scp or rsync for file transfers in addition to the Azure Cloud Shell menu upload/download feature.
- Where Windows-specific tools or formats (e.g., .ppk for PuTTY) are mentioned, also describe the Linux equivalents (e.g., using the private key directly with ssh).
- Clarify that all CLI examples work on both Linux and Windows (with WSL or Azure Cloud Shell), and note any platform-specific differences where relevant.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/deploy-s4hana.md
...ain/articles/sap/center-sap-solutions/deploy-s4hana.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell-only example for listing Azure Marketplace images, with no equivalent CLI (az), Bash, or Linux-native command example. This could disadvantage Linux users, who are the primary audience for S/4HANA on Azure, as the supported OSes are all Linux distributions. No Windows-specific tools or patterns are otherwise emphasized, but the lack of Linux/CLI parity in code samples is a notable bias.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all Azure operations, especially for listing VM images.
- Explicitly mention that both PowerShell and CLI can be used, and link to relevant documentation for both.
- If possible, include Bash shell usage examples, as Linux users are likely to use Bash.
- Review all code snippets and ensure Linux-friendly alternatives are always present when PowerShell is shown.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/archived-hli-docs/hana-example-installation.md
...stances/archived-hli-docs/hana-example-installation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing only Windows-based examples for downloading SAP HANA installation packages to the jump box, despite the service targeting Linux virtual machines. There are no Linux-based instructions or examples for this critical step, and Windows is mentioned explicitly as the operating system in the example. The remainder of the installation steps correctly focus on Linux, but the initial example may confuse or disadvantage Linux users.
Recommendations
- Provide equivalent Linux-based instructions and examples for downloading SAP HANA installation packages to the jump box, such as using wget, curl, or SAP's download manager on a Linux VM.
- Clarify that the jump box can be either Windows or Linux, and offer guidance for both platforms.
- Ensure screenshots and commands reflect both Windows and Linux environments where applicable.
- Review the documentation for other steps that may implicitly assume Windows usage and update for Linux parity.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/get-started.md
...e-docs/blob/main/articles/sap/workloads/get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates some Windows bias, primarily through the explicit mention of Windows clustering and Windows failover cluster tools before or alongside Linux equivalents (Pacemaker). Windows-specific scenarios, such as SQL Server on Windows and Windows failover clustering, are referenced in both the main text and the change log. However, Linux platforms (SLES, RHEL) and tools (Pacemaker) are also well-represented, especially in high availability and automation sections. There is a tendency to mention Windows solutions and tools first or with more detail, and some examples or guides are Windows-specific without always providing equivalent Linux instructions.
Recommendations
- Ensure that every Windows-specific example or guide has a Linux equivalent, especially for common scenarios like clustering, storage configuration, and identity integration.
- Present Linux and Windows options in parallel, rather than listing Windows first or exclusively.
- Expand automation and deployment examples to include Linux-native tools and scripts where possible.
- Where Windows tools (e.g., failover clustering, PowerShell) are referenced, provide links or instructions for Linux alternatives (e.g., Pacemaker, shell scripts).
- Review documentation for subtle ordering bias (Windows-first) and alternate the order or group by scenario rather than OS.
- Add explicit parity statements to assure users that Linux is fully supported and provide cross-references between Windows and Linux guides.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel-ibm-db2-luw.md
.../workloads/high-availability-guide-rhel-ibm-db2-luw.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is focused on deploying IBM Db2 HADR on Azure VMs running Red Hat Enterprise Linux and provides Linux-centric instructions and examples throughout. However, there are instances of Windows bias: references to Windows documentation and terminology appear before Linux equivalents in some places (e.g., availability set documentation links to Windows first), and Azure-specific tooling and patterns (such as Azure Load Balancer) are described in a way that sometimes references Windows resources or documentation before Linux ones. There are also mentions of Azure Marketplace images for RHEL for SAP, but no equivalent mention of Windows images, which is appropriate for the Linux focus. There is no evidence of PowerShell-heavy examples or missing Linux examples; all command-line instructions use Linux tools and syntax.
Recommendations
- Ensure that all cross-references to Azure documentation use Linux-first or Linux-specific links when the context is Linux (e.g., link to /azure/virtual-machines/linux/tutorial-availability-sets instead of /azure/virtual-machines/windows/tutorial-availability-sets).
- When mentioning Azure tools or features (such as Load Balancer), clarify Linux-specific configuration steps and avoid referencing Windows terminology unless directly relevant.
- Review any included tabs or code snippets for Azure CLI, PowerShell, and Portal to ensure Linux parity and that Linux examples are presented first or most prominently.
- Audit all external documentation links to ensure they point to Linux-relevant content when the page is Linux-focused.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel-nfs-azure-files.md
...kloads/high-availability-guide-rhel-nfs-azure-files.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on deploying SAP NetWeaver high availability on RHEL with NFS on Azure Files, and is overall Linux-centric. However, there is minor evidence of Windows bias: Windows is mentioned in the prerequisites (SAP kernel version for Windows and Linux), and PowerShell is included as a tab for load balancer configuration before Linux CLI. The documentation also references Azure tools and patterns that are cross-platform but sometimes lists Windows options (PowerShell) alongside Linux ones (Azure CLI), with PowerShell not always being relevant for Linux-only deployments.
Recommendations
- Remove or de-emphasize references to Windows and PowerShell in contexts where the guide is strictly for Linux (RHEL) deployments.
- Ensure Linux-native tools (Azure CLI, Bash scripts) are listed first and are the default in code examples and instructions.
- Clarify in the prerequisites and tool selection sections that PowerShell is not required for Linux deployments, and provide explicit Linux-only instructions where possible.
- Review all example tabs and remove PowerShell options unless there is a clear cross-platform scenario.
- Where Windows is mentioned in prerequisites, split out Linux-specific requirements to avoid confusion.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-standard-load-balancer-outbound-connections.md
...lity-guide-standard-load-balancer-outbound-connections.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is focused on SAP high-availability scenarios using Azure VMs and Standard Load Balancer, but it demonstrates a Windows bias in several ways. The page's metadata, service tags, and deployment instructions are oriented toward Windows (e.g., 'virtual-machines-windows', 'ms.tgt_pltfrm: vm-windows'), and Azure portal GUI instructions are given, which are more familiar to Windows users. There are no explicit Linux CLI examples for infrastructure setup (e.g., using Azure CLI or ARM templates from Linux), and the only Linux-specific configuration is for Pacemaker proxy settings, which is limited to the proxy scenario. The main infrastructure steps (load balancer, firewall, NSG) lack Linux-centric command-line examples, and the documentation does not mention Linux tools or patterns for these tasks.
Recommendations
- Add Linux-specific Azure CLI and/or ARM template examples for all deployment steps (e.g., creating load balancers, backend pools, NSGs, firewalls, routes).
- Include references to Linux command-line tools and scripting patterns for managing Azure resources, such as using bash scripts or automation via cloud-init.
- Balance the portal-based instructions with CLI-based instructions that are platform-agnostic and suitable for Linux administrators.
- Clarify that all steps can be performed from Linux environments and provide guidance for Linux users where relevant.
- Consider updating metadata and service tags to reflect Linux parity (e.g., include 'virtual-machines-linux' in services and platform targeting).
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse-nfs-azure-files.md
...kloads/high-availability-guide-suse-nfs-azure-files.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is focused on deploying SAP NetWeaver high availability on SUSE Linux Enterprise Server (SLES) with NFS on Azure Files, and provides detailed Linux-centric instructions and examples. However, there are minor signs of Windows bias: Windows services are listed in the metadata ('virtual-machines-windows'), and Windows prerequisites are mentioned before Linux equivalents in the prerequisites section. Additionally, PowerShell is included as a tab for load balancer configuration, even though the main scenario is Linux-based. No Linux examples are missing, and all technical steps are shown with Linux commands.
Recommendations
- Remove or deprioritize references to Windows services in the metadata when the guide is Linux-specific.
- List Linux prerequisites before Windows ones, or separate them clearly by platform.
- Consider removing or moving PowerShell examples to a separate section or appendix, making Linux (Azure CLI, bash) the default for this scenario.
- Ensure that any cross-platform tooling (e.g., Azure CLI, PowerShell) is presented with Linux-first examples when the guide is for Linux workloads.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse.md
...articles/sap/workloads/high-availability-guide-suse.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is focused on deploying SAP NetWeaver high availability on SUSE Linux Enterprise Server, with all configuration and operational examples using Linux-native tools and commands. However, there is evidence of Windows bias in the metadata, service tags, and ordering of information: Windows services are listed first in the metadata, and references to Windows and Linux support in SAP Notes often mention Windows before Linux. Additionally, PowerShell is included as a tab for load balancer configuration, and some cross-platform Azure tools (Azure CLI, PowerShell, Portal) are presented, but Linux-specific CLI examples are not prioritized over Windows tools.
Recommendations
- In metadata and service tags, list Linux-related services and subservices before or alongside Windows equivalents to reflect the Linux focus of the guide.
- When referencing SAP Notes or supported platforms, mention Linux before Windows when the guide is Linux-centric.
- For Azure resource configuration, prioritize Azure CLI and Linux shell examples over PowerShell, or provide Linux-specific CLI examples first.
- Remove or de-emphasize PowerShell tabs/examples unless strictly necessary for Linux users, or clarify when PowerShell is applicable on Linux.
- Ensure that all example commands and scripts are tailored for Linux environments, and avoid referencing Windows tools unless providing explicit cross-platform guidance.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-start.md
...les/sap/workloads/sap-high-availability-guide-start.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows/WSFC scenarios and guides before Linux equivalents in all major sections. The use of Windows-specific terminology (e.g., 'Windows Server Failover Cluster', 'shared disk', 'file share') is prominent, while Linux solutions are described more generically as 'Linux Cluster Framework'. The page also references Windows-specific tools and patterns (WSFC, file share, shared disk) before Linux alternatives (Pacemaker, GlusterFS, NFS). However, Linux examples and guides are present and reasonably detailed, so Linux support is not missing, just secondary.
Recommendations
- Alternate the order of Windows and Linux sections/examples to avoid always listing Windows first.
- Use parallel terminology for Linux solutions (e.g., mention Pacemaker, Corosync, DRBD, NFS explicitly alongside WSFC, file share, shared disk).
- Provide equal visual prominence (logos, formatting) for Linux and Windows options.
- Ensure that Linux-specific tools and patterns are described with the same level of detail as Windows ones.
- Consider a summary table or matrix that presents Windows and Linux options side-by-side for easier parity comparison.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration.md
...s/blob/main/articles/sap/workloads/rise-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes integrating SAP RISE with Azure, but the examples and references in the 'First steps' section focus on Microsoft-centric tools (Power App, Power BI, Entra ID, Sentinel) without mentioning Linux-specific integration scenarios or tools. Although the page is tagged for both Linux and Windows VMs, there are no explicit Linux command-line examples, nor references to Linux-native tools or patterns. Windows-oriented services and terminology are presented first and exclusively.
Recommendations
- Add Linux-specific integration examples, such as connecting SAP RISE with Azure using Linux command-line tools (e.g., Azure CLI, SSH, Linux-based firewalls).
- Include references to open-source or Linux-native solutions for identity management, monitoring, and data integration (e.g., Keycloak, Prometheus, Grafana, Linux-based ETL tools).
- Provide parity in documentation by offering both Windows and Linux workflows for common tasks (e.g., network peering, SSO setup, data gateway configuration).
- Explicitly mention Linux VM scenarios in example lists and link to relevant guides.
- Ensure that Linux tools and patterns are presented alongside or before their Windows equivalents where appropriate.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-high-availability.md
...n/articles/sap/workloads/sap-hana-high-availability.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is focused on SAP HANA high availability on SUSE Linux Enterprise Server and provides extensive Linux-specific instructions and examples. However, there is evidence of Windows bias in the SAP Notes section, where Windows is mentioned before Linux in the context of supported SAP kernel versions. Additionally, references to Windows are present in SAP documentation links and prerequisites, and Windows is listed alongside Linux in some compatibility notes. The load balancer configuration section provides examples for Azure Portal, Azure CLI, and PowerShell, but does not prioritize PowerShell or Windows-specific tooling over Linux equivalents. Overall, the documentation is strongly Linux-centric, but minor Windows-first ordering and tool mentions are present.
Recommendations
- In SAP Notes and compatibility sections, mention Linux before Windows, or present both equally to avoid Windows-first ordering.
- Where Windows is referenced, ensure Linux equivalents are also mentioned and described with equal detail.
- Review all prerequisite and compatibility lists to ensure Linux is not secondary to Windows in ordering or emphasis.
- If Windows tools (e.g., PowerShell) are mentioned, ensure Linux-native tools (e.g., Bash, Azure CLI) are presented first or equally.
- Remove unnecessary references to Windows in a Linux-focused guide, unless directly relevant for mixed environments.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/troubleshooting.md
...s/blob/main/articles/sap/automation/troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by omitting explicit Linux examples and commands, and by referencing tools and troubleshooting steps that are either platform-neutral or implicitly Windows-centric (e.g., agent VM, Azure Cloud Shell, Ansible upgrade instructions without OS-specific guidance). There are no PowerShell-specific commands, but the lack of Linux-specific troubleshooting, commands, or environment variable handling suggests a Windows-first approach.
Recommendations
- Include explicit Linux shell (bash) examples alongside any Azure CLI or troubleshooting steps.
- Provide guidance for upgrading Ansible on both Windows and Linux agents, including package manager commands (e.g., apt, yum, pip).
- Clarify agent VM requirements and setup for both Windows and Linux environments.
- Add troubleshooting steps for common Linux-specific issues (e.g., file permissions, environment variable export differences).
- Ensure references to Azure Cloud Shell or CLI usage are accompanied by notes on platform compatibility and alternative commands for Windows and Linux.