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 301-325 of 639 flagged pages
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-supported-configurations.md ...les/sap/workloads/planning-supported-configurations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and clustering frameworks (e.g., Windows Failover Cluster, Scale-Out File Services, SIOS Datakeeper) are frequently mentioned first and in greater detail than their Linux equivalents. Many examples and recommendations (especially for SQL Server and SAP Central Services) are Windows-centric, with Linux alternatives often presented later or with less detail. Some high availability and multi-SID clustering scenarios are described as fully supported only on Windows, with Linux support more limited or requiring third-party solutions. There are also cases where Linux examples or guidance are missing or less comprehensive, particularly for Oracle Linux and Pacemaker configurations.
Recommendations
  • Ensure that Linux-based examples (e.g., Pacemaker, NFS, DRBD, GlusterFS) are presented with equal prominence and detail as Windows examples.
  • Where Windows tools or frameworks are mentioned, immediately provide the Linux equivalent (e.g., Pacemaker, Corosync) and link to relevant documentation.
  • Expand documentation for Linux high availability and multi-SID clustering scenarios, including Oracle Linux, and clarify support boundaries and third-party options.
  • Avoid presenting Windows solutions first by alternating or grouping by OS, or by providing parallel sections for Windows and Linux.
  • Include more Linux-specific configuration and troubleshooting examples, especially for SAP Central Services and DBMS high availability.
  • Clarify any limitations or gaps in Linux support and provide guidance or links to community or vendor resources for unsupported scenarios.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-wsfc-file-share.md ...rkloads/sap-high-availability-guide-wsfc-file-share.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Server Failover Clustering (WSFC) and related Microsoft technologies (e.g., Storage Spaces Direct, SMB file shares, SOFS, SIOS DataKeeper). All examples, architectures, and recommendations are specific to Windows environments. There are no Linux equivalents, examples, or references to Linux-based clustering or file sharing solutions. The document assumes a Windows-only context throughout, with no mention of Linux tools, commands, or patterns.
Recommendations
  • Add a section or cross-reference for Linux-based SAP ASCS/SCS clustering in Azure, such as using Pacemaker or SUSE HAE.
  • Provide parity diagrams and architecture overviews for Linux-based high availability solutions.
  • Include Linux-specific prerequisites, such as supported distributions, file system recommendations (e.g., NFS, OCFS2), and kernel requirements.
  • Offer example configurations and step-by-step guides for Linux clusters, similar to the detailed Windows instructions.
  • Reference relevant SAP Notes and Azure documentation for Linux HA scenarios.
  • Clarify in the introduction that the guide is Windows-specific, and link to Linux-focused documentation for users seeking those solutions.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-wsfc-shared-disk.md ...kloads/sap-high-availability-guide-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on Windows Server Failover Clustering (WSFC) for SAP ASCS/SCS high availability in Azure, with no mention of Linux-based clustering solutions or examples. All technical details, diagrams, and configuration steps are tailored to Windows environments and tools, such as WSFC, SIOS DataKeeper, and Windows-specific file shares. There are no references to Linux equivalents (e.g., Pacemaker, Corosync, NFS, or Linux clustering patterns), nor are Linux operating systems or their supported versions discussed.
Recommendations
  • Add a parallel section or separate documentation for clustering SAP ASCS/SCS on Linux in Azure, covering supported Linux distributions, clustering tools (e.g., Pacemaker, Corosync), and storage options (e.g., NFS, Azure shared disks for Linux).
  • Include Linux-specific examples, diagrams, and configuration steps to provide parity with the Windows-focused content.
  • Mention supported Linux OS versions and recommended best practices for SAP HA on Linux in Azure.
  • Reference SAP and Azure documentation for Linux-based high availability architectures.
  • Clarify in the introduction that the page is Windows-specific, and provide links to Linux-focused documentation if available.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/lama-installation.md .../blob/main/articles/sap/workloads/lama-installation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Linux and Windows guidance, but Windows examples and tools (such as Microsoft ODBC Driver, Visual C++ Redistributable, NT AUTHORITY\SYSTEM, and Windows file paths) are often presented first or exclusively, especially in SQL Server sections. Some deployment and troubleshooting steps focus on Windows-specific requirements, and certain examples (e.g., mounting IP addresses for SQL Server) are only shown for Windows, with Linux equivalents missing or less emphasized.
Recommendations
  • Ensure that every Windows-specific example (e.g., mounting IP addresses, file paths, troubleshooting steps) is paired with a Linux equivalent, especially for SQL Server and application server deployment.
  • Present Linux and Windows examples side-by-side, or alternate which comes first, to avoid implicit prioritization.
  • Include Linux-specific troubleshooting guidance for common SAP LaMa scenarios, not just Windows/SQL Server issues.
  • Clarify when a step or tool is Windows-only, and provide alternatives for Linux (e.g., for ODBC drivers, file permissions, user accounts).
  • Expand sections that mention Windows tools (such as Visual C++ Redistributable) to explicitly state their Linux counterparts or note when not required.
  • Review all code blocks and ensure Linux and Windows commands are equally represented and easy to find.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-file-share.md ...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-08 00:53
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 Cluster (WSFC) and Scale-Out File Server (SOFS). All examples, prerequisites, and procedures are Windows-centric, using Windows paths, PowerShell scripts, and Windows-specific clustering concepts. There is no mention of Linux equivalents, nor are any Linux-specific instructions, tools, or patterns provided.
Recommendations
  • Provide equivalent instructions for Linux-based high availability SAP NetWeaver installations, such as using Pacemaker/Corosync clusters.
  • Include Linux shell script examples alongside PowerShell, especially for file share creation, permissions, and cluster resource configuration.
  • Reference Linux-based storage solutions (e.g., NFS, GlusterFS) as alternatives to SOFS/CSV.
  • Add guidance for SAP administrators deploying on Linux VMs in Azure, including differences in cluster setup and SAPMNT share configuration.
  • Clarify in the introduction that the procedures are Windows-specific and link to Linux documentation if available.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md ...ap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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) and related tooling. All examples, procedures, and scripts use Windows-specific technologies (WSFC, SIOS DataKeeper, DNS Manager, Windows Firewall, PowerShell). There are no references to Linux equivalents, nor any mention of how to achieve similar SAP multi-SID HA setups on Linux or with Linux-native clustering tools (e.g., Pacemaker, Corosync). The documentation assumes a Windows-only approach and does not provide parity for Linux users.
Recommendations
  • Add a section describing how to implement SAP ASCS/SCS multi-SID HA on Linux using Pacemaker/Corosync and STONITH.
  • Provide Linux-specific examples for load balancer configuration, disk setup, and cluster resource management.
  • Include Bash or Azure CLI scripts for infrastructure setup alongside PowerShell examples.
  • Reference Linux tools (e.g., crm, pcs, systemd, firewalld) and provide guidance for configuring SAP HA clusters on Linux.
  • Clarify early in the documentation that the guide is Windows-specific, or provide links to equivalent Linux documentation.
  • Ensure all major steps (DNS, load balancer, disk replication, firewall) have Linux alternatives or instructions.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md ...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-08 00:53
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, specifically Windows Failover Clustering (WSFC), and provides only Windows-based examples, tools, and instructions (e.g., PowerShell commands, registry edits, Windows-specific features like Cloud Witness, and SIOS DataKeeper for Windows). There is no mention of Linux equivalents, nor any guidance for setting up SAP ASCS/SCS HA on Linux or using Linux clustering solutions. The documentation assumes a Windows-only environment throughout.
Recommendations
  • Add equivalent guidance for SAP ASCS/SCS high availability on Linux, such as using Pacemaker/Corosync clusters.
  • Provide Linux-based examples for VM creation, disk attachment, and load balancer configuration (e.g., using Azure CLI, shell scripts).
  • Include instructions for configuring shared disks and cluster quorum in Linux environments.
  • Mention Linux-supported third-party solutions for shared disk or replication, if available.
  • Clearly state in the introduction that the guide is Windows-specific, and link to Linux-focused documentation if it exists.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-higher-availability-architecture-scenarios.md ...oads/sap-higher-availability-architecture-scenarios.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific tools and patterns, such as Windows Server Failover Clustering (WSFC), are mentioned first and in detail, while Linux equivalents (Pacemaker) are referenced only briefly and with limited scope (only SUSE Linux Enterprise Server 12+). The majority of architecture diagrams and figures are focused on Windows scenarios (WSFC), with little or no visual or step-by-step coverage for Linux HA solutions. There are no Linux-specific command examples or configuration walkthroughs, and the documentation links and references are predominantly Windows-centric. Linux is acknowledged, but not given equal practical guidance or visibility.
Recommendations
  • Provide equivalent Linux HA architecture diagrams and step-by-step configuration examples (e.g., Pacemaker on RHEL/SLES).
  • Include Linux-specific commands and configuration walkthroughs alongside Windows/PowerShell examples.
  • Reference Linux documentation and SAP notes for Pacemaker and other Linux HA solutions.
  • Expand coverage to include other supported Linux distributions, not just SUSE.
  • Ensure that Linux tools and patterns are mentioned with equal prominence and detail as Windows tools.
  • Add troubleshooting and operational guidance for Linux-based SAP HA deployments.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap-new.md ...ain/articles/sap/workloads/vm-extension-for-sap-new.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Links
Summary
The documentation generally maintains parity between Windows and Linux in terms of examples and instructions, especially in the manual deployment and readiness/health check sections. However, there is evidence of Windows bias in several areas: Windows VM links and instructions are listed first and more prominently in the managed identity configuration section, and most deep links for configuring managed identities are for Windows VMs. Additionally, the documentation references Windows-specific tools and patterns (e.g., PowerShell, Windows VM links) before their Linux equivalents, and the overall structure tends to present Windows options before Linux ones.
Recommendations
  • Ensure that links and instructions for configuring managed identities include Linux VM equivalents and are presented with equal prominence and order.
  • Where possible, alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Add direct links to Linux VM managed identity configuration guides (e.g., Azure portal, CLI, PowerShell, ARM templates) in the relevant sections.
  • Review all sections for tool parity and ensure that Linux-specific tools and patterns are mentioned wherever Windows tools are referenced.
  • Consider adding a summary table or matrix at the top of the page showing both Windows and Linux options for each major step.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md ...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-08 00:53
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 references are Windows-centric, with PowerShell scripts and Windows-specific features (e.g., Failover-Clustering, Cloud Witness). There are no Linux equivalents or alternative approaches mentioned, nor are Linux-based high availability solutions for SAP discussed.
Recommendations
  • Add parallel guidance for deploying SAP ASCS/SCS high availability on Linux, such as using Pacemaker/Corosync clusters.
  • Provide Linux-specific examples and scripts (e.g., shell commands, Ansible playbooks) for infrastructure setup.
  • Reference Azure templates or automation for Linux-based SAP HA clusters.
  • Include a comparison section outlining when to use Windows vs. Linux for SAP HA on Azure.
  • Mention Linux file sharing options (e.g., NFS, GlusterFS) as alternatives to Scale-Out File Server.
  • Ensure that documentation navigation makes Linux options equally discoverable and prominent.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/virtual-machine-scale-set-sap-faq.md ...les/sap/workloads/virtual-machine-scale-set-sap-faq.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing PowerShell for disaster recovery setup and migration tasks, and by highlighting Windows-centric tools and patterns (such as PowerShell scripts and functions) without providing equivalent Linux or cross-platform alternatives. There are no Bash, CLI, or Linux-specific instructions or examples, and Windows tooling is mentioned first and exclusively in migration and recovery scenarios.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell instructions for disaster recovery and migration tasks.
  • Reference cross-platform or Linux-native tools/scripts where available, or clarify if only PowerShell is supported and explain why.
  • Include explicit guidance for Linux administrators, such as steps for configuring managed identities, attaching VMs, and setting up NetApp Files using Linux tools.
  • Ensure that documentation sections mentioning PowerShell also link to or describe equivalent Linux/CLI workflows, or state limitations clearly if parity is not possible.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-shared-disk.md ...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-08 00:53
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), with exclusive use of Windows tools (Failover Cluster Manager, Windows DNS Manager, Windows Firewall, PowerShell scripts) and no mention of Linux equivalents or alternatives. All examples and instructions are for Windows, and there are no Linux-specific steps, commands, or references. The use of PowerShell is pervasive, and Windows terminology and tooling are used throughout, with no parity for Linux-based SAP HA scenarios.
Recommendations
  • Add equivalent instructions and examples for SAP NetWeaver HA installation on Linux clusters (e.g., using Pacemaker/Corosync, SUSE HA, Red Hat HA).
  • Provide Linux shell (bash) commands and scripts for tasks such as DNS configuration, firewall rules, and cluster management.
  • Reference Linux-specific SAP HA guides (such as those for SUSE or Red Hat) alongside Windows guides.
  • Include links to Linux-based Azure SAP HA documentation and templates.
  • Clearly state the scope and limitations at the beginning, and if the guide is Windows-only, provide pointers to Linux guides for parity.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-security-infrastructure.md .../articles/sap/workloads/sap-security-infrastructure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as Group Policy, Windows Firewall, SMB encryption, and Windows security books) are mentioned before or in more detail than their Linux equivalents. Windows examples and recommendations (e.g., Defender XDR blocking on Windows, Windows Malicious Software Removal Tool, Windows Group Policy) are often provided without corresponding Linux examples or parity. Linux guidance is present but sometimes less detailed or appears after Windows content. Some sections (e.g., OS-level hardening) provide more granular Windows instructions, while Linux instructions are more generic. Powershell and Windows-centric deployment/upgrade instructions are referenced without Linux CLI equivalents.
Recommendations
  • Ensure Linux examples and recommendations are provided alongside Windows ones, especially for security tooling, patching, and hardening.
  • Include Linux-specific tools and patterns (e.g., firewalld, SELinux, auditd, Linux-specific malware scanners) where Windows tools are mentioned.
  • Provide parity in detail for both Windows and Linux sections, such as step-by-step guides for configuring security features.
  • When referencing deployment or upgrade instructions (e.g., Trusted Launch), include Linux CLI or Azure CLI examples, not just Powershell or Windows-centric tabs.
  • List Linux and Windows options together (not Windows first) in checklists and recommendations to avoid perceived prioritization.
  • Expand Linux-specific troubleshooting, security, and operational guidance to match the depth of Windows content.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-register-system-cli.md ...center-sap-solutions/quickstart-register-system-cli.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: Windows tools and paths are often mentioned first or exclusively, and some operational examples are missing for Linux. For example, the PowerShell cmdlet Register-AzResourceProvider is referenced before the equivalent Azure CLI command, and the command to check the status of sapstartsrv is only given for Windows, not Linux. File paths for both OSes are listed, but operational commands are more detailed for Windows.
Recommendations
  • Provide Linux equivalents for all operational commands, such as checking the status of sapstartsrv, not just for Windows.
  • When referencing tools or commands (e.g., Register-AzResourceProvider), present the Azure CLI version first or alongside PowerShell to avoid Windows-first bias.
  • Ensure that all examples and instructions are given for both Linux and Windows, especially since SAP systems are commonly deployed on Linux.
  • Where file paths or commands differ by OS, always present both together and with equal detail.
  • Consider adding a table or section that summarizes OS-specific steps for clarity and parity.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-hana.md ...e-docs/blob/main/articles/sap/monitor/provider-hana.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and providing a quickstart link for PowerShell, while not mentioning or linking to any Linux or cross-platform CLI alternatives. There are no Linux-specific instructions or examples, and the use of PowerShell is highlighted before any other automation or scripting options.
Recommendations
  • Include equivalent quickstart links and instructions for the Azure CLI, which is cross-platform and commonly used on Linux.
  • Avoid referencing PowerShell as the only scripting/automation option; mention Azure CLI and Bash where appropriate.
  • Provide examples or notes for Linux users, especially for steps that may differ (such as certificate management or connectivity checks).
  • Ensure that any screenshots or diagrams do not assume a Windows environment unless necessary.
  • Review all prerequisite and setup steps to ensure parity for Linux and Windows users.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-sqlserver.md ...ob/main/articles/sap/workloads/dbms-guide-sqlserver.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is explicitly and exclusively focused on Windows-based SQL Server deployments for SAP workloads on Azure. It repeatedly states that SAP does not support SQL Server on Linux for SAP software, and all configuration, operational, and example sections assume Windows Server as the guest OS. All instructions, tooling, file system references (NTFS, D:\ drive), and high-availability patterns (Always On, clustering) are Windows-centric. There are no Linux equivalents, examples, or even mentions of Linux-based deployment patterns, tools, or file systems. The only mention of Linux is to state it is unsupported for this scenario.
Recommendations
  • If SAP support for SQL Server on Linux becomes available, update the documentation to include Linux-based deployment guidance, examples, and parity for all configuration and operational steps.
  • Where possible, clarify which recommendations are Windows-specific and which are general best practices for SQL Server on Azure, to help users understand what is OS-dependent.
  • Include a section or callout for customers interested in Linux-based SQL Server deployments, even if only to direct them to current support status or alternative documentation.
  • For parity, provide Linux equivalents for file system, disk formatting, and high-availability patterns (e.g., XFS/ext4, mdadm/LVM, Linux clustering/HA options) if/when supported.
  • Avoid assuming Windows-only patterns (such as D:\ drive, NTFS, Windows command line) without noting their OS specificity.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-oracle.md .../blob/main/articles/sap/workloads/dbms-guide-oracle.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally focuses on Oracle on Linux as the primary and recommended platform for SAP on Azure, with detailed configuration, tuning, and deployment guidance for Oracle Linux. However, there is some evidence of Windows bias in the structure and presentation: Windows-specific sections and tools (e.g., Windows Storage Spaces) are presented in dedicated sections, and Windows recommendations are summarized separately, sometimes after Linux. There are also references to Windows tools and patterns (e.g., NTFS, Windows Storage Spaces, Windows Tuning guides), and some configuration tables and examples are provided for Windows. However, Linux is clearly the preferred and more deeply documented platform, with more extensive examples and recommendations. There are few, if any, PowerShell or Windows command-line examples, but the Windows configuration is described in detail. In some cases, Windows considerations are mentioned after Linux, but the parity of detail is not always maintained.
Recommendations
  • Ensure that Linux and Windows configuration sections are equally detailed, with parallel structure and equivalent examples for both platforms.
  • Where Windows-specific tools or patterns are mentioned (e.g., Storage Spaces, NTFS), provide Linux equivalents (e.g., LVM, ext4/XFS) in the same context.
  • If providing configuration tables for Windows, ensure Linux tables are presented with the same level of detail and vice versa.
  • Include example commands for both Linux (bash, systemctl, etc.) and Windows (PowerShell, cmd) where relevant, or clarify when a step is platform-specific.
  • Review the order of presentation: if Linux is the primary supported platform, clarify this early and consistently, but avoid relegating Windows to an afterthought—ensure both are treated as first-class options where supported.
  • Where features are not supported on Windows (e.g., ASM), explicitly state this and provide alternative best practices for Windows users.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md ...kloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC). All operational examples, scripts, and tooling references are for Windows and PowerShell. There is no mention of Linux equivalents, nor are any Linux-based high-availability clustering solutions (such as Pacemaker/Corosync) or Linux command-line examples provided. The documentation assumes a Windows-only context throughout, from infrastructure setup to SAP installation and failover testing.
Recommendations
  • Add a parallel section or separate article for Linux-based SAP ASCS/SCS HA with Azure shared disk, using Pacemaker/Corosync or other supported Linux clustering solutions.
  • Provide Linux command-line examples (e.g., using Azure CLI, shell scripts) for disk creation, attachment, and formatting.
  • Include instructions for configuring load balancers and health probes in Linux environments, referencing relevant Linux tools and configuration files.
  • Describe how to set up DNS entries and cluster resources using Linux-native tools (e.g., `crm`, `pcs`, or systemd-resolved).
  • Reference SAP installation procedures for Linux, including any OS-specific SAP profile or kernel parameter adjustments.
  • Clearly state at the beginning of the article that it is Windows-specific, and provide a link to Linux documentation if available.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md ...ap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Windows Server Failover Clustering (WSFC), Windows tools (such as DNS Manager and Windows Firewall), and PowerShell scripts for Azure resource configuration. There are no references or examples for Linux-based SAP high availability solutions, nor are Linux equivalents or alternative approaches mentioned.
Recommendations
  • Add a parallel section or separate documentation for SAP ASCS/SCS multi-SID HA on Linux, using Pacemaker/Corosync and native Linux clustering tools.
  • Provide equivalent command-line examples for Linux (e.g., using Azure CLI or shell scripts instead of PowerShell).
  • Mention Linux-supported shared disk and replication solutions (such as STONITH, DRBD, or native Azure shared disks with Pacemaker).
  • Reference SAP and Azure documentation for Linux-based high availability setups.
  • Clearly state in the introduction that this guide is Windows-specific, and link to Linux-focused guides if available.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse-pacemaker.md ...ap/workloads/high-availability-guide-suse-pacemaker.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, with extensive Linux-specific instructions and examples. However, there is a notable Windows/Azure bias in several areas: (1) The only provided example for creating and attaching Azure shared disks uses PowerShell, with Azure CLI and Portal relegated to a brief mention and no example; (2) Azure-native tooling and patterns (PowerShell, Azure portal, Azure CLI) are referenced throughout, with no Linux-native alternatives for Azure resource management; (3) In some cross-references and links, Windows is mentioned before Linux (e.g., maintenance documentation links), which can subtly reinforce a Windows-first perspective.
Recommendations
  • Provide full Azure CLI examples for all resource creation and management steps, especially for creating and attaching shared disks, to ensure Linux users can follow along without needing PowerShell.
  • Include explicit instructions or links for performing Azure resource management tasks via the Azure Portal and Azure CLI, not just PowerShell.
  • Where both Linux and Windows are referenced (e.g., maintenance documentation), list Linux first or equally to avoid reinforcing a Windows-first ordering.
  • Where possible, highlight or link to Linux-native automation tools (such as bash scripts using az CLI) for Azure resource management.
  • Clarify that PowerShell is cross-platform, but provide guidance for Linux users on installing and using it if it remains the only example.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/tools-configuration.md ...ob/main/articles/sap/automation/tools-configuration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing file path examples in Windows format (e.g., C:\Users\...), referencing Windows-specific file locations, and omitting equivalent Linux/macOS instructions for saving SSH keys or file paths. The workflow assumes a Windows environment for Visual Studio Code usage and does not provide parallel guidance for Linux users.
Recommendations
  • Include Linux/macOS file path examples alongside Windows paths when instructing users where to save SSH keys (e.g., ~/.ssh/weeu_deployer.ssh).
  • Explicitly mention steps for Linux/macOS users, such as using the terminal to save the SSH key with appropriate permissions (e.g., chmod 600).
  • When referencing Visual Studio Code commands or shortcuts, note any differences for Linux/macOS platforms.
  • Provide screenshots or descriptions that are platform-agnostic or include both Windows and Linux/macOS variants where relevant.
  • Review all instructions to ensure parity for users on non-Windows platforms.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/compliance-bcdr-reliabilty.md ...sap/center-sap-solutions/compliance-bcdr-reliabilty.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation references PowerShell and CLI as the primary interfaces for deploying and managing SAP systems with Azure Center for SAP Solutions, but does not provide explicit Linux/bash examples or mention Linux-native tools. PowerShell is a Windows-centric tool, and its mention without Linux parity can create a perception of Windows bias. There are no screenshots, code snippets, or step-by-step instructions for Linux users, and the documentation does not clarify if all steps are equally supported on Linux platforms.
Recommendations
  • Explicitly provide bash/Azure CLI examples alongside or before PowerShell examples for all deployment and registration steps.
  • Clarify that all CLI commands are cross-platform and provide sample commands in bash syntax.
  • If PowerShell is required, mention PowerShell Core's cross-platform support and provide installation instructions for Linux.
  • Include screenshots or terminal output from Linux environments where applicable.
  • Add a section or note confirming Linux support and parity for all documented procedures.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-create-distributed-non-high-availability.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-create-distributed-non-high-availability.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, and there are no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and prerequisites focus on Azure PowerShell and Cloud Shell, which defaults to PowerShell, and there is no mention of Linux-specific workflows or tools. The documentation does not provide parity for Linux users or those preferring Bash/Azure CLI.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operations.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Include Linux/Bash-specific instructions for preparing the environment, such as installing Azure CLI on Linux.
  • Ensure that sample payload file editing instructions are platform-agnostic or include Linux-friendly editors (e.g., nano, vim).
  • Review all prerequisites and steps to ensure they are not exclusively tailored to Windows/PowerShell users.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/register-existing-system.md ...s/sap/center-sap-solutions/register-existing-system.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools and patterns (such as PowerShell and Windows file paths) are mentioned prominently and sometimes before their Linux equivalents. Some instructions and troubleshooting steps provide detailed guidance for Windows (e.g., PowerShell scripts, Windows VM Agent troubleshooting) but lack equivalent detail or parity for Linux users. In some cases, Linux commands are mentioned, but Windows commands are more explicit or prioritized.
Recommendations
  • Ensure all examples and instructions are provided for both Windows and Linux environments, with equal detail and prominence.
  • When referencing PowerShell or Windows tools, always provide the equivalent Bash or Linux-native command, and vice versa.
  • Avoid listing Windows-specific instructions before Linux equivalents; instead, group them together or alternate their order.
  • Expand troubleshooting sections to include step-by-step guidance for both Windows and Linux VM agents, not just links for one and details for the other.
  • Where file paths or commands are given, always show both Windows and Linux syntax side by side.
  • Review all notes and prerequisites to ensure Linux users are not left with less actionable or less detailed information.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, focusing exclusively on Windows Server Failover Clustering (WSFC), Windows VMs, and Microsoft-specific tools such as PowerShell and Scale-Out File Server. All examples, instructions, and code samples are Windows-centric, with no mention of Linux equivalents, SAP HA on Linux, or cross-platform considerations.
Recommendations
  • Add equivalent guidance for deploying SAP ASCS/SCS HA on Linux, including supported clustering technologies (e.g., Pacemaker, Corosync).
  • Provide Linux-based examples and scripts (e.g., shell commands, Ansible playbooks) alongside PowerShell examples.
  • Mention and link to documentation for Linux-based SAP HA deployments in Azure, ensuring parity in prerequisites and deployment steps.
  • Clarify in the introduction that the guide is Windows-specific, and direct users to Linux documentation if available.
  • Include a comparison table or section outlining differences and similarities between Windows and Linux SAP HA deployments on Azure.
GitHub Create Pull Request
← Previous Page 13 of 26 Next →