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 251-275 of 639 flagged pages
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/new-vs-existing.md ...s/blob/main/articles/sap/automation/new-vs-existing.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 provides both Bash and PowerShell examples for deployment steps, but PowerShell commands and Windows-specific tooling (e.g., SAPDeploymentUtilities.psd1, Windows file paths) are consistently presented alongside or immediately after Bash. In some cases, Windows/PowerShell examples use more detailed or named modules (e.g., Import-Module), and Windows file paths are shown without Linux equivalents. The example SAP system in the 'existing environment' scenario uses Microsoft SQL Server on Windows Server 2016, while the 'new deployment' scenario uses SUSE Linux, but the documentation does not provide parity in terms of Linux database options or Linux-specific troubleshooting. There is a slight preference for Windows/PowerShell tooling and patterns, and some examples lack explicit Linux alternatives (e.g., Windows file paths, module imports).
Recommendations
  • Ensure Linux/Bash examples are presented first or equally with PowerShell/Windows examples.
  • Provide Linux equivalents for all Windows-specific tools and modules (e.g., clarify if SAPDeploymentUtilities.psd1 has a Bash equivalent or how to achieve the same functionality in Bash).
  • Use platform-neutral file paths in documentation, or show both Windows and Linux paths explicitly.
  • Expand examples to include Linux database back-ends (e.g., HANA on SUSE, PostgreSQL) in existing deployment scenarios, not just Windows/SQL Server.
  • Add troubleshooting and operational notes for both Linux and Windows environments.
  • Clearly state platform requirements and supported environments for each example.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/integration-sap-cloud-application-library.md ...utomation/integration-sap-cloud-application-library.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 demonstrates a Windows/Azure-centric bias by focusing exclusively on Azure DevOps, Microsoft Entra, Azure Key Vault, and related Microsoft tooling. There are no explicit Linux or cross-platform command-line examples, and the workflow assumes the use of Azure-native tools and interfaces. While there is a brief mention of 'shell scripts' and a link with '?tabs=linux', the step-by-step instructions, screenshots, and tool recommendations are all Microsoft/Azure-specific, with no Linux-native or non-Azure alternatives provided.
Recommendations
  • Provide explicit Linux shell command examples for key steps, such as certificate creation and authentication setup, using standard Linux tools (e.g., OpenSSL, curl) in addition to Azure CLI/PowerShell.
  • Include instructions and examples for using non-Azure CI/CD tools (such as Jenkins, GitLab CI) to run the deployment scripts, not just Azure DevOps.
  • Clarify which steps are cross-platform and which are Azure-specific; offer alternative workflows for users deploying from Linux environments or non-Microsoft ecosystems.
  • Add screenshots or terminal output examples from Linux environments where relevant.
  • Reference and link to SAP CAL documentation for Linux-based automation or CLI usage, if available.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/get-started.md ...-docs/blob/main/articles/sap/automation/get-started.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 exhibits a Windows bias by providing multiple PowerShell-based examples and scripts, especially for key setup tasks such as application registration, pre-flight checks, and Azure DevOps integration. Windows/PowerShell instructions are often presented first or exclusively, with limited or no equivalent Linux/bash examples for several steps. Linux instructions are only provided for a subset of tasks (e.g., installing prerequisites and running the deployer), while many automation and DevOps setup steps lack bash or cross-platform alternatives.
Recommendations
  • Provide bash/Linux equivalents for all PowerShell scripts, especially for application registration, pre-flight checks, and Azure DevOps setup.
  • Clearly indicate which steps are platform-specific and offer guidance for both Windows and Linux users.
  • Where possible, use Azure CLI commands in bash syntax for cross-platform compatibility, rather than embedding them in PowerShell scripts.
  • Add explicit Linux/macOS instructions for running scripts and handling file paths, not just Windows-centric approaches.
  • Review all examples to ensure Linux users can follow the documentation without needing to translate PowerShell to bash themselves.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both Windows and Linux file paths for SAP executables, but Windows-specific tools and commands (such as PowerShell's Register-AzResourceProvider and Windows-specific status checks) are mentioned explicitly and sometimes before their Linux equivalents. There is a lack of parity in example commands for checking SAP service status on Linux, and some instructions reference Windows tools without providing Linux alternatives.
Recommendations
  • Ensure all commands and instructions have both Windows and Linux examples, especially for service status checks and starting processes.
  • Where PowerShell commands are referenced (e.g., Register-AzResourceProvider), provide equivalent Azure CLI or bash commands for Linux users.
  • Present Linux and Windows instructions in parallel, or alternate which platform is presented first to avoid implicit prioritization.
  • Clarify any platform-specific requirements or differences, and link to platform-specific documentation where appropriate.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/start-stop-sap-systems.md ...les/sap/center-sap-solutions/start-stop-sap-systems.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows and Windows Server Failover Clustering (WSFC) before Linux equivalents (RHEL/SUSE and Pacemaker), listing Windows as the first supported OS in multiple places, and referencing Azure PowerShell as a primary tool. There are no explicit Linux shell (bash) or Linux-native tool examples, and the troubleshooting and operational steps do not provide Linux-specific guidance or parity in examples.
Recommendations
  • Alternate the order of OS mentions (e.g., list Linux first in some places, or use alphabetical order).
  • Provide explicit Linux CLI/bash examples and commands alongside PowerShell examples.
  • Include references to Linux-native tools and troubleshooting steps (e.g., systemctl, journalctl, Pacemaker commands) where relevant.
  • Add screenshots or instructions for Linux environments where the UI or experience differs.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows and Linux shells.
  • Ensure parity in cluster management tool documentation, giving equal detail to Pacemaker and WSFC.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/enable-sap-insights.md .../blob/main/articles/sap/monitor/enable-sap-insights.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell script examples for role assignment, referencing the Azure portal and Cloud Shell with instructions to switch to PowerShell, and omitting equivalent Bash or Linux CLI instructions. The onboarding script is a .ps1 PowerShell script, and there is no mention of Linux-native tools or workflows. The documentation assumes familiarity with Windows-centric tooling and does not offer parity for Linux users.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for Linux users alongside PowerShell instructions.
  • Offer a Linux shell script (.sh) version of the onboarding script, or document how to use Azure CLI commands to achieve the same role assignments.
  • Explicitly mention that the steps can be performed from Linux environments and provide guidance for those workflows.
  • Ensure screenshots and instructions reference both Windows and Linux experiences in Azure Cloud Shell (e.g., Bash and PowerShell).
  • Review all steps to confirm that Linux users are not required to switch to PowerShell and can complete the process using their preferred shell.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/businessobjects-deployment-guide.md ...cles/sap/workloads/businessobjects-deployment-guide.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 Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows and Azure SQL Database are frequently mentioned first or exclusively, especially in database and deployment examples. There is a lack of Linux-specific examples, commands, or tooling, and Windows-centric Azure services (e.g., Azure SQL Database, which is only supported for SAP BOBI on Windows) are emphasized. While Linux is acknowledged as a supported OS, practical guidance and parity in examples for Linux deployments are limited.
Recommendations
  • Provide Linux-specific deployment examples, including commands and configuration steps for SUSE, RHEL, and Oracle Linux.
  • Include parity in tooling and database options for Linux, such as step-by-step guides for using Azure Database for MySQL or other supported databases on Linux.
  • Ensure that examples and recommendations are presented for both Windows and Linux, ideally side-by-side, rather than defaulting to Windows-first.
  • Highlight any differences or additional considerations for Linux deployments, such as file system sharing (e.g., NFS setup and HA), security, and networking configurations.
  • Add explicit references and links to Linux-focused documentation and resources, and ensure that the 'Next steps' section includes Linux deployment guides with equal prominence.
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: 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 exhibits a moderate Windows bias. Windows-specific requirements and tools (such as PowerShell scripts, allow-listing www.microsoft.com, and Windows file paths) are mentioned before or in more detail than their Linux equivalents. Some troubleshooting steps and examples are provided only for Windows (e.g., VM Agent troubleshooting), while Linux instructions are less detailed or missing. The use of PowerShell and Windows-centric patterns is prominent, and Linux alternatives are not always given equal coverage.
Recommendations
  • Provide Linux CLI and shell script examples alongside PowerShell instructions, especially for registration and customization steps.
  • Ensure troubleshooting sections include detailed Linux-specific steps and links, matching the depth of Windows guidance.
  • Mention Linux tools and file paths before or alongside Windows equivalents, not after.
  • Clarify when instructions apply to both platforms and highlight any platform-specific differences.
  • Add parity for network configuration, agent management, and SAP process control commands for Linux environments.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/certifications.md ...ocs/blob/main/articles/sap/workloads/certifications.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 Missing Linux Example
Summary
The documentation lists both Windows and Linux as supported platforms for most SAP workloads on Azure, but Windows is often mentioned first in tables and examples. Some products, such as SAP BusinessObjects BI and SAP Business One on SQL Server, are documented as Windows-only, with no Linux alternatives or explanations. There is a lack of Linux-specific configuration examples, and Windows tools (e.g., SQL Server) are referenced more prominently than Linux equivalents.
Recommendations
  • Alternate the order of OS listings to avoid always putting Windows first; consider listing Linux first where appropriate.
  • Provide Linux-specific configuration and deployment examples, especially for products that support both platforms.
  • Where products are Windows-only, explicitly state why Linux is not supported, and offer guidance for Linux users.
  • Include references to Linux-native tools and databases (e.g., PostgreSQL, MariaDB) where relevant, not just Windows-centric options.
  • Ensure parity in documentation depth for both Windows and Linux, including troubleshooting, best practices, and optimization tips.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/data-reference.md ...-docs/blob/main/articles/sap/monitor/data-reference.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page lists many MSSQL-related log tables and references, which are inherently Windows-centric due to SQL Server's historical association with Windows and the use of Windows-specific dynamic management views (DMVs) such as sys.dm_os_windows_info. There are no equivalent examples or references for Linux-based database systems (e.g., PostgreSQL, MySQL) or for SQL Server on Linux. The documentation also does not mention Linux-specific monitoring tools or patterns except for Prometheus exporters, which are listed after the SAP HANA tables and before the MSSQL tables, but the MSSQL section is much more extensive and detailed.
Recommendations
  • Add examples and references for Linux-based database systems commonly used with SAP, such as PostgreSQL or MySQL, if supported.
  • Include SQL Server on Linux-specific DMVs or clarify which MSSQL tables and views are relevant for SQL Server running on Linux.
  • Provide parity in documentation for Linux monitoring tools (e.g., collectd, sysstat) and how their data can be integrated with Azure Monitor for SAP solutions.
  • Balance the depth of documentation between Windows/MSSQL and Linux/OSS database systems to avoid the perception of Windows bias.
  • Explicitly state platform compatibility for each log table and reference, indicating whether it applies to Windows, Linux, or both.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-general.md ...blob/main/articles/sap/workloads/dbms-guide-general.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 (e.g., Storage Spaces) are mentioned before their Linux equivalents (MDADM/LVM), and Windows examples or terminology (e.g., drive D, Windows Server versions) are often presented first or in greater detail. There are references to Windows-centric articles (e.g., SQL Server, Windows VM conversion) and some sections lack parity in Linux-specific guidance (e.g., load balancer configuration examples are Windows-focused). Linux tools are mentioned, but sometimes only as a follow-up or with less detail.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is presented first in each section.
  • Provide equivalent detail and links for Linux-specific tools and procedures (e.g., show how to configure load balancers for HANA System Replication on Linux, not just SQL Server on Windows).
  • Include Linux command-line examples (e.g., shell scripts, systemd units) where Windows PowerShell or GUI steps are shown.
  • Ensure that all recommendations (e.g., disk conversion, storage striping) have explicit Linux instructions and links, not just Windows.
  • Expand Linux-specific troubleshooting and best practices sections to match the depth of Windows coverage.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-sql-server.md .../blob/main/articles/sap/monitor/provider-sql-server.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 page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns. It instructs users to open Windows firewall ports, uses SQL Server Management Studio (a Windows application) for configuration, and links to Windows-specific encryption setup. There are no Linux equivalents or examples provided for firewall configuration, SQL Server management, or secure communication setup, despite SQL Server's support for Linux.
Recommendations
  • Add instructions for opening ports on Linux firewalls (e.g., using ufw or firewalld).
  • Include examples for configuring SQL Server authentication using command-line tools available on Linux (e.g., sqlcmd).
  • Provide guidance for managing SQL Server on Linux, such as using mssql-conf or systemctl for service management.
  • Link to documentation for enabling TLS on SQL Server running on Linux.
  • Ensure parity in examples and steps for both Windows and Linux environments throughout the documentation.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-ibm.md ...ocs/blob/main/articles/sap/workloads/dbms-guide-ibm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (e.g., Storage Pools, PowerShell cmdlets) are mentioned explicitly and sometimes before Linux equivalents (LVM, mdadm). Windows-specific configuration steps (such as using New-StoragePool) are described in detail, while Linux alternatives are referenced but not explained with equivalent depth or examples. Some sections, such as backup/restore, focus on Windows features (VSS) and their limitations, with less coverage of Linux backup tooling. Linux examples (such as NFS mounts and Pacemaker) are present but less frequent and detailed compared to Windows instructions.
Recommendations
  • Provide Linux command-line examples (e.g., LVM and mdadm setup) with the same detail as Windows PowerShell examples.
  • Ensure Linux tools and patterns (LVM, mdadm, Pacemaker) are described before or alongside Windows equivalents, not after.
  • Include Linux-specific backup/restore strategies and tooling, matching the coverage given to Windows (e.g., mention native Linux snapshot/backup tools).
  • Balance the documentation by adding more Linux-focused configuration walkthroughs, troubleshooting steps, and performance tuning advice.
  • Where Windows-specific limitations are discussed (e.g., VSS), provide Linux-specific considerations in parallel.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/exchange-online-integration-sap-email-outbound.md ...oads/exchange-online-integration-sap-email-outbound.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 page demonstrates a Windows bias by exclusively referencing Microsoft 365 Admin Center and Exchange Online PowerShell for configuration steps, without mentioning or providing Linux-based alternatives (such as using Linux mail relay servers, Postfix/Sendmail configuration, or CLI tools). All screenshots and step-by-step instructions assume a Windows-centric environment, and there are no examples or guidance for Linux administrators or those running SAP on Linux servers.
Recommendations
  • Include Linux-specific configuration steps for setting up SMTP relay, such as using Postfix or Sendmail as the intermediary mail server.
  • Provide examples of how to test SMTP connectivity from Linux (e.g., using openssl, telnet, or swaks) in addition to Windows tools.
  • Mention and document how to configure SAP NetWeaver outbound email on Linux-based SAP servers, including relevant commands and configuration file locations.
  • Add guidance for integrating Linux-based relay servers with Exchange Online, including authentication and TLS setup.
  • Ensure parity in screenshots and instructions by showing both Windows and Linux admin workflows where applicable.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-sapiq.md ...s/blob/main/articles/sap/workloads/dbms-guide-sapiq.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 (e.g., Windows Server Failover Cluster, UNC paths, SMB protocol) are described in detail, often before or with more depth than their Linux equivalents. Windows deployment and high-availability solutions are presented first, and the use of Windows-centric terminology (such as WSFC and shared disks) is prominent. Linux alternatives (e.g., Pacemaker, NFS/NetApp Files) are mentioned but with less explanation and fewer practical examples. Some backup/restore examples are Windows-specific (UNC path), with no Linux path examples provided.
Recommendations
  • Ensure Linux deployment and high-availability sections are as detailed as Windows sections, including step-by-step examples and practical guidance.
  • Provide Linux-specific backup/restore examples, such as using NFS paths or typical Linux file system paths.
  • Mention Linux tools (e.g., Pacemaker, Corosync) with equal prominence and detail as Windows Server Failover Cluster.
  • Present Windows and Linux options side-by-side in tables and explanations, rather than listing Windows first.
  • Include troubleshooting and automation examples for Linux environments, similar to those provided for Windows.
  • Clarify any OS-specific limitations or features in a neutral, comparative manner.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-guide-storage.md .../main/articles/sap/workloads/planning-guide-storage.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 Storage Spaces) are mentioned before or more prominently than their Linux equivalents (LVM). High availability scenarios and SMB shares for Windows are described in detail, with Linux/NFS alternatives sometimes mentioned secondarily or less thoroughly. There are references to Windows-specific technologies (e.g., Storage Spaces, SMB) without equivalent detail for Linux (e.g., LVM, NFS). Some examples and guides are Windows-focused, and Linux-specific recommendations or examples are less visible or detailed.
Recommendations
  • Ensure Linux equivalents (such as LVM) are described with equal detail and prominence as Windows tools (e.g., Storage Spaces).
  • When listing supported scenarios or high availability guides, present Linux and Windows options side-by-side, or alternate the order to avoid Windows-first presentation.
  • Provide explicit Linux command-line examples (e.g., using LVM, NFS mount commands) where Windows/PowerShell examples are given.
  • Expand documentation of Linux-specific storage patterns and best practices, especially for SAP workloads.
  • Clarify support for Linux in tables and capability matrices, and avoid language that implies Windows is the default or preferred platform.
  • Add links to Linux-focused guides and troubleshooting resources, ensuring parity with Windows documentation.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel-pacemaker.md ...ap/workloads/high-availability-guide-rhel-pacemaker.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 Tools Windows First
Summary
The documentation page is focused on configuring Pacemaker on RHEL in Azure, with most examples and instructions using Linux-native tools and commands. However, there is a notable Windows bias in the section on configuring Azure shared disks, where only PowerShell examples are provided for disk creation and attachment, despite Azure CLI and portal options being mentioned only in passing. The use of PowerShell as the primary example for resource provisioning may disadvantage Linux users, as PowerShell is more commonly associated with Windows environments. Additionally, references to Microsoft Docs and some Azure resource management patterns (such as managed identities and service principals) are presented in a way that may be more familiar to Windows administrators. The documentation does not provide equivalent Azure CLI examples for disk provisioning, which is the most common tool for Linux users.
Recommendations
  • Provide full Azure CLI examples for creating and attaching Azure shared disks, alongside PowerShell examples, to ensure Linux users have parity and can follow instructions using their preferred tools.
  • Explicitly mention and link to Linux-friendly tooling and workflows (e.g., Bash scripts, Azure CLI) wherever resource provisioning or management is discussed.
  • Where multiple tooling options exist (PowerShell, CLI, Portal), present them in parallel or in a Linux-first order when the target audience is Linux administrators.
  • Review other sections for subtle Windows-first language or assumptions, and clarify that all steps are performed on Linux VMs using Linux-native commands unless otherwise specified.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-zones.md ...main/articles/sap/workloads/high-availability-zones.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 page exhibits several signs of Windows bias. Windows-specific tools, examples, and references (such as Windows Server Failover Clustering and PowerShell scripts) are mentioned before or more prominently than their Linux equivalents. The 'Next steps' section exclusively lists Windows failover cluster guides, omitting Linux cluster equivalents. Where automation is discussed, only PowerShell is referenced, with no mention of Bash or Linux-native tooling. Although Linux is referenced in some supporting documents, the main text and actionable guidance favor Windows approaches.
Recommendations
  • Add equivalent Linux automation examples (e.g., Bash scripts) alongside PowerShell references for tasks such as latency measurement.
  • Include Linux Pacemaker cluster setup guides in the 'Next steps' section, ensuring parity with Windows cluster documentation.
  • When discussing failover cluster solutions, mention Linux Pacemaker and its configuration steps alongside Windows Server Failover Clustering.
  • Ensure that references to tools (e.g., load balancers, fencing agents) include both Windows and Linux usage patterns and links.
  • Review all examples and procedures to provide both Windows and Linux command-line instructions where relevant.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/disaster-recovery-sap-guide.md .../articles/sap/workloads/disaster-recovery-sap-guide.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 Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance for SAP disaster recovery, but there are subtle biases favoring Windows. Windows terminology (e.g., Active Directory, SMB, robocopy, Windows Server Failover Cluster) is mentioned early and sometimes exclusively, and Windows tools/patterns are referenced before or more prominently than Linux equivalents. Some backup/restore and storage replication examples are Windows-centric, and the backup support matrix lists more Windows-supported scenarios. Linux examples are present but sometimes less detailed or referenced after Windows.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal detail and prominence.
  • When referencing tools (e.g., robocopy for SMB), also mention Linux equivalents (e.g., rsync for NFS/SMB) and provide usage examples.
  • Avoid listing Windows-specific technologies (e.g., Active Directory, SMB, robocopy) before Linux alternatives unless contextually necessary; consider a neutral or Linux-first order where appropriate.
  • Expand backup/restore and storage replication guidance for Linux scenarios, ensuring parity with Windows coverage.
  • Where possible, provide cross-platform scripts or commands (e.g., both PowerShell and Bash/CLI) for common DR operations.
  • Review support matrices to ensure Linux scenarios are clearly documented and not implicitly deprioritized.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-file-share.md ...sap/workloads/sap-ascs-ha-multi-sid-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 Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC) and Scale-Out File Server (SOFS) on Azure. All configuration steps, examples, and scripts are provided exclusively for Windows, using PowerShell and Windows-specific tools (Failover Cluster Manager, SMB shares, NTFS permissions). There is no mention of Linux equivalents, alternative clustering solutions (e.g., Pacemaker, Corosync), or cross-platform considerations. The page title, prerequisites, and all technical instructions assume a Windows-only deployment, with no guidance for Linux users.
Recommendations
  • Add equivalent instructions and examples for Linux-based SAP deployments, using tools such as Pacemaker, Corosync, and NFS for file sharing.
  • Include Linux shell script examples for cluster and file share setup, permissions, and SAP Global Host preparation.
  • Reference Azure documentation for Linux high availability clusters and file shares.
  • Clearly state in the introduction whether Linux is supported or provide links to Linux-specific guides.
  • Balance the documentation by presenting both Windows and Linux options side-by-side where possible, or in separate sections.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-guide.md ...ocs/blob/main/articles/sap/workloads/planning-guide.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, while targeting SAP deployments on Azure with a stated focus on Linux VMs, exhibits several signs of Windows bias. Windows tools and concepts (such as Windows Server Active Directory, RDP, Windows failover clustering, and PowerShell) are mentioned frequently and often before or alongside their Linux equivalents. Examples and guidance for Linux-specific tools, patterns, or commands are sparse or missing, and some migration and operational instructions reference PowerShell scripts without providing equivalent Bash/CLI alternatives. In several cases, Windows-centric terminology and solutions are presented as defaults or primary options, with Linux alternatives relegated to secondary mentions.
Recommendations
  • Ensure that every example or tool mentioned for Windows (e.g., PowerShell scripts, Windows Server Active Directory, RDP, Windows failover clustering) is paired with an equivalent Linux example (e.g., Bash/CLI scripts, LDAP/SSSD, SSH, Pacemaker).
  • When referencing migration scripts or automation, provide both PowerShell and Bash/CLI alternatives, or link to cross-platform tools.
  • Present Linux-first examples and guidance, especially in sections where the target platform is Linux (as indicated by ms.tgt_pltfrm: vm-linux).
  • Expand documentation of Linux-specific high-availability frameworks (e.g., Pacemaker) and operational patterns, including troubleshooting and best practices.
  • Avoid using Windows-centric terminology as the default; instead, clarify when a solution is Windows-specific and offer Linux alternatives in parallel.
  • Include more references to Linux-native identity management, encryption, and security tooling, rather than focusing primarily on Windows Server Active Directory and related services.
  • Where SAP Notes or external resources are referenced, clarify their applicability to Linux and Windows, and provide direct links to Linux-relevant documentation.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/deployment-checklist.md ...ob/main/articles/sap/workloads/deployment-checklist.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 several instances of Windows bias. Windows-specific tools, registry settings, and examples are often mentioned first or exclusively (e.g., LogMan, NotMyFault, Windows registry parameters, failover cluster tuning). PowerShell is listed as a primary scripting tool for automation, and some technical details (such as failover cluster configuration and registry tweaks) are only provided for Windows, with Linux equivalents either missing or less detailed. While Linux is referenced and some guidance is given (e.g., LVM, sysstat, nmon), Windows-centric patterns and tools are more prominent, and in some cases, Linux instructions are less thorough or absent.
Recommendations
  • Ensure that for every Windows-specific example or tool, a Linux equivalent is provided and described with equal detail (e.g., registry settings vs. sysctl or network config files).
  • Present automation tooling (PowerShell, CLI, Ansible, Terraform) in a neutral order or prioritize cross-platform tools first.
  • Where Windows tools are referenced (LogMan, NotMyFault), include Linux alternatives (e.g., sysstat, stress-ng, crash, etc.) with usage instructions.
  • Expand Linux-specific configuration and troubleshooting guidance to match the depth given for Windows (e.g., failover cluster settings, network tuning).
  • Review all checklist items and ensure Linux procedures are as explicit and actionable as Windows ones.
  • Consider adding a table or section that directly maps Windows tasks/tools to their Linux equivalents for quick reference.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/deploy-system.md ...ocs/blob/main/articles/sap/automation/deploy-system.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows deployment instructions, but the Windows examples use a custom PowerShell cmdlet (New-SAPSystem), while the Linux instructions use a shell script. The Windows instructions are presented immediately after Linux, and the use of a specialized PowerShell tool may suggest Windows-centric tooling. There is no explicit mention of Linux equivalents for the PowerShell cmdlet, and Windows tools (xcopy) are used without Linux parity discussion.
Recommendations
  • Clarify whether the PowerShell cmdlet (New-SAPSystem) has a direct Linux equivalent or provide a cross-platform CLI tool for parity.
  • Ensure that any custom tools or scripts mentioned for Windows are also available and documented for Linux, or provide alternatives.
  • Present Linux and Windows instructions in parallel, with equal detail and prominence, to avoid implicit prioritization.
  • If Windows-specific tools (like xcopy) are mentioned, provide the Linux equivalent (e.g., cp -Rp) and explain any differences.
  • Document any platform-specific limitations or features so users can make informed choices.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-workload-zone.md ...ain/articles/sap/automation/configure-workload-zone.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Default Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Utility VM parameters' section, where the default image is Windows Server 2019 and the use case is to host SAPGui (a Windows-only tool). There are no Linux-based utility VM examples or mentions of Linux alternatives for SAPGui. Additionally, Windows defaults are specified before Linux options, and Linux parity is not demonstrated in example variable definitions for utility VMs.
Recommendations
  • Provide explicit examples for deploying Linux-based utility VMs, including sample variable definitions.
  • Mention Linux-compatible SAP administration tools (e.g., SAPGui for Java, remote desktop alternatives) as options for utility VMs.
  • Avoid setting Windows Server as the default utility VM image; instead, offer both Windows and Linux options equally.
  • Add a table or section comparing Windows and Linux utility VM use cases, with guidance for both platforms.
  • Ensure that all example code snippets and default values are platform-neutral or include both Windows and Linux variants.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-sap-parameters.md ...in/articles/sap/automation/configure-sap-parameters.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing dedicated sections and parameters for Windows support (such as domain names, SQL Server, and cluster types) while lacking equivalent detail or examples for Linux-specific configurations. Windows-related parameters (e.g., cluster IPs, SQL Server version) are mentioned explicitly and sometimes before Linux alternatives. There are no explicit Linux command-line or configuration examples, and Linux-specific tools or patterns (such as systemd, Linux clustering, or Linux user/group management) are not discussed, despite the majority of SAP deployments being on Linux.
Recommendations
  • Add a dedicated section for Linux support, including parameters and configuration examples relevant to Linux environments (such as systemd services, Linux clustering solutions like Pacemaker, and Linux domain integration).
  • Provide Linux-specific examples for overriding parameters, including command-line and configuration file snippets using typical Linux tools.
  • Ensure parity in documentation by listing Linux equivalents whenever Windows-specific parameters or features are described (e.g., describe Linux clustering options alongside Windows cluster types).
  • Clarify platform-specific requirements and options for each parameter, especially where Windows-only features are mentioned.
  • Include references or links to Linux administration guides for SAP deployments.
GitHub Create Pull Request
← Previous Page 11 of 26 Next →