Sap

440
Total Pages
349
Linux-Friendly Pages
91
Pages with Bias
20.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

177 issues found
Showing 1-25 of 177 flagged pages
Sap SAP MaxDB, liveCache, and Content Server deployment on Azure VMs | Microsoft Docs ...s/blob/main/articles/sap/workloads/dbms-guide-maxdb.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on Windows deployments for SAP MaxDB, liveCache, and Content Server on Azure VMs. All configuration, backup, restore, and performance guidance is written for Windows environments, with repeated recommendations for Windows Server and Windows-specific storage tools (e.g., Storage Pools, Storage Spaces). There are no Linux-specific instructions, examples, or references to Linux tools or patterns for these SAP components, despite Azure supporting Linux VMs.
Recommendations
  • Add equivalent sections for Linux deployments, including supported Linux distributions and VM types for SAP MaxDB, liveCache, and Content Server.
  • Provide Linux-specific storage configuration guidance, referencing Linux tools (e.g., LVM, mdadm) and best practices for disk striping, caching, and backup.
  • Include backup and restore instructions for Linux, mentioning native SAP MaxDB tools and common Linux backup utilities.
  • List supported versions and configuration steps for SAP components on Linux, and clarify any differences or limitations compared to Windows.
  • Ensure parity in recommendations for performance, monitoring, and availability features on Linux.
  • Where third-party tools (e.g., MaxBack) are Windows-only, suggest Linux alternatives or clarify support status.
GitHub Create Pull Request
Sap Configure Azure DevOps Services for SAP Deployment Automation Framework .../blob/main/articles/sap/automation/configure-devops.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a notable Windows bias, especially in the automation sections. All core setup scripts for configuring Azure DevOps Services for SAP Deployment Automation Framework are provided exclusively in PowerShell, with explicit instructions to use PowerShell ISE. There are no equivalent Bash or Linux shell examples for these critical steps, and Windows tooling (PowerShell ISE, Remove-Module, Import-Module, etc.) is referenced without alternatives. While some later sections (e.g., app registration, web app updates) provide both Linux and Windows tabs, the initial and most critical automation steps lack Linux parity, making it difficult for non-Windows users to follow the guide end-to-end.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell automation scripts, especially for initial setup and workload zone configuration.
  • Replace references to PowerShell ISE with cross-platform editors (e.g., VS Code) or generic instructions.
  • Clearly indicate which scripts are cross-platform and which are Windows-only, and provide guidance for Linux/macOS users.
  • Ensure all critical steps have both Windows and Linux/macOS instructions/examples.
  • Where custom modules are used (e.g., SDAFUtilities), document how to use/install them on Linux/macOS.
GitHub Create Pull Request
Sap About workload zone deployment in automation framework ...b/main/articles/sap/automation/deploy-workload-zone.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Only Windows Excluded
Summary
The documentation provides detailed Linux/bash instructions for deploying SAP workload zones, but explicitly states that deployment cannot be performed from Windows. No PowerShell or Windows command-line examples are given, and Windows users are excluded from performing the deployment directly.
Recommendations
  • Investigate and document any possible workarounds or alternatives for Windows users, such as using WSL (Windows Subsystem for Linux), Docker containers, or remote deployment from a Linux VM.
  • If deployment from Windows is fundamentally unsupported, clarify the technical reasons and suggest supported cross-platform approaches.
  • Provide guidance for Windows users on setting up a Linux environment (e.g., WSL2) to perform the deployment.
  • Ensure parity in documentation by mentioning any prerequisites or limitations for each platform at the start of the guide.
GitHub Create Pull Request
Sap Deploy the control plane for SAP Deployment Automation Framework ...b/main/articles/sap/automation/deploy-control-plane.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Only Windows Excluded
Summary
The documentation exhibits a bias against Windows users: critical deployment steps for the control plane can only be performed on Linux, with explicit statements that Windows is unsupported. All deployment scripts and examples are Bash-based, with no PowerShell or Windows-native alternatives. Windows users are excluded from completing the main task, except for a minor optional web app configuration step, which does include PowerShell, but the core deployment remains Linux-only.
Recommendations
  • Provide PowerShell equivalents for all Bash deployment scripts and commands.
  • Document any prerequisites or limitations for running the deployment on Windows, and offer workarounds (e.g., WSL, Docker).
  • If Windows cannot be supported for technical reasons, clearly state why and suggest supported alternatives (such as using WSL or a Linux VM).
  • Ensure that all critical automation steps have cross-platform parity, or document platform-specific differences and solutions.
GitHub Create Pull Request
Sap SQL Server Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs ...ob/main/articles/sap/workloads/dbms-guide-sqlserver.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
This documentation is heavily biased towards Windows, with explicit statements that SAP does not support SQL Server on Linux for SAP workloads. All examples, configuration steps, and recommendations are for Windows Server and NTFS, with no Linux equivalents or parity. Windows-specific tools, file systems, and deployment patterns are referenced exclusively, and all sample configurations assume Windows as the operating system. Linux is mentioned only to clarify its lack of support, and no Linux commands, tools, or patterns are provided.
Recommendations
  • Clearly state at the top that SAP does not support SQL Server on Linux for SAP workloads, and link to official SAP documentation for confirmation.
  • If partial Linux support exists (e.g., for non-SAP workloads), provide a separate section or page for Linux users, outlining what is and isn't supported.
  • Where possible, mention Linux alternatives for general SQL Server on Azure VM deployment (outside SAP workloads), or link to relevant Linux documentation.
  • Ensure that any general recommendations (e.g., disk layout, backup strategies) clarify which are Windows-only and which could apply to Linux.
  • If future SAP support for SQL Server on Linux becomes available, update documentation to include Linux examples, tools, and configuration steps.
GitHub Create Pull Request
Sap SAP ASCS/SCS multi-SID HA with WSFC&shared disk on Azure | Microsoft Docs ...ap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments, focusing exclusively on Windows Server Failover Clustering (WSFC), Windows-only tools (SIOS DataKeeper, DNS Manager), and PowerShell scripts for Azure resource configuration. There are no Linux or cross-platform equivalents, and the architecture, prerequisites, and procedures are all tailored to Windows, leaving Linux users without guidance or alternatives.
Recommendations
  • Provide equivalent instructions for Linux-based SAP high-availability clusters, such as using Pacemaker/Corosync and NFS or other supported shared disk solutions.
  • Include Azure CLI or Bash script examples alongside PowerShell for resource configuration steps.
  • Mention and link to SAP documentation for Linux HA setups on Azure, if available.
  • Clarify in the introduction that the guide is Windows-specific, and direct Linux users to relevant resources.
  • Discuss alternative clustering and disk replication solutions available on Linux (e.g., DRBD, native Azure managed disks).
GitHub Create Pull Request
Sap SAP ASCS/SCS multi-SID HA with WSFC and Azure shared disk | Microsoft Docs ...kloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clustering (WSFC) and provides only Windows-specific instructions, examples, and tooling (PowerShell, Windows DNS Manager, Failover Cluster Manager). There are no references to Linux-based clustering solutions, nor any Linux command-line examples or guidance for SAP HA on Linux. All operational steps, including disk management, cluster configuration, and failover, are described using Windows tools and PowerShell, with no mention of Linux equivalents.
Recommendations
  • Add a parallel guide or sections for Linux-based SAP HA deployments (e.g., using Pacemaker, Corosync, or SUSE/Red Hat clustering tools).
  • Provide Linux command-line examples for disk attachment, formatting, and cluster resource management (using az CLI, shell commands, etc.).
  • Include instructions for DNS configuration using Linux tools (e.g., bind, systemd-resolved, or relevant cloud DNS services).
  • Reference SAP notes and best practices for Linux HA clusters.
  • Clarify in the introduction that the guide is Windows-only, or provide links to Linux-specific documentation if available.
GitHub Create Pull Request
Sap SAP ASCS/SCS instance multi-SID high availability with Windows Server Failover Clustering and file share on Azure ...sap/workloads/sap-ascs-ha-multi-sid-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
This documentation is heavily biased toward Windows environments. All examples, scripts, and tooling references are for Windows Server Failover Clustering, Scale-Out File Server, and PowerShell. No Linux equivalents, alternative clustering solutions, or cross-platform guidance are provided. The instructions and architecture are exclusively Windows-centric, making it impossible for Linux users to follow or adapt the content for their platforms.
Recommendations
  • Clearly state in the introduction that the guide is Windows-only and provide links to Linux high availability documentation for SAP on Azure.
  • Add a section comparing Windows and Linux HA architectures for SAP, including supported scenarios and limitations.
  • Provide Linux-specific examples, such as using Pacemaker/Corosync clusters, NFS shares, and shell scripts for file/folder permissions.
  • Reference SAP and Azure documentation for Linux-based multi-SID high availability setups.
  • Ensure parity in diagrams and step-by-step instructions for Linux environments where possible.
GitHub Create Pull Request
Sap Cluster SAP ASCS/SCS instance on WSFC using shared disk in Azure | Microsoft Docs ...kloads/sap-high-availability-guide-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is exclusively focused on clustering SAP ASCS/SCS instances using Windows Server Failover Clustering (WSFC) in Azure. All examples, instructions, and architectural diagrams reference Windows tools, patterns, and file structures. There is no mention of Linux-based clustering solutions (such as Pacemaker or Corosync), nor any guidance for Linux users. The prerequisites, supported OS versions, and next steps all reinforce a Windows-only approach, making the documentation inaccessible to Linux/macOS users.
Recommendations
  • Add a section or separate documentation for clustering SAP ASCS/SCS on Linux in Azure, covering supported Linux distributions and clustering tools (e.g., Pacemaker, Corosync).
  • Provide Linux-specific examples for shared disk configuration, load balancing, and SAP file structures.
  • Include parity in diagrams and architecture overviews for Linux-based clusters.
  • Clearly state in the introduction that the documentation is Windows-specific, and link to Linux equivalents if available.
GitHub Create Pull Request
Sap Azure infrastructure for SAP ASCS/SCS with WSFC&shared disk | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is exclusively focused on Windows environments, specifically Windows Server Failover Clustering (WSFC) for SAP ASCS/SCS high availability on Azure. All examples, instructions, and tooling (PowerShell, Windows registry, Windows Failover Cluster, SIOS DataKeeper) are Windows-specific, with no mention of Linux-based clustering solutions (e.g., Pacemaker, Corosync), Linux VM setup, or Linux command-line equivalents. This creates a strong Windows bias and excludes Linux users from following the guide.
Recommendations
  • Add a parallel guide or sections for Linux-based SAP ASCS/SCS high availability on Azure, using Pacemaker or other supported Linux clustering solutions.
  • Provide Linux VM deployment instructions and examples.
  • Include Azure CLI and Linux shell command equivalents for infrastructure setup (disk creation, load balancer configuration, etc.), not just PowerShell.
  • Reference SAP and Azure documentation for Linux HA scenarios.
  • Clearly state in the introduction that the guide is Windows-only, and link to Linux alternatives if available.
GitHub Create Pull Request
Sap Cluster SAP ASCS/SCS on WSFC using file share in Azure | Microsoft Docs ...rkloads/sap-high-availability-guide-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clustering (WSFC) and related Windows technologies (e.g., Storage Spaces Direct, SMB file shares, SOFS). All examples, architectures, and instructions are specific to Windows environments, with no mention of Linux or cross-platform alternatives for clustering SAP ASCS/SCS in Azure. Linux-based clustering solutions (e.g., Pacemaker, SUSE HA) are not referenced, and there are no Linux/macOS commands, patterns, or parity notes.
Recommendations
  • Add a section or cross-reference for Linux-based SAP ASCS/SCS clustering in Azure, such as using Pacemaker or SUSE Linux Enterprise High Availability Extension.
  • Provide parity diagrams and architecture explanations for Linux clusters in Azure, including supported file share and quorum options.
  • Include links to Linux-specific SAP notes and Azure documentation for SAP on Linux high availability.
  • Explicitly state in the introduction that the guide is Windows-only, and direct Linux users to the appropriate resources.
  • Where possible, mention equivalent Linux technologies (e.g., NFS for file shares, Pacemaker for clustering) and their support status in Azure.
GitHub Create Pull Request
Sap Azure infrastructure for SAP ASCS/SCS HA with WSFC&file Share ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC) and Microsoft Scale-Out File Server. All examples, instructions, and tooling are Windows-centric, with exclusive use of PowerShell and Windows features. There are no Linux or cross-platform alternatives mentioned, and the prerequisites and next steps assume a Windows-only deployment.
Recommendations
  • Add equivalent instructions and examples for Linux-based SAP high availability setups, such as using Pacemaker or SUSE Linux Enterprise High Availability Extension.
  • Provide sample scripts and automation templates for Linux (e.g., Bash, Ansible) alongside PowerShell.
  • Mention Linux-supported clustering and file share solutions (e.g., NFS, GlusterFS) and how to integrate them with Azure.
  • Clarify in the introduction that the guide is Windows-specific, or link to Linux-focused documentation if available.
  • Ensure parity in troubleshooting, tuning, and configuration guidance for Linux clusters.
GitHub Create Pull Request
Sap SAP NetWeaver high availability installation on a Windows failover cluster and file share for SAP ASCS/SCS instances on Azure | Microsoft Docs ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Cluster (WSFC) and Scale-Out File Server (SOFS). All examples, instructions, and tooling references are Windows-centric, with exclusive use of PowerShell scripts and Windows file paths. There are no Linux or cross-platform alternatives provided, and the prerequisites, architecture, and operational steps are tailored solely for Windows-based deployments.
Recommendations
  • Clearly state in the introduction that the guide is Windows-specific, and provide links to equivalent Linux high-availability documentation for SAP NetWeaver on Azure.
  • If Linux is supported, add parallel sections or examples for Linux-based clustering (e.g., using Pacemaker/Corosync, NFS shares, Linux file paths, and shell commands).
  • Include a comparison table of Windows and Linux approaches for SAP NetWeaver high availability on Azure.
  • Reference SAP documentation for Linux high-availability setups and provide guidance on Azure-specific considerations for Linux clusters.
GitHub Create Pull Request
Sap Install SAP NetWeaver HA on a Windows failover cluster and shared disk for an SAP ASCS/SCS instance in Azure | Microsoft Docs ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is strongly focused on Windows environments, specifically Windows Server Failover Clustering, Windows DNS Manager, and Windows Firewall. All configuration and scripting examples use PowerShell, and all operational steps reference Windows-specific tools and patterns. There are no Linux or cross-platform equivalents or alternatives mentioned, nor any guidance for performing similar tasks on Linux-based clusters (e.g., SUSE, Pacemaker, Corosync). The prerequisites and architecture are exclusively Windows-centric.
Recommendations
  • Add a section or links for installing SAP NetWeaver HA on Linux clusters (e.g., SUSE, Red Hat) in Azure, referencing Pacemaker/Corosync and Linux shared disk solutions.
  • Provide Linux-specific examples for DNS configuration, firewall rules (e.g., using firewalld or iptables), and cluster management (e.g., crm shell, pcs commands).
  • Include parity guidance for probe port configuration and load balancer integration on Linux clusters.
  • Clearly state in the introduction that the guide is Windows-only, and link to Linux HA documentation if available.
  • Where possible, abstract Azure-specific steps so they apply to both Windows and Linux environments.
GitHub Create Pull Request
Sap SAP MaxDB, liveCache, and Content Server deployment on Azure VMs | Microsoft Docs ...s/blob/main/articles/sap/workloads/dbms-guide-maxdb.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows deployments, with all examples, recommendations, and configuration guidelines referencing Windows Server, Windows Storage Pools/Spaces, and Windows-specific backup integrations (VSS). There is no mention of Linux support, Linux OS versions, or Linux equivalents for storage, backup, or deployment patterns. This creates friction for users deploying SAP MaxDB, liveCache, or Content Server on Linux VMs in Azure.
Recommendations
  • Add equivalent sections for Linux deployments, including supported Linux distributions and versions for SAP MaxDB, liveCache, and Content Server.
  • Provide Linux-specific configuration guidelines for storage (e.g., using LVM, mdadm for RAID, or other Linux-native tools).
  • Include Linux backup/restore strategies, such as integration with Azure Backup via Linux agents or third-party tools compatible with Linux.
  • Mention Linux-specific best practices for performance, disk striping, and logical volume management.
  • Ensure parity in examples and recommendations for both Windows and Linux, or clearly state if a feature is Windows-only.
GitHub Create Pull Request
Sap Azure infrastructure for SAP ASCS/SCS with WSFC&shared disk | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is exclusively focused on deploying SAP ASCS/SCS high-availability clusters on Azure using Windows Failover Clustering and Windows-centric tooling (PowerShell, Windows registry, SIOS DataKeeper for Windows). All examples, instructions, and automation templates are for Windows Server; there is no mention of Linux or cross-platform alternatives, nor any guidance for Linux-based SAP deployments.
Recommendations
  • Clearly state in the introduction that this guide is Windows-only and provide links to equivalent Linux HA documentation if available.
  • Add a section or cross-reference for SAP HA on Linux (e.g., using Pacemaker, STONITH, or other Linux clustering solutions on Azure).
  • Where possible, provide parity examples for Linux (e.g., using Azure CLI/bash, Linux disk formatting, Linux cluster setup).
  • Mention Linux-supported shared disk solutions and how to configure them in Azure.
  • If SIOS DataKeeper or similar tools exist for Linux, reference them or alternatives.
  • Ensure automation templates (ARM, Terraform) are available for Linux scenarios.
GitHub Create Pull Request
Sap SAP ASCS/SCS multi-SID HA with WSFC&shared disk on Azure | Microsoft Docs ...ap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC), PowerShell scripting, and Windows-specific tools like SIOS DataKeeper and DNS Manager. There are no examples or guidance for Linux-based SAP high availability setups, nor are Linux equivalents mentioned or referenced. All instructions, scripts, and screenshots are Windows-centric, making it inaccessible for Linux/macOS users.
Recommendations
  • Add a section describing Linux-based SAP high availability architectures (e.g., using Pacemaker, Corosync, or SUSE Linux Enterprise High Availability Extension).
  • Provide equivalent Linux command-line examples (e.g., using Azure CLI, shell scripts) for infrastructure setup and load balancer configuration.
  • Reference SAP documentation for Linux cluster setups and provide links to relevant guides.
  • Clarify in the introduction that the guide is Windows-specific, and link to Linux-focused documentation if available.
  • Include a comparison table of Windows vs. Linux HA approaches for SAP on Azure.
GitHub Create Pull Request
Sap Install SAP NetWeaver HA on a Windows failover cluster and shared disk for an SAP ASCS/SCS instance in Azure | Microsoft Docs ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering. All examples, instructions, and scripts use Windows tools such as DNS Manager, Failover Cluster Manager, and PowerShell cmdlets. There are no Linux or cross-platform alternatives or examples provided, and Linux high-availability clustering solutions (e.g., Pacemaker, Corosync) are not mentioned or linked. The page assumes the use of Windows throughout and does not address how to perform equivalent tasks on Linux.
Recommendations
  • Add a section or links for Linux-based SAP NetWeaver HA deployments, referencing SUSE or Red Hat clustering guides.
  • Provide equivalent Linux commands and examples (e.g., using crmsh, pcs, or native SAP tools on Linux).
  • Mention Linux-specific high-availability patterns and tools (Pacemaker, Corosync, etc.) where appropriate.
  • Clarify in the introduction that the guide is Windows-specific and link to Linux documentation for parity.
  • Where PowerShell is used, offer analogous bash or shell script examples for Linux clusters.
GitHub Create Pull Request
Sap Deploy the control plane for SAP Deployment Automation Framework ...b/main/articles/sap/automation/deploy-control-plane.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Only Windows Excluded
Summary
The documentation exhibits a bias against Windows users: critical deployment steps for the SAP Deployment Automation Framework control plane can only be performed on Linux, with explicit statements that Windows is unsupported for these tasks. All deployment examples and scripts are provided for Linux, with no PowerShell or Windows-native alternatives. Windows users are instructed that they cannot perform the control plane deployment from Windows, creating a significant barrier for those on Windows platforms.
Recommendations
  • Provide PowerShell scripts or Windows-compatible instructions for control plane deployment, or clarify technical limitations preventing Windows support.
  • If Linux is required due to toolchain dependencies, suggest using WSL (Windows Subsystem for Linux) and provide guidance for setting it up.
  • Explicitly document any platform limitations and offer alternatives (e.g., using Azure Cloud Shell, WSL, or a Linux VM) for Windows users.
  • Ensure that all critical deployment steps have cross-platform parity or clear workarounds.
GitHub Create Pull Request
Sap About workload zone deployment in automation framework ...b/main/articles/sap/automation/deploy-workload-zone.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Only Windows Excluded
Summary
The documentation page demonstrates a bias against Windows by explicitly stating that deployment cannot be performed from Windows, providing only Linux/bash examples, and omitting any Windows or PowerShell instructions. This creates a significant barrier for Windows users, who are unable to complete the deployment process using their native environment.
Recommendations
  • Investigate and document any possible workarounds or alternative methods for Windows users, such as using WSL (Windows Subsystem for Linux), Docker containers, or remote Linux hosts.
  • If deployment from Windows is fundamentally unsupported, clearly explain the technical reasons and suggest supported alternatives (e.g., using Azure DevOps pipelines or Linux VMs).
  • Provide guidance for Windows users on setting up a compatible environment (e.g., installing WSL, configuring SSH, or using Azure Cloud Shell).
  • Ensure that any prerequisites or limitations for Windows users are highlighted early in the documentation.
GitHub Create Pull Request
Sap SQL Server Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs ...ob/main/articles/sap/workloads/dbms-guide-sqlserver.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily biased toward Windows, both in scope and practical guidance. The page explicitly states that SAP does not support SQL Server on Linux for SAP workloads, and all deployment, configuration, and operational examples are Windows-centric. Only Windows Server is mentioned for OS, NTFS for file system, and Windows-specific tools and patterns (e.g., Windows command prompt, NTFS formatting, D:\ drive usage, Windows clustering, Windows-specific VM images, and Windows-only features like Write Accelerator). No Linux equivalents, examples, or guidance are provided, and Linux is only referenced to clarify its lack of support.
Recommendations
  • Clearly state at the top that Linux is not supported for SAP workloads with SQL Server, and link to any SAP or Microsoft documentation explaining the rationale.
  • If partial Linux support exists for non-SAP workloads, provide a brief section or link for those scenarios.
  • Where possible, mention what would be different if Linux were supported (e.g., file system, disk formatting, OS-level configuration), to help users understand the gap.
  • If SAP or Microsoft ever adds Linux support, update the documentation to include Linux-specific examples, tools, and configuration steps in parity with Windows.
GitHub Create Pull Request
Sap SAP ASCS/SCS instance multi-SID high availability with Windows Server Failover Clustering and file share on Azure ...sap/workloads/sap-ascs-ha-multi-sid-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is exclusively focused on Windows Server Failover Clustering (WSFC) and related Windows technologies (SOFS, PowerShell, Failover Cluster Manager). All examples, scripts, and screenshots use Windows tools and PowerShell, with no mention of Linux equivalents or cross-platform approaches. There are no Linux or macOS instructions, examples, or references, and the architecture described is inherently Windows-centric.
Recommendations
  • Add a section describing how to achieve SAP ASCS/SCS multi-SID high availability on Linux (e.g., using Pacemaker, Corosync, NFS, etc.)
  • Provide Linux-specific examples and scripts for cluster setup, file share configuration, and permissions management.
  • Include links to SAP and Azure documentation for Linux-based high availability solutions.
  • Clearly state in the introduction that the guide is Windows-only, and link to Linux documentation if available.
  • Where possible, highlight differences and parity between Windows and Linux approaches for SAP high availability.
GitHub Create Pull Request
Sap SAP ASCS/SCS multi-SID HA with WSFC and Azure shared disk | Microsoft Docs ...kloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments, specifically Windows Server Failover Clustering (WSFC). All examples, instructions, and tooling references are Windows-centric, with exclusive use of PowerShell, Windows DNS Manager, and Windows OS versions. There is no mention of Linux or cross-platform alternatives for clustering, disk management, or SAP high availability setup, making the guide inaccessible to Linux or macOS users.
Recommendations
  • Add equivalent instructions and examples for Linux-based SAP high availability clusters, such as using Pacemaker/Corosync and STONITH.
  • Provide Azure CLI and Bash script examples alongside PowerShell for disk creation, attachment, and formatting.
  • Include guidance for configuring DNS and load balancer settings on Linux (e.g., using BIND, systemd-resolved, or CLI tools).
  • Clarify in the prerequisites whether Linux-based SAP clusters are supported with Azure shared disks, and if not, provide links to relevant Linux HA documentation.
  • If the solution is Windows-only by design, state this clearly at the top and link to Linux HA documentation for SAP on Azure.
GitHub Create Pull Request
Sap Cluster SAP ASCS/SCS instance on WSFC using shared disk in Azure | Microsoft Docs ...kloads/sap-high-availability-guide-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on Windows Server Failover Clustering (WSFC) for SAP ASCS/SCS high availability in Azure, with all examples, terminology, and tooling specific to Windows. There is no mention of Linux-based clustering solutions, nor any guidance for SAP ASCS/SCS clustering on Linux or cross-platform approaches. Windows tools and patterns (WSFC, SIOS DataKeeper, UNC paths, Windows file shares) are referenced throughout, and supported OS versions are limited to Windows Server. This creates a strong bias toward Windows, making the documentation unusable for Linux or macOS users.
Recommendations
  • Add a parallel guide or section for clustering SAP ASCS/SCS instances on Linux (e.g., using Pacemaker, Corosync, or SUSE HA extensions) in Azure.
  • Include Linux-specific prerequisites, supported OS versions, and storage options (such as NFS, Azure Files, or Linux-compatible shared disks).
  • Provide Linux command-line examples and configuration steps alongside Windows/Powershell equivalents.
  • Reference cross-platform or Linux-native high availability patterns for SAP workloads in Azure.
  • Clarify in the introduction that the guide is Windows-specific, and link to Linux documentation if available.
GitHub Create Pull Request
Sap Cluster SAP ASCS/SCS on WSFC using file share in Azure | Microsoft Docs ...rkloads/sap-high-availability-guide-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows Server Failover Clustering (WSFC) and related Windows technologies (SOFS, Storage Spaces Direct, SMB file shares, Active Directory ACLs). All examples, diagrams, and instructions are specific to Windows environments, with no mention of Linux-based clustering solutions or parity for Linux/macOS users. There are no Linux equivalents or alternative approaches described, and Windows terminology and tools are used exclusively throughout.
Recommendations
  • Add a section or cross-reference for clustering SAP ASCS/SCS on Linux (e.g., using Pacemaker, SUSE HA, or Red Hat Cluster Suite) in Azure.
  • Provide parity documentation for Linux-based SAP high availability setups, including supported file share and clustering technologies (NFS, GlusterFS, etc.).
  • Include links to Linux-specific SAP HA guides (such as 'high-availability-guide-suse.md') in the 'Next steps' section.
  • Clearly state in the introduction that the guide is Windows-specific and provide guidance for Linux users.
  • Where possible, mention Linux alternatives to Windows features (e.g., NFS instead of SMB, Linux clustering tools instead of WSFC).
GitHub Create Pull Request
← Previous Page 1 of 8 Next →