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 501-525 of 639 flagged pages
Sap
Get started with SAP on Azure VMs | Microsoft Docs
...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 provides a broad overview of SAP on Azure VMs, mentioning both Windows and Linux platforms. However, there is evidence of Windows bias: Windows tools and technologies (such as Windows Failover Clustering, SQL Server, and Microsoft Entra ID) are referenced explicitly and sometimes before their Linux equivalents. In the 'You want to know' section, Windows-specific scenarios and limitations are listed before Linux ones, and Windows clustering is mentioned alongside Pacemaker but not always with equal detail. The documentation also includes several references to Windows-specific high availability guides and tools, sometimes without parallel Linux examples or with Windows scenarios listed first.
Recommendations
- Ensure that Linux tools and patterns (such as Pacemaker, systemd, and Linux-based clustering) are mentioned with equal prominence and detail as Windows equivalents.
- Where Windows-specific examples or guides are provided, include parallel Linux examples (e.g., for RHEL, SLES, Oracle Linux) in the same context.
- Avoid listing Windows scenarios or tools before Linux ones unless there is a technical reason; consider alternating or grouping by platform.
- Review all sections (especially 'You want to know' and documentation area summaries) to ensure Linux solutions are not omitted or treated as secondary.
- Add explicit cross-references to Linux guides wherever Windows guides are mentioned, and vice versa.
Create Pull Request
Sap
Azure Virtual Machines HA for SAP NW on RHEL with Azure NetApp Files| Microsoft Docs
...workloads/high-availability-guide-rhel-netapp-files.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is focused on SAP NetWeaver HA deployment on RHEL (Linux) and provides extensive Linux-specific instructions and examples. However, there is evidence of Windows bias in the prerequisites section, where Windows is mentioned before Linux in the context of supported SAP kernel versions. Additionally, Windows tools (such as PowerShell) are referenced in the load balancer configuration section, with PowerShell examples provided alongside Azure CLI and portal instructions, even though the main scenario is Linux-based.
Recommendations
- In the prerequisites, mention Linux before Windows when listing supported SAP kernel versions, as the guide is Linux-focused.
- In sections where PowerShell is referenced, clarify that PowerShell is primarily for Windows users and provide equivalent Bash or Linux-native scripting alternatives where possible.
- Consider removing or relegating Windows-specific references to footnotes or separate sections, ensuring Linux instructions are always primary and complete.
- Ensure that all example commands, especially for infrastructure setup and configuration, are provided in Bash or Linux-native tools first, with Windows/PowerShell equivalents only if relevant for mixed environments.
- Review all cross-references and links to ensure Linux documentation is prioritized and clearly separated from Windows content.
Sap
Deploy SAP dialog instances with SAP ASCS/SCS high-availability VMs on RHEL | Microsoft Docs
...s/high-availability-guide-rhel-with-dialog-instance.md
Medium Priority
View Details →
Detected Bias Types
Windows Reference
Windows Tools
Summary
The documentation is focused on deploying SAP dialog instances on RHEL and provides Linux-centric instructions and examples throughout. However, there are minor references to Windows, such as mentioning required SAP kernel versions for Windows and Linux, and referencing SAP Notes that include Windows information. There are no Windows-specific examples, tools, or PowerShell commands given, and all operational guidance is for Linux (RHEL) environments. The documentation does not exhibit Windows-first ordering, nor does it omit Linux examples.
Recommendations
- Ensure that any references to Windows in SAP Notes are clearly separated from Linux instructions, or provide explicit guidance for Linux users.
- If Windows-specific information is mentioned, consider providing parallel Linux details to maintain parity.
- Continue to avoid Windows/Powershell examples unless the documentation is intended to be cross-platform; otherwise, keep the focus on Linux tools and patterns as appropriate for the audience.
Sap
Public endpoint connectivity for Azure VMs&Standard ILB in SAP HA scenarios
...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 titled and scoped for Windows VMs, but the actual configuration examples and instructions focus on SAP high-availability scenarios using Pacemaker for SUSE/RHEL (Linux). However, the page metadata, service tags, and initial context are Windows-centric, and there are no equivalent instructions or examples for Windows clustering or Windows-based SAP deployments. All step-by-step configuration examples (proxy, outbound connectivity) are provided only for Linux (SUSE/RHEL), with no PowerShell or Windows Server guidance.
Recommendations
- Update the page title and metadata to clarify that the instructions are for Linux (SUSE/RHEL) SAP clusters, or add equivalent sections for Windows Server-based SAP deployments.
- Provide examples for configuring outbound connectivity for SAP on Windows VMs, including PowerShell commands and Windows-specific networking tools.
- If Windows clustering (e.g., Windows Failover Cluster) is supported for SAP on Azure, include configuration steps and outbound connectivity guidance for those scenarios.
- Ensure parity in troubleshooting, deployment, and security group configuration examples for both Linux and Windows platforms.
- Explicitly state platform applicability at the top of the document to avoid confusion for Windows administrators.
Sap
Azure VMs high availability for SAP NetWeaver on SLES | Microsoft Docs
...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, and all technical examples, configuration steps, and scripts are Linux-centric. However, there is evidence of Windows bias in the following ways: Windows is mentioned first in several places (e.g., in the list of supported OSes and services), and Windows-specific tools and services (such as Azure Virtual Machines for Windows and Azure PowerShell) are referenced before or alongside Linux equivalents, even though the guide is for SLES. Additionally, the metadata and service tags include 'virtual-machines-windows' and 'devx-track-azurepowershell', which may suggest a prioritization of Windows tooling.
Recommendations
- Reorder mentions of operating systems so that Linux is listed first, especially in documentation focused on Linux deployments.
- Remove or de-emphasize Windows-specific service tags and metadata when the content is exclusively for Linux.
- Ensure that Linux tools (Azure CLI, Bash, etc.) are presented before Windows tools (PowerShell) in all example sections and tabs.
- Review referenced SAP Notes and documentation links to ensure Linux-relevant content is prioritized or highlighted.
- Consider removing references to Windows services and tools unless they are directly relevant to the Linux deployment scenario.
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 in Azure and is overall Linux-centric. However, there is evidence of Windows bias in the ordering and references: Windows is mentioned first in some SAP Notes (e.g., kernel versions for Windows and Linux), and Windows tools/versions are referenced before Linux equivalents. There are also references to Windows in supported OS combinations and kernel versions, even though the guide is for SLES. The load balancer configuration examples are provided for Azure Portal, Azure CLI, and PowerShell, but PowerShell is listed after CLI and Portal, and all Linux configuration steps use native Linux tools. No PowerShell-heavy or missing Linux example bias is present.
Recommendations
- In SAP Notes and prerequisites, list Linux before Windows when both are mentioned, especially in Linux-focused documentation.
- Where Windows kernel versions or tools are referenced, ensure Linux equivalents are equally or more prominently described.
- If mentioning Windows tools or patterns, always provide the Linux equivalent first or exclusively in Linux-centric guides.
- Review the ordering of example tabs (Portal, CLI, PowerShell) to ensure CLI (Linux) is listed first in Linux documentation.
- Remove or minimize references to Windows-specific details unless directly relevant to the Linux deployment scenario.
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 page demonstrates a Windows bias by consistently listing Windows/WSFC scenarios and guides before Linux equivalents in all major sections. Windows-specific tools and terminology (e.g., Windows Server Failover Cluster, shared disk, file share) are highlighted and described first, while Linux solutions (SUSE, RHEL, Pacemaker, GlusterFS) appear later in each list. There are no explicit PowerShell examples or missing Linux examples, but the ordering and emphasis favor Windows environments.
Recommendations
- Alternate the order in which Windows and Linux examples/guides are presented, or group them by scenario rather than OS to avoid implicit prioritization.
- Provide equal detail and visibility for Linux-specific tools and frameworks (e.g., Pacemaker, GlusterFS, SUSE cluster framework) in summaries and introductions.
- Ensure that visual elements (logos, icons) and terminology are balanced between Windows and Linux, avoiding repeated emphasis on Windows-specific technologies.
- Consider adding a parity table or matrix summarizing both Windows and Linux options side-by-side for each scenario.
- Explicitly state that both Windows and Linux are fully supported and provide links to Linux documentation with the same prominence as Windows links.
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 configuration examples for Azure portal, Azure CLI, and Azure PowerShell, with PowerShell given equal prominence to CLI and portal. There is a slight Windows bias in the ordering and presentation: PowerShell examples are included and labeled as a primary method, and the page metadata references 'azurepowershell'. However, Linux-specific tools (such as Bash scripts or cloud-init) are not mentioned, and there are no Linux-first examples. The CLI examples are cross-platform, but the documentation does not explicitly highlight Linux usage or provide Linux-centric guidance. The only explicit Linux reference is in the quick start guide link at the end, which is not integrated into the main workflow.
Recommendations
- Add explicit Linux/Bash scripting examples for scale set creation, demonstrating usage in a native Linux environment.
- Clarify that Azure CLI commands are cross-platform and can be run natively on Linux, macOS, and Windows.
- Include references to Linux automation tools (e.g., cloud-init, Ansible) for VM configuration within scale sets.
- Reorder examples to present CLI (cross-platform) first, followed by PowerShell (Windows-centric), to reduce perceived Windows-first bias.
- Expand the quick start section to include Linux-specific configuration steps and troubleshooting tips.
- Mention and link to Linux documentation and best practices for SAP workloads on Azure in the main body, not just in the quick start.
Sap
Prepare Bill of Materials for automation
...-docs/blob/main/articles/sap/automation/bom-prepare.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation demonstrates a bias towards Linux environments. All command-line examples use bash scripts, and validation steps require Linux-type commands (yamllint, ansible-lint). Windows users are only briefly mentioned, with instructions to use Windows Subsystem for Linux (WSL), but no native Windows or PowerShell examples are provided. There are no references to Windows-native tools or workflows, and Linux commands are presented as the default throughout.
Recommendations
- Add PowerShell examples for BOM creation and validation, such as using PowerShell scripts to run equivalent checks.
- List Windows-native tools (e.g., Notepad++, Windows YAML editors, or Windows-based linters) as alternatives in prerequisites.
- Provide explicit instructions for Windows users who do not wish to use WSL, including how to install and use yamllint/ansible-lint on Windows or suggest comparable Windows tools.
- Include a section or callouts for Windows-specific workflows, such as using Windows Explorer for file navigation and manipulation.
- Ensure that both Linux and Windows command examples are presented side-by-side where applicable.
Sap
Configure a Deployer Web Application for SAP on Azure Deployment Automation Framework
.../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. The PowerShell example uses Windows-specific syntax and variable handling, which may be less familiar to Linux users. However, both platforms are represented, and Azure CLI is used in both cases. No exclusive mention of Windows tools or missing Linux examples is found, but the Windows example is more verbose and uses Windows-centric patterns.
Recommendations
- Ensure that both Linux and Windows examples are equally detailed and use similar variable naming conventions for clarity.
- Consider providing a brief explanation of differences between bash and PowerShell commands for users unfamiliar with one platform.
- Add explicit notes about platform parity and encourage users to select the appropriate tab for their environment.
- Where possible, use cross-platform commands (e.g., Azure CLI) and minimize platform-specific scripting unless necessary.
Sap
Configure SAP system parameters for automation
.../blob/main/articles/sap/automation/configure-system.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias. Windows-specific technologies (e.g., Windows failover clustering) are mentioned as high-availability options alongside Linux equivalents (Pacemaker), but Windows is listed first in those cases. The 'license_type' parameter lists Windows options after Linux, but otherwise, examples and configuration snippets focus on Linux (SUSE, RHEL) and do not provide PowerShell or Windows-specific configuration samples. No Linux examples are missing, and Linux is well represented throughout.
Recommendations
- When listing high-availability options, alternate the order or explicitly state parity between Windows and Linux solutions.
- Provide configuration examples for both Windows and Linux deployments where applicable, especially for parameters like VM image definitions.
- Include references or links to Windows-specific documentation (e.g., configuring Windows failover clustering in SAP on Azure) to ensure parity.
- Clarify in notes or tables which parameters or patterns are applicable to Windows, Linux, or both, to avoid implicit prioritization.
- Where command-line examples are given (e.g., Azure CLI), consider including PowerShell equivalents for Windows administrators.
Sap
SAP system deployment for the automation framework
...ocs/blob/main/articles/sap/automation/deploy-system.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Linux and Windows deployment instructions, 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 the PowerShell cmdlet is more specialized than the generic shell script. There is a slight bias toward Windows in terms of tooling and presentation order.
Recommendations
- Provide parity in tooling: If a custom PowerShell cmdlet is offered for Windows, consider providing an equivalent CLI or shell script for Linux users, or document how to use the shell script with similar parameters.
- Ensure example parity: Make sure both Linux and Windows examples are equally detailed and use similar workflows (e.g., both using scripts or both using platform-native tools).
- Order examples neutrally: Alternate or randomize the order of platform-specific instructions, or present Linux and Windows instructions side-by-side to avoid implicit prioritization.
- Highlight cross-platform compatibility: Clearly state which tools/scripts are available for both platforms and provide guidance for users on each OS.
- Add troubleshooting notes for both platforms: If there are platform-specific issues or prerequisites, document them for both Linux and Windows.
Sap
Get started with manual deployment of automation framework
...blob/main/articles/sap/automation/manual-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally Linux/CLI-centric, using Azure CLI, Bash, and Terraform commands throughout. However, there is evidence of Windows bias in the SSH client instructions, where PuTTY (a Windows SSH client) is mentioned as the example tool for connecting to the deployer and converting SSH keys to .ppk format. No Linux SSH client (e.g., OpenSSH) is mentioned, and the instructions for key conversion are Windows-specific. The mention of Azure Cloud Shell is neutral, as it is available on both platforms. There are no PowerShell examples, and most commands are cross-platform, but the SSH client section prioritizes Windows tooling.
Recommendations
- Add instructions for connecting via SSH from Linux and macOS using OpenSSH (e.g., 'ssh -i <key> <user>@<host>'), alongside the PuTTY example.
- Include guidance on using standard OpenSSH key formats and conversion tools (e.g., 'ssh-keygen -p -m PEM -f <key>') for Linux/macOS users.
- Explicitly state that the deployment steps are compatible with Linux, macOS, and Windows, and provide platform-specific notes where relevant.
- If mentioning PuTTY, also mention alternatives like MobaXterm (Windows), Terminal (macOS), and GNOME Terminal/Konsole (Linux) for parity.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only a PowerShell example for listing available OS image versions, with no equivalent Linux (bash/Azure CLI) example. This may disadvantage users working from Linux environments, as PowerShell is primarily a Windows tool. No other explicit Windows bias is present, and the OS support and deployment instructions are Linux-centric (RHEL/SUSE), but the lack of Linux command-line parity is notable.
Recommendations
- Add Azure CLI (bash) examples alongside PowerShell for listing VM images, e.g., using 'az vm image list' or 'az vm image show'.
- Explicitly state that both Windows and Linux users can perform deployment tasks, and provide cross-platform command alternatives wherever possible.
- Review other command-line instructions to ensure Linux users are equally supported and not required to use PowerShell.
Sap
Quickstart - Create a distributed highly available SAP system with Azure Center for SAP solutions with Azure CLI
...ions/quickstart-create-high-availability-namecustom.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Azure PowerShell as an alternative to Azure CLI for deploying SAP systems, highlighting a Windows-centric tool before any Linux equivalents. No Linux-specific tools or shell examples (e.g., bash scripts) are provided, and PowerShell is referenced without noting cross-platform compatibility or parity with Linux-native workflows.
Recommendations
- Explicitly mention that Azure PowerShell is cross-platform, and provide links or instructions for using it on Linux/macOS.
- Include bash or shell script examples alongside Azure CLI commands to demonstrate Linux-native workflows.
- Reference Linux tools (e.g., az CLI in bash, jq for JSON manipulation) where relevant, and provide parity in tooling recommendations.
- Avoid listing Windows tools (PowerShell) before Linux equivalents unless both are given equal prominence.
- Add a section or note for Linux/macOS users, clarifying any differences or additional steps.
Sap
Install HANA on SAP HANA on Azure (Large Instances) | Microsoft Docs
...stances/archived-hli-docs/hana-example-installation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based examples for downloading SAP HANA installation packages to the jump box, despite the service targeting Linux-based SAP HANA Large Instances. The initial example explicitly states the use of a Windows jump box, with no mention of Linux alternatives or equivalent commands for Linux jump boxes. This may disadvantage users who prefer or require a Linux-based workflow, especially since the actual SAP HANA installation occurs on Linux.
Recommendations
- Provide parallel instructions and examples for downloading and extracting SAP HANA installation packages on a Linux jump box, including relevant Linux commands (e.g., wget, curl, tar).
- Clarify that both Windows and Linux jump boxes are supported and describe any differences in workflow or prerequisites.
- Ensure screenshots and command-line examples are available for both platforms, or use platform-agnostic instructions where possible.
- Mention common Linux tools and patterns (e.g., SCP, rsync for file transfer) alongside Windows equivalents.
- Review documentation for other sections where Windows tools or terminology may be used exclusively, and add Linux alternatives.
Sap
Certification of SAP HANA on Azure (Large Instances) | Microsoft Docs
...arge-instances/archived-hli-docs/hana-certification.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Windows-centric tools and patterns, such as Active Directory, DNS, RDP servers, and jump servers, without mentioning Linux equivalents or alternatives. These Windows tools are listed before any Linux-specific details, despite the service targeting Linux-based SAP HANA deployments. There are no Linux-specific administration or connectivity examples, and the documentation does not provide parity in describing Linux tools or patterns for managing SAP HANA on Azure.
Recommendations
- Include Linux-native alternatives to Windows tools (e.g., LDAP for Active Directory, SSH bastion hosts instead of RDP/jump servers).
- Provide examples of connecting to SAP HANA using Linux tools (e.g., SSH, Linux desktop clients, command-line utilities).
- Describe Linux-based network and system administration patterns alongside or before Windows equivalents.
- Clarify that both Windows and Linux approaches are supported and provide guidance for each.
- Add explicit instructions or references for Linux system management, monitoring, and connectivity relevant to SAP HANA on Azure.
Sap
Create IBM Db2 provider for Azure Monitor for SAP solutions
...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 quickstarts in the prerequisites, without mentioning or providing equivalent Linux/CLI examples. There are no instructions or examples for Linux users (e.g., Azure CLI, Bash), and Windows tools/patterns are mentioned first and exclusively.
Recommendations
- Add Linux/CLI-based quickstart links alongside or before PowerShell, such as Azure CLI or Bash scripts.
- Include explicit instructions or examples for Linux users to create and configure the IBM Db2 provider using Azure CLI.
- Ensure that all steps referencing the Azure portal or PowerShell have equivalent Linux/CLI documentation.
- Review future documentation for parity in tool and example coverage between Windows and Linux environments.
Sap
Get started with SAP on Azure VMs | Microsoft Docs
...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 by referencing Windows-specific tools and clustering solutions (e.g., Windows Failover Clustering) and mentioning Windows scenarios before or alongside Linux equivalents. However, there is substantial coverage of Linux platforms (SLES, RHEL, Oracle Linux) and open-source clustering tools (Pacemaker), with many updates and examples for Linux environments. The documentation is not exclusively Windows-focused, but Windows technologies and patterns are sometimes highlighted or listed first, and some sections (such as AD integration and clustering) emphasize Windows solutions.
Recommendations
- Ensure Linux examples and tools (e.g., Pacemaker, systemd, Linux identity integration) are presented with equal prominence and detail as Windows solutions.
- Avoid listing Windows tools or scenarios first unless there is a technical reason; alternate ordering or group by OS type.
- Provide explicit Linux equivalents for every Windows-specific example, especially in areas like clustering, identity integration, and storage.
- Expand documentation for Linux identity integration and single sign-on scenarios to match the depth of Windows/Entra coverage.
- Review and update any sections where Windows terminology or tools are used generically (e.g., 'failover clustering') to clarify Linux alternatives.
Sap
Set up IBM Db2 HADR on Azure virtual machines (VMs) on RHEL | Microsoft Docs
.../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 RHEL and is generally Linux-centric. However, there are minor instances of Windows bias: (1) the 'availability set' concept is linked to a Windows-specific Azure documentation page before Linux equivalents, and (2) the documentation references Windows in the context of IBM Db2 LUW and Azure VM types. Additionally, the load balancer configuration section presents Azure portal, CLI, and PowerShell tabs, with PowerShell (a Windows-centric tool) included as a primary method, though Linux-native CLI examples are present and prioritized. No examples are missing for Linux, and all operational instructions and code samples are for Linux (bash, pcs, systemctl, etc.).
Recommendations
- When referencing Azure features like 'availability set', link to both Windows and Linux documentation, or prefer the Linux-specific page when the target is RHEL.
- In sections listing configuration methods (portal, CLI, PowerShell), clarify which tools are most appropriate for Linux users, and consider listing Azure CLI before PowerShell.
- Remove or clarify any references to Windows documentation or tools unless strictly necessary for cross-platform scenarios.
- Ensure that any mention of IBM Db2 LUW (Linux, Unix, Windows) does not imply Windows is the primary or preferred platform when the article is Linux-focused.
Sap
Azure VMs high availability for SAP NW on SLES with NFS on Azure Files| Microsoft Docs
...kloads/high-availability-guide-suse-nfs-azure-files.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on SAP NetWeaver high availability on SUSE Linux Enterprise Server (SLES) and provides Linux-centric instructions and examples throughout. However, there is mild Windows bias in the prerequisites and service tags, where Windows is mentioned before Linux, and Windows tools (PowerShell) are referenced as configuration options for Azure resources (e.g., load balancer setup). The Azure CLI, portal, and PowerShell are all presented as options, but PowerShell (a Windows-centric tool) is included and sometimes listed after portal and CLI, suggesting parity but still referencing Windows tooling. There are no missing Linux examples, and all operational steps are shown for Linux/SLES. No PowerShell-heavy or Windows-only examples are present.
Recommendations
- Reorder service tags and prerequisites to mention Linux before Windows when the guide is Linux-focused.
- Clarify that PowerShell is cross-platform, or de-emphasize its use in favor of Azure CLI for Linux-centric guides.
- Ensure that all example commands and configuration steps are shown for Linux first, and only mention Windows tools as alternatives if needed.
- Remove or minimize references to Windows-specific tools unless strictly necessary for cross-platform parity.
- Explicitly state Linux as the primary platform in introductory sections to reinforce the intended audience.
Sap
Azure VMs high availability for SAP NetWeaver on SLES | Microsoft Docs
...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 SAP NetWeaver high availability on SUSE Linux Enterprise Server, and all technical steps, examples, and code are Linux-centric. However, there is evidence of Windows bias in the following ways: (1) Windows is mentioned first in several places, such as in the services metadata ('virtual-machines-windows') and in SAP Note summaries, where Windows is listed before Linux; (2) The documentation references Windows-specific SAP kernel versions and VM sizes before Linux equivalents; (3) The load balancer configuration instructions provide tabs for Azure Portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) included as a first-class option, even though the scenario is Linux-only; (4) The metadata and cross-references include Windows-related services, which may confuse Linux-focused readers.
Recommendations
- In SAP Note summaries and service metadata, list Linux before Windows when the documentation is Linux-specific.
- Remove or de-emphasize PowerShell instructions/tabs for load balancer configuration, as PowerShell is not typically used in Linux environments.
- Ensure that all examples, tools, and references are Linux-focused, and avoid mentioning Windows unless directly relevant to interoperability or migration scenarios.
- Clarify in the introduction and metadata that the guide is for Linux only, and remove references to Windows services to avoid confusion.
- If cross-platform parity is needed, provide equivalent Linux and Windows instructions side-by-side, but prioritize Linux in this Linux-focused guide.
Sap
Azure VMs high availability for SAP NetWeaver on SLES for SAP Applications with simple mount and NFS| Microsoft Docs
...loads/high-availability-guide-suse-nfs-simple-mount.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on deploying SAP NetWeaver on SUSE Linux Enterprise Server (SLES) and provides Linux-centric instructions and examples throughout. However, there are minor signs of Windows bias: the 'services' metadata includes 'virtual-machines-windows', and some referenced SAP Notes and prerequisites mention Windows before Linux. Additionally, Azure CLI, PowerShell, and portal instructions are presented in parallel for load balancer configuration, with PowerShell (a Windows-centric tool) included as a primary method. No Linux examples are missing, and all operational instructions use Linux commands.
Recommendations
- Remove or clarify the inclusion of 'virtual-machines-windows' in the services metadata if the guide is exclusively for Linux.
- When referencing SAP Notes or prerequisites, list Linux before Windows when the context is Linux-focused.
- Consider providing Bash/Azure CLI examples before PowerShell in tabbed instructions, or clarify that PowerShell is optional for Linux users.
- Ensure that all example commands and tooling references are relevant to Linux environments, and avoid unnecessary mention of Windows-specific tools unless strictly required for cross-platform scenarios.
Sap
Integrating Azure services with SAP RISE| Microsoft Docs
...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 primarily Windows-based technologies. There are no explicit examples, instructions, or mentions of Linux-based alternatives or deployment patterns, despite the page targeting both Linux and Windows virtual machines. This creates a bias toward Windows environments and tools, with Linux parity lacking in practical guidance.
Recommendations
- Include explicit instructions and examples for deploying self-hosted integration runtime and on-premises data gateway on Linux VMs.
- Mention and document SAP connectors or integration runtimes that support Linux, such as the SAP Java Connector (JCo) or JDBC/ODBC drivers for Linux.
- Provide architecture diagrams and step-by-step guides for Linux-based integration scenarios, ensuring equal visibility and support.
- Clarify any limitations or differences between Windows and Linux deployments for each integration pattern.
- List prerequisites and troubleshooting steps for Linux environments alongside Windows-specific guidance.
Sap
High availability of SAP HANA scale-up with Azure NetApp Files on SLES | Microsoft Docs
...kloads/sap-hana-high-availability-netapp-files-suse.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is focused on SAP HANA high availability on SUSE Linux (SLES) and provides comprehensive Linux-specific instructions. However, there is evidence of Windows bias in the following ways: (1) The service metadata lists 'virtual-machines-windows' before Linux, (2) Load balancer configuration instructions are provided for Azure portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) included as a first-class option, and (3) Some referenced SAP Notes and documentation mention Windows before Linux, even though the main content is Linux-focused. There are no missing Linux examples, and all operational steps and code samples are for Linux/SLES.
Recommendations
- In service metadata and introductory sections, list Linux-related services and documentation before or alongside Windows equivalents to reflect the Linux focus.
- When presenting tooling options (e.g., Azure CLI, PowerShell), clarify which are cross-platform and which are Windows-specific, and consider prioritizing cross-platform tools (e.g., Azure CLI, Bash) in Linux-focused documentation.
- In referenced SAP Notes and documentation, ensure Linux is mentioned before or alongside Windows when the context is Linux-centric.
- Explicitly state that PowerShell is optional and primarily for Windows users, and highlight Azure CLI or Bash as the preferred automation tools for Linux environments.
- Review and update any remaining references or examples that may imply Windows is the default or primary platform, especially in metadata, navigation, and cross-references.