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 226-250 of 639 flagged pages
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: 2026-01-09 00:34
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 biased towards Windows environments, specifically Windows Server Failover Clustering (WSFC). All examples, instructions, and tooling references are Windows-centric, with exclusive use of PowerShell commands and Windows DNS Manager. There is no mention of Linux-based clustering solutions (e.g., Pacemaker/Corosync), nor any Linux CLI or configuration examples. Supported OS versions are limited to Windows Server, and all operational steps assume a Windows context.
Recommendations
  • Add equivalent instructions and examples for Linux-based SAP HA deployments, such as using Pacemaker/Corosync clusters.
  • Include Linux CLI (e.g., az CLI, shell scripts) examples for disk management, load balancer configuration, and SAP installation steps.
  • Document supported Linux OS versions and highlight any Azure-specific considerations for Linux clusters.
  • Provide guidance on DNS configuration using Linux tools (e.g., bind, dnsmasq) and CLI utilities.
  • Reference SAP notes and installation guides relevant to Linux HA setups.
  • Where PowerShell is used, offer parallel bash or shell script alternatives for Linux users.
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-09 00:34
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-based SAP ASCS/SCS high availability using Windows Server Failover Clustering (WSFC) and related Windows tools. All examples, scripts, and procedures use Windows-specific technologies (WSFC, SIOS DataKeeper, PowerShell, Windows Firewall, DNS Manager), with no mention of Linux equivalents or alternative approaches for SAP HA on Linux. There are no Linux commands, tools, or architectural patterns referenced, and the article assumes a Windows-only environment throughout.
Recommendations
  • Add a section or separate documentation for SAP ASCS/SCS multi-SID HA on Linux, covering Pacemaker/Corosync clusters, Linux-based shared disk solutions, and Azure-specific Linux HA patterns.
  • Provide equivalent Linux command-line examples (e.g., using Azure CLI, shell scripts) for load balancer and VM configuration.
  • Reference Linux cluster management tools and procedures (e.g., crm, pcs, systemd) alongside Windows tools.
  • Clarify in the introduction that the guide is Windows-specific, and link to Linux HA documentation if available.
  • Include a comparison table of Windows and Linux HA architectures for SAP on Azure, highlighting supported features and limitations.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-architecture-scenarios.md ...kloads/sap-high-availability-architecture-scenarios.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools and patterns (such as WSFC) are mentioned first and in more detail, especially for SAP ASCS/SCS instance high availability and multi-SID clustering. Windows deployment options and terminology (WSFC, SMB, SOFS) are presented before or more prominently than Linux equivalents (Pacemaker, NFS). There are more references and links to Windows-specific guides, and some sections (e.g., multi-SID) provide more detail for Windows than Linux. Linux examples are present but sometimes less detailed or appear after Windows options.
Recommendations
  • Ensure Linux deployment options and examples are presented with equal prominence and detail as Windows options.
  • Provide Linux-specific step-by-step guides and references for all major scenarios, matching the depth of Windows documentation.
  • Avoid mentioning Windows tools (e.g., WSFC, SMB) before Linux equivalents (e.g., Pacemaker, NFS) unless contextually necessary; consider parallel presentation.
  • Include explicit Linux command-line examples (e.g., shell scripts, Pacemaker configuration) where Windows PowerShell or GUI steps are shown.
  • Clarify any limitations or differences for Linux deployments upfront, and provide links to external Linux HA resources if needed.
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-09 00:34
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 (such as Storage Spaces Direct, SMB file shares, and SOFS), with no mention of Linux-based clustering solutions or examples. All technical guidance, architecture diagrams, and prerequisites are specific to Windows environments, and there are no references to Linux equivalents or alternative approaches for non-Windows platforms.
Recommendations
  • Add a section or cross-reference for Linux-based SAP ASCS/SCS high availability clustering in Azure, such as using Pacemaker/Corosync, NFS file shares, or other Linux-supported HA solutions.
  • Provide parallel Linux examples or links to Linux documentation for each major architectural pattern described (e.g., file share-based clustering, scale-out file shares, etc.).
  • Mention Linux-supported protocols and file systems (such as NFS, OCFS2, GFS2) where SMB and ReFS are discussed for Windows.
  • Clarify in the introduction or prerequisites that the guide is Windows-specific, and direct Linux users to appropriate resources.
  • Where possible, provide a comparison table or decision matrix to help users choose between Windows and Linux clustering approaches for SAP on Azure.
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-09 00:34
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-based high availability for SAP on Azure, specifically using Windows Server Failover Clustering (WSFC) and Scale-Out File Server. All examples, instructions, and referenced tools are Windows-centric (e.g., PowerShell scripts, Windows features, Azure Cloud Witness). There is no mention of Linux-based clustering solutions, nor any Linux-specific guidance or parity in examples.
Recommendations
  • Add equivalent guidance for SAP high availability on Linux, such as using Pacemaker/Corosync clusters and NFS or other Linux-supported file shares.
  • Provide Linux-based example commands (e.g., shell scripts, cluster configuration steps) alongside PowerShell examples.
  • Reference Azure documentation and templates for deploying SAP HA clusters on Linux VMs.
  • Include a section comparing Windows and Linux approaches for SAP HA on Azure, helping users choose the best fit for their environment.
  • Ensure that prerequisites and next steps include links to Linux documentation for SAP HA on Azure.
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-09 00:34
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, instructions, and tooling references (e.g., PowerShell scripts, CSV volumes, SMB shares, registry edits) are Windows-centric. There are no Linux equivalents or alternative instructions for performing similar SAP NetWeaver high availability installations on Linux clusters, nor are Linux tools or commands mentioned.
Recommendations
  • Add equivalent instructions and examples for Linux-based SAP NetWeaver high availability installations, such as using Pacemaker/Corosync clusters and NFS shares.
  • Provide Linux shell script examples for file share creation, permissions, and cluster resource configuration.
  • Reference Linux documentation and tooling (e.g., crmsh, systemd, NFS, ext4/xfs volumes) alongside Windows tools.
  • Clearly indicate platform-specific sections and offer parity in guidance for both Windows and Linux environments.
  • Include a comparison table or section outlining differences and similarities between Windows and Linux high availability setups for SAP NetWeaver.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Windows technologies (such as Windows Server Failover Clustering, WSFC) are mentioned first and in greater detail, with numerous references to WSFC-specific diagrams and setup steps. There is a lack of equivalent Linux clustering examples or diagrams (e.g., Pacemaker), and Linux support is only briefly mentioned as limited to SUSE Linux Enterprise Server (SLES) 12+. The page references Windows-specific tools and patterns (WSFC, SIOS DataKeeper, .NET Framework installation) without providing Linux alternatives or parity in instructions or visuals. No Linux-specific commands, configuration steps, or architecture diagrams are provided, and the majority of referenced figures and guides are Windows-centric.
Recommendations
  • Add equivalent Linux clustering examples and diagrams (e.g., Pacemaker, Corosync) for SAP high availability scenarios.
  • Provide Linux-specific configuration steps, commands, and troubleshooting guidance alongside Windows instructions.
  • Ensure Linux tools and patterns are mentioned with equal prominence and detail as Windows tools (e.g., explain Pacemaker setup, storage configuration, autostart nuances for Linux).
  • Include architecture diagrams and walkthroughs for SAP on Linux VMs, not just Windows.
  • Clarify support for multiple Linux distributions (not just SLES), or explicitly state limitations.
  • Review all referenced guides and figures to ensure Linux parity, or add Linux-specific versions where missing.
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-09 00:34
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 all examples, diagrams, and configuration steps tailored to Windows environments. There is no mention of Linux equivalents, such as Pacemaker or Corosync, nor any guidance for SAP clustering on Linux. Windows-specific tools and terminology (WSFC, SIOS DataKeeper, Windows Scale-Out File Server, UNC paths, etc.) are used throughout, with no Linux alternatives or parity.
Recommendations
  • Add a section or a separate guide for clustering SAP ASCS/SCS on Linux in Azure, using supported Linux clustering solutions (e.g., Pacemaker, Corosync).
  • Provide Linux-specific examples for shared disk configuration, load balancing, and SAP file sharing (e.g., NFS, Linux mount points).
  • Include diagrams and architecture patterns for SAP high availability on Linux, similar to those provided for Windows.
  • Reference Linux-supported Azure features and third-party solutions for shared storage and failover.
  • Clarify in the introduction that the guide is Windows-specific, and link to equivalent Linux documentation if available.
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-09 00:34
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 related Windows tools (PowerShell, registry edits, Windows-specific features). All examples, instructions, and tooling are for Windows; there are no Linux equivalents or alternative approaches for SAP HA on Azure. Linux clustering technologies (e.g., Pacemaker, Corosync) and Linux-based SAP deployments are not mentioned or supported in this guide.
Recommendations
  • Add equivalent guidance for SAP ASCS/SCS high-availability deployments on Linux, using Azure infrastructure.
  • Provide examples using Linux clustering tools (e.g., Pacemaker, Corosync) and Azure shared disk integration for Linux VMs.
  • Include CLI/bash examples alongside PowerShell for infrastructure provisioning and disk management.
  • Mention Linux support and link to relevant documentation if available, or clarify Windows-only scope at the top.
  • Where registry edits are discussed, provide Linux networking/tuning equivalents (e.g., sysctl settings for TCP keepalive).
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-09 00:34
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 all examples, scripts, and tooling (e.g., PowerShell, Windows DNS Manager, Windows Firewall) being Windows-specific. There are no Linux equivalents, alternative Linux HA patterns, or cross-platform guidance provided. Linux tools and procedures are not mentioned, and the documentation assumes a Windows-only deployment scenario.
Recommendations
  • Add equivalent instructions and examples for SAP NetWeaver HA deployments on Linux clusters (e.g., using Pacemaker/Corosync, SUSE HA, or Red Hat HA).
  • Provide Linux shell script examples for tasks such as firewall configuration, DNS updates, and cluster failover.
  • Reference Linux-based SAP HA guides (such as those for SUSE or Red Hat) alongside Windows guides in the prerequisites and architecture sections.
  • Include a section comparing Windows and Linux HA approaches for SAP on Azure, helping users choose the appropriate platform.
  • Mention and link to Azure documentation for Linux VM clustering and shared disk usage.
  • Where PowerShell is used, provide Bash or Ansible equivalents for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Links
Summary
The documentation demonstrates a moderate Windows bias. In several sections, Windows-specific instructions, links, and examples are presented before their Linux equivalents. The links for configuring managed identities are exclusively for Windows VMs, with only a single Terraform link referencing Linux. While most command examples (PowerShell, CLI, Terraform) do provide both Windows and Linux variants, the ordering and linking favor Windows. The documentation also references Windows tools and patterns (PowerShell, Windows VM links) more frequently and prominently than Linux alternatives.
Recommendations
  • Provide direct links for configuring managed identities on Linux VMs, not just Windows.
  • Ensure that Linux instructions and examples are presented with equal prominence and ordering as Windows examples.
  • Add Linux-specific troubleshooting and configuration links where only Windows links are present.
  • Review and balance the ordering of Windows and Linux examples in all code blocks and instructions.
  • Include references to Linux-native tools or patterns where appropriate, not just PowerShell or Windows-centric approaches.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits moderate Windows bias. Windows-related services, tools, and patterns are often mentioned before their Linux equivalents, and some sections provide more detail or examples for Windows. Windows-specific tools (such as Group Policy, Windows Firewall, Windows Malicious Software Removal Tool) are referenced without direct Linux counterparts, and some links default to Windows or PowerShell tabs. Linux guidance is present but less detailed or is sometimes referenced after Windows. There are few explicit Linux command examples, and some recommendations (e.g., Defender XDR blocking on Windows) are Windows-centric.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal detail and prominence.
  • Provide Linux-specific command-line examples (e.g., for configuring SSH, firewall, SELinux) alongside Windows Group Policy or PowerShell instructions.
  • Reference Linux-native security tools (e.g., iptables, firewalld, auditd, SELinux, AppArmor) where Windows tools are mentioned.
  • Include links to Linux-specific documentation or guides whenever Windows resources are cited.
  • Clarify where features or recommendations differ between platforms (e.g., Defender XDR blocking capabilities, patching workflows).
  • Avoid defaulting to Windows or PowerShell tabs in code or configuration examples; offer Bash/Azure CLI and Linux-native alternatives.
  • Balance the depth of OS-level hardening guidance between Windows and Linux sections.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/virtual-machine-scale-set-sap-deployment-guide.md ...oads/virtual-machine-scale-set-sap-deployment-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Virtual Machine Scale Sets for SAP workloads, but it gives equal prominence to PowerShell (a Windows-centric tool) and does not include any Linux shell scripting or native Linux command examples. The PowerShell section is detailed and present, but there are no bash or Linux-specific instructions, and the CLI examples are generic (not tailored for Linux environments). Additionally, the documentation references the Azure portal, which is cross-platform, but the lack of Linux-specific scripting or automation guidance creates a subtle Windows bias.
Recommendations
  • Add explicit bash/Linux shell scripting examples for common deployment scenarios, especially for users managing SAP on Linux.
  • Clarify in the Azure CLI section that the commands can be run from Linux, macOS, or Windows, and provide sample bash scripts for automation.
  • Include references or links to Linux-specific SAP deployment guides or best practices.
  • Where PowerShell is used, consider providing a bash equivalent or noting when PowerShell Core (cross-platform) can be used on Linux.
  • Highlight any differences or considerations for Linux-based SAP workloads, such as integration with pacemaker or Linux HA tools.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap.md ...ob/main/articles/sap/workloads/vm-extension-for-sap.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows and PowerShell are mentioned before Linux and Azure CLI in several places. SAP Host Agent requirements for Windows are listed before Linux, and PowerShell is referenced as the primary automation tool, with Azure CLI mentioned second. There are no explicit Linux command examples or Linux-first instructions, and Windows tools/patterns are presented first or exclusively in some cases.
Recommendations
  • Present Linux and Windows instructions/examples in parallel, or alternate the order to avoid Windows-first bias.
  • Provide explicit Linux command-line examples (e.g., bash, Azure CLI) alongside PowerShell examples.
  • Reference Linux tools and patterns (such as shell scripting, systemd, etc.) where relevant.
  • Ensure SAP Host Agent requirements for Linux are listed with equal prominence and detail as Windows.
  • Consider adding a table or section that summarizes differences and steps for both platforms side-by-side.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/soft-stop-sap-and-hana-database.md ...enter-sap-solutions/soft-stop-sap-and-hana-database.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 consistently presents Azure PowerShell examples first, followed by CLI and REST API, with no explicit Linux shell or native Linux tool examples. The use of PowerShell as the primary scripting interface suggests a Windows-centric approach, and there is no mention of Linux-specific commands or patterns for SAP system management, despite SAP and HANA being commonly deployed on Linux.
Recommendations
  • Add native Linux shell (bash) examples for all operations, using az CLI or REST API via curl.
  • Clarify that az CLI is cross-platform and provide explicit instructions for Linux environments (e.g., installation, usage in bash).
  • Include references to Linux-native SAP management tools (such as sapcontrol or HDB stop commands) where appropriate, and explain how these integrate with Azure Center for SAP solutions.
  • Reorder examples so that CLI (cross-platform) or REST API are presented before PowerShell, or present all interfaces in parallel.
  • Explicitly mention platform compatibility for each method, helping users on Linux feel equally supported.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse-nfs-azure-files.md ...kloads/high-availability-guide-suse-nfs-azure-files.md
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 is focused on deploying SAP NetWeaver on SUSE Linux Enterprise Server, and the technical steps, examples, and commands are all Linux-centric (bash, Pacemaker, SLES tools). However, there is evidence of Windows bias in the structure and presentation: (1) The 'services' metadata lists 'virtual-machines-windows' before any Linux mention, (2) PowerShell and Azure CLI examples are provided for load balancer configuration, with PowerShell included as a first-class option, and (3) Azure portal instructions and terminology are often Windows-oriented. There is also a tendency to mention Windows prerequisites and kernel versions alongside Linux, even when the guide is Linux-specific.
Recommendations
  • In metadata and introductory sections, list Linux services and tools before Windows equivalents when the guide is Linux-focused.
  • Where multiple example tabs are provided (Azure portal, CLI, PowerShell), ensure Linux-native tools (Azure CLI, bash) are presented first, and PowerShell is clearly marked as optional for Linux users.
  • Remove or de-emphasize Windows-specific prerequisites and kernel version references unless strictly necessary for mixed environments.
  • Add explicit notes clarifying that PowerShell is not required for Linux deployments, and provide bash/CLI alternatives wherever possible.
  • Review terminology and navigation to ensure Linux-first language and context in Linux-centric guides.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-availability-overview.md ...ticles/sap/workloads/sap-hana-availability-overview.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 Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows and PowerShell before Linux alternatives, such as mentioning deployment via the Azure portal or PowerShell first, and linking to Windows VM availability guidance before any Linux equivalent. There are no explicit Linux or Bash examples, nor are Linux-specific tools or patterns discussed. The documentation assumes familiarity with Windows-centric tools and omits Linux parity in examples and recommendations.
Recommendations
  • Explicitly mention Linux VM deployment methods (e.g., Bash, Azure CLI) alongside or before Windows/PowerShell.
  • Provide links to both Windows and Linux VM availability documentation, or a unified cross-platform guide.
  • Include examples and instructions for common Linux administration tasks relevant to SAP HANA on Azure.
  • Reference Linux-specific tools and patterns (e.g., systemd, shell scripting) where appropriate.
  • Ensure that prerequisites and guidance are platform-neutral or balanced between Windows and Linux.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
Although the documentation is focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, there is evidence of Windows bias. The page includes PowerShell-only examples for creating and attaching Azure shared disks, with no equivalent Azure CLI or Bash examples provided. References to Windows maintenance documentation appear before Linux equivalents in some places. The 'services' metadata lists 'virtual-machines-windows' before 'virtual-machines-linux', and some links and instructions reference Windows tools or patterns as defaults.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for all resource creation and management steps, especially for disk attachment.
  • Ensure Linux-first ordering in references, links, and metadata when the content is Linux-centric.
  • Where Windows documentation is referenced, ensure Linux equivalents are mentioned first or in parallel.
  • Review and update metadata ('services', 'ms.service', etc.) to prioritize Linux when appropriate.
  • Audit all sections for implicit Windows tool or workflow assumptions and add Linux-native alternatives.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/supported-product-on-azure.md ...n/articles/sap/workloads/supported-product-on-azure.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 lists supported operating systems for SAP on Azure, but frequently mentions Windows Server before Linux distributions and provides more detail for Windows scenarios (e.g., Oracle DBMS support for non-Unicode SAP systems is only on Windows). There is a tendency to mention Windows as the default or primary platform, with Linux options listed second or as exceptions. Some product support (e.g., Hybris Commerce Platform) is described for Windows/SQL Server first, with Linux/HANA as an alternative. There are no Linux-specific examples, commands, or troubleshooting steps, and Windows is often referenced as the main guest OS for certain SAP components.
Recommendations
  • List Linux distributions before or alongside Windows when describing supported platforms, to avoid implying Windows is the default.
  • Provide Linux-specific examples, scenarios, and troubleshooting steps where Windows examples or details are given.
  • Clarify parity between Windows and Linux support for SAP workloads, especially for Oracle DBMS and SAP Hybris Commerce Platform.
  • Explicitly mention any limitations or differences for Linux users, and provide guidance for migration or configuration.
  • Ensure that references to SAP support notes and product matrices highlight Linux support equally with Windows.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap.md ...ob/main/articles/sap/workloads/vm-extension-for-sap.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 page demonstrates a moderate Windows bias. Windows-specific tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and SAP Host Agent version requirements for Windows are listed before Linux. The documentation references PowerShell cmdlets explicitly, and while Azure CLI is mentioned, it is not given equal prominence. There are no direct Linux shell examples, and Windows patterns/tools are referenced first or exclusively in several places.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell examples for all command-line operations.
  • Mention Azure CLI before or alongside Azure PowerShell to avoid Windows-first ordering.
  • Ensure that Linux-specific requirements (e.g., SAP Host Agent version for Linux) are listed with equal prominence and ordering as Windows requirements.
  • Include references to Linux-native tools and workflows where relevant, such as bash scripts or Ansible, especially in sections discussing automation.
  • Add troubleshooting and deployment guidance specific to Linux environments, not just Windows.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/virtual-machine-scale-set-sap-deployment-guide.md ...oads/virtual-machine-scale-set-sap-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 Powershell Heavy Missing Linux Example
Summary
The documentation provides configuration instructions for Azure Virtual Machine Scale Sets for SAP workloads, including examples for the Azure portal, Azure CLI, and Azure PowerShell. However, there is a notable Windows bias: PowerShell examples are given equal prominence to CLI, and no Linux-specific shell examples (such as Bash scripts or Linux command line nuances) are provided. The documentation references both Windows and Linux as supported OSes, but the example commands and instructions do not demonstrate Linux-native workflows or tools, and the PowerShell section may be less accessible to Linux administrators.
Recommendations
  • Add explicit Bash/Linux shell examples for creating and managing scale sets, especially for Linux administrators who may not use PowerShell.
  • Clarify in the CLI section that the Azure CLI commands are cross-platform and can be run natively on Linux, macOS, and Windows.
  • Consider reordering the example tabs so that Azure CLI (the most cross-platform tool) appears before PowerShell, or make CLI the default tab.
  • Include a note or section highlighting Linux-specific considerations or best practices for SAP workloads on Azure VMSS.
  • Where PowerShell is mentioned, clarify that it is primarily for Windows users, and provide equivalent Linux-native instructions where appropriate.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/plan-deployment.md ...s/blob/main/articles/sap/automation/plan-deployment.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 demonstrates a Windows bias in several areas. Windows-based deployment scenarios are described in detail, including credential naming conventions and Active Directory integration, while equivalent Linux scenarios are not covered with the same depth. PowerShell is used as the primary scripting example, even for testing connectivity from Linux VMs, and Windows-specific tools (PowerShell Gallery, Visual Studio components) are listed explicitly in firewall requirements. There is a lack of Linux-specific examples, such as using Bash or native Linux tools for connectivity tests, and Linux credential management patterns are not discussed in detail.
Recommendations
  • Provide equivalent Linux-based deployment examples, including credential naming conventions and integration with Linux authentication systems (such as LDAP or local accounts).
  • Include Bash or shell script examples for connectivity testing from Linux VMs, rather than only PowerShell scripts.
  • List Linux-specific tools and repositories (e.g., apt/yum sources, OpenSSH, etc.) in the firewall requirements table, alongside Windows tools.
  • Ensure that Linux deployment scenarios are described with the same level of detail as Windows scenarios, including DNS and credential management.
  • Where PowerShell is used for cross-platform scripting, clarify how to install and use PowerShell on Linux, or provide alternative native Linux command examples.
  • Review the order of presentation to avoid always listing Windows tools and patterns before Linux equivalents.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/tutorial.md ...ure-docs/blob/main/articles/sap/automation/tutorial.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 demonstrates a moderate Windows bias. While the main deployment workflow uses Bash and Cloud Shell (which is cross-platform), several instructions and examples reference Windows-specific tools, patterns, and file locations. For example, SSH key saving instructions use Windows paths (e.g., 'C:\Users\<your-username>\.ssh'), and tools like Visual Studio Code and PuTTY are mentioned before or instead of Linux-native alternatives. There are no explicit Linux desktop instructions for SSH key management, and some troubleshooting and tool recommendations are Windows-centric.
Recommendations
  • Provide explicit instructions and examples for Linux and macOS users, especially for SSH key management (e.g., saving keys to ~/.ssh, setting permissions with chmod).
  • Mention Linux-native editors (e.g., nano, vim, gedit) alongside Visual Studio Code and Notepad++.
  • Include PuTTY/PuTTYGen only in a dedicated Windows section, and suggest Linux/macOS alternatives (e.g., ssh-keygen, native SSH clients).
  • Ensure all file path examples use POSIX syntax (~/ or /home/user/) alongside Windows paths.
  • Add troubleshooting steps and tool usage examples for Linux and macOS environments where applicable.
  • Review all screenshots and tool references to ensure they are not exclusively Windows-centric.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/run-ansible.md ...-docs/blob/main/articles/sap/automation/run-ansible.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides parity between Linux and Windows in terms of Ansible playbook usage and example commands, but there is evidence of Windows bias in several areas. Windows-specific tools and Desired State Configuration (DSC) modules (e.g., StorageDsc, NetworkingDsc, ComputerManagementDsc, PSDesiredStateConfiguration, SecurityPolicyDsc) are explicitly listed for Windows OS configuration, while Linux equivalents (such as systemd, networkd, or other configuration management tools) are not mentioned. The Windows sections reference domain joining and Windows Firewall, but the Linux sections do not mention comparable security or identity management tasks. Additionally, the Windows examples assume use of PowerShell modules and patterns, whereas Linux examples use generic bash scripting. In some cases, Windows-specific terminology (e.g., 'failover cluster', 'Always On availability group') is used without Linux equivalents being described in detail.
Recommendations
  • List Linux equivalents for Windows DSC modules (e.g., systemd, firewalld, user/group management tools) in the Linux OS configuration section.
  • Provide more detail on Linux-specific configuration tasks, such as SELinux/AppArmor, firewalld/iptables, and integration with LDAP/AD if applicable.
  • Ensure that security and identity management steps are described for both platforms, not just Windows (e.g., domain joining vs. LDAP/SSSD integration).
  • Where Windows-specific terms are used (e.g., 'failover cluster'), provide Linux equivalents (e.g., Pacemaker, Corosync) and describe their configuration.
  • Consider including troubleshooting tips or references for both platforms, not just Windows.
  • Review the ordering and depth of examples to ensure Linux is not treated as secondary or less detailed than Windows.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/bom-get-files.md ...ocs/blob/main/articles/sap/automation/bom-get-files.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 exhibits Windows bias by referencing Windows-style filenames (e.g., SAPCAR*.EXE), using Windows-centric tools (e.g., Postman, SAP Download Manager), and omitting explicit Linux command-line examples or alternatives. While there are occasional mentions of Linux OS types, practical instructions and examples are tailored to Windows environments, with no parity for Linux users in terms of tooling or step-by-step guidance.
Recommendations
  • Include Linux-specific examples for downloading and extracting SAP media, such as using wget/curl and command-line SAPCAR usage.
  • Provide instructions for using SAP Download Manager on Linux, including installation and execution steps.
  • Offer alternatives to GUI tools like Postman, such as curl or httpie command-line examples for retrieving the DownloadBasket.json manifest.
  • Clarify file naming conventions for both Windows (.EXE) and Linux (no extension or .LINUX) SAPCAR executables.
  • Ensure upload instructions reference both Windows Explorer and Linux file managers/command-line tools (e.g., azcopy, Azure CLI).
GitHub Create Pull Request
← Previous Page 10 of 26 Next →