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 326-350 of 639 flagged pages
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/set-up-network.md ...-docs/blob/main/articles/sap/monitor/set-up-network.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 in the 'Next steps' section and not providing equivalent Linux/CLI examples throughout the guide. The instructions and examples are oriented around the Azure portal and PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. There are no explicit Linux command-line examples or references, and the PowerShell quickstart is mentioned before any Linux alternative.
Recommendations
  • Add Azure CLI (az) command examples alongside or before PowerShell instructions for all relevant steps.
  • Include Linux/Bash-specific guidance or screenshots where applicable, especially for network configuration and DNS settings.
  • In the 'Next steps' section, provide a quickstart for Linux/Azure CLI users and ensure it is listed before or alongside the PowerShell quickstart.
  • Explicitly mention that all steps can be performed on Linux using Azure CLI, and provide links to relevant documentation.
  • Where screenshots are shown, include versions from both Windows and Linux environments if UI differences exist.
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: 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 consistently presents Azure PowerShell (a Windows-centric tool) examples first, followed by CLI and REST API, without providing any native Linux shell or bash examples. There is an implicit assumption that users are familiar with PowerShell, and no explicit Linux command-line (bash) or native SAP/Linux system commands are shown. The documentation also references PowerShell-specific cmdlets and does not mention Linux-specific tools or patterns.
Recommendations
  • Provide bash or shell script examples for Linux users, especially for invoking Azure CLI commands.
  • Alternate the order of examples, sometimes presenting CLI (cross-platform) before PowerShell to avoid implying Windows primacy.
  • Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide sample shell environments.
  • Where possible, include native SAP/Linux commands for soft stopping instances/databases, or at least reference how to do this outside of Azure tooling.
  • Clarify that PowerShell is available cross-platform, but that many Linux users may prefer bash or zsh, and tailor examples accordingly.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments, particularly in the sections referencing Microsoft SQL Server (MSSQL) log tables. All examples and references for database monitoring are focused on SQL Server, which is traditionally a Windows-centric technology, and the referenced system views (such as sys.dm_os_windows_info) are specific to Windows. There are no equivalent examples or references for Linux-based database systems (e.g., PostgreSQL, MySQL) or for running SQL Server on Linux. Additionally, there is a lack of Linux-specific monitoring tools or patterns, and Windows-related tools/views are mentioned exclusively.
Recommendations
  • Include examples and references for Linux-based database systems commonly used with SAP, such as PostgreSQL or MySQL, if supported.
  • If Azure Monitor for SAP solutions supports SQL Server on Linux, clarify this and provide examples or notes on any differences in monitoring/logging.
  • Where possible, balance references to Windows-specific system views (e.g., sys.dm_os_windows_info) with Linux equivalents or note their absence.
  • Highlight or provide guidance on using Linux-native monitoring tools (such as sysstat, sar, or journalctl) where relevant.
  • Explicitly state platform limitations or support to help users on Linux understand what is or isn't available.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/about-azure-monitor-sap-solutions.md ...icles/sap/monitor/about-azure-monitor-sap-solutions.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 listing Azure PowerShell as the only command-line deployment option, omitting equivalent instructions for Linux-native tools (such as Azure CLI or ARM templates). The mention of PowerShell appears before any cross-platform alternatives, and there are no explicit Linux command-line examples or references for deployment or management, despite the product's relevance to Linux-based SAP landscapes.
Recommendations
  • Add Azure CLI examples alongside or before Azure PowerShell for deployment and configuration steps, ensuring Linux users have clear, native instructions.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, ARM templates, Bicep) wherever PowerShell is referenced.
  • Where possible, provide bash or shell script examples for common tasks, especially in sections relevant to Linux-based SAP deployments.
  • Review and update quickstart and configuration links to ensure parity between Windows and Linux workflows.
  • Clarify in the documentation that all features are accessible from both Windows and Linux environments, and provide links to platform-specific guidance where necessary.
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: 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 demonstrates a moderate Windows bias. Windows tools and patterns (such as Windows Server Failover Cluster and SMB/UNC backup paths) are described in more detail and often appear before their Linux equivalents. There are more specific instructions and examples for Windows (e.g., UNC path for backup), while Linux sections lack equivalent command-line or configuration examples. The documentation references Windows-specific tools and deployment guides more prominently, and the Windows deployment section precedes the Linux section in both structure and detail.
Recommendations
  • Provide Linux-first or parallel examples for all procedures, especially for backup/restore commands (e.g., show NFS path usage for Linux backups as is done for Windows UNC paths).
  • Include Linux-native clustering tools (e.g., Pacemaker) with equal detail and example configurations as given for Windows Server Failover Cluster.
  • Ensure that Linux deployment and high-availability solutions are described with the same depth and clarity as Windows, including links to relevant Linux documentation and guides.
  • When listing storage options, avoid presenting Windows options first or in more detail; instead, present both OS options side by side.
  • Add Linux-specific troubleshooting tips and automation scripts where Windows PowerShell or tools are mentioned.
  • Balance the order of sections so that Linux and Windows are treated equally, or use a truly parallel tabbed structure for all OS-specific content.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-devops.md .../blob/main/articles/sap/automation/configure-devops.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 demonstrates a significant Windows bias. Most automation and setup scripts are provided exclusively in PowerShell, with instructions to use PowerShell ISE and Windows-specific command patterns. Linux equivalents are either missing or only appear in a few sections, often after the Windows instructions. The use of Windows tools and terminology (e.g., PowerShell ISE, .ps1 scripts, Windows file paths) is prevalent, and Linux users are only occasionally accommodated, sometimes with minimal or incomplete guidance.
Recommendations
  • Provide all automation and setup scripts in both PowerShell and Bash (or other common Linux shells), ensuring parity in functionality and clarity.
  • Avoid referencing Windows-specific tools (such as PowerShell ISE) as the default or only option; suggest cross-platform editors (e.g., VS Code) or terminal usage.
  • When presenting code blocks, use tabbed or side-by-side examples for Windows and Linux, and ensure both are equally detailed and tested.
  • Ensure all steps (such as downloading, unblocking, and executing scripts) have clear Linux equivalents, not just conditional PowerShell code for Unix.
  • Review all instructions for terminology and paths, replacing Windows-centric language with cross-platform alternatives where possible.
  • Where Azure CLI or other tools are used, provide explicit Linux command-line examples, not just PowerShell wrappers.
  • Audit the documentation for any missing Linux-specific troubleshooting or caveats, and add them as needed.
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: 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 Windows-first bias by frequently mentioning Windows and Azure SQL Database before Linux and MySQL equivalents, especially in architecture and sizing sections. Windows-specific tools and services (e.g., Azure SQL Database, which is only supported for SAP BOBI on Windows) are highlighted, while Linux-specific guidance is less detailed or deferred to external links. There is a lack of Linux-specific examples or step-by-step instructions within the main document, with Linux deployment guidance relegated to a separate page.
Recommendations
  • Provide parallel Linux examples and guidance alongside Windows instructions within the main document, rather than referring users to a separate Linux page.
  • When listing supported operating systems, alternate the order or present Windows and Linux options together to avoid implicit prioritization.
  • Include Linux-specific tools, commands, and configuration steps (e.g., for file sharing, database setup, and high availability) directly in the main guide.
  • Ensure that all Azure services and features discussed (such as storage and database options) clearly indicate Linux compatibility and any differences in implementation.
  • Add explicit Linux architecture diagrams or callouts where implementation details diverge from Windows.
  • Where Windows-only services are mentioned (e.g., Azure SQL Database for SAP BOBI), provide equivalent Linux alternatives and note any limitations or required workarounds.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/disaster-recovery-overview-guide.md ...cles/sap/workloads/disaster-recovery-overview-guide.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. PowerShell is mentioned as the only method for configuring disaster recovery for VMs in scale sets, with no equivalent Linux CLI or Bash example provided. Windows-specific tools like RoboCopy are recommended for SMB file replication, while the Linux alternative (rsync) is only mentioned for NFS scenarios. There is a section specifically referencing 'SAP system running on Windows with Azure shared disk', but no parallel guidance for Linux-based SAP systems. Overall, Windows tools and patterns are mentioned first or exclusively in several places, and Linux-native approaches are underrepresented.
Recommendations
  • Provide equivalent Azure CLI and/or Bash script examples for all PowerShell-only instructions, especially for configuring disaster recovery for VMs in scale sets.
  • When recommending file replication tools, mention both Windows (RoboCopy) and Linux (rsync) options for all relevant storage types (e.g., SMB as well as NFS).
  • Include explicit guidance and examples for SAP systems running on Linux, especially in sections that currently reference only Windows scenarios (e.g., Azure shared disk).
  • Ensure that Linux-native tools and patterns are presented alongside or before Windows equivalents to avoid the appearance of Windows-first bias.
  • Add a table or section summarizing DR strategies for both Windows and Linux SAP workloads, highlighting any differences and providing parity in documentation.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-maxdb.md ...s/blob/main/articles/sap/workloads/dbms-guide-maxdb.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 page demonstrates a strong Windows bias. All deployment, configuration, and backup/restore guidance is exclusively for Windows environments, with repeated references to Windows-specific tools and features (e.g., Windows Storage Pools, Windows Storage Spaces, VSS integration, Microsoft IIS). There are no Linux examples, nor any mention of Linux support, tools, or best practices for SAP MaxDB, liveCache, or Content Server on Azure VMs. The structure and content assume Windows as the default and only platform.
Recommendations
  • Add equivalent sections for Linux deployments, including supported distributions, VM types, and SAP MaxDB/liveCache/Content Server configuration on Linux.
  • Provide Linux-specific storage configuration guidance (e.g., using LVM, mdadm, or other Linux-native tools for disk striping and logical volumes).
  • Include backup/restore instructions and recommendations for Linux, referencing Linux-compatible tools and SAP MaxDB utilities.
  • Mention Linux best practices for performance, security, and monitoring in Azure.
  • Ensure that all platform-specific advice is clearly labeled and that Linux is presented as a first-class option alongside Windows.
  • Where Windows tools (e.g., VSS, IIS, Storage Spaces) are mentioned, provide Linux equivalents or alternatives (e.g., Apache/Nginx for IIS, LVM/mdadm for Storage Spaces, native Linux backup strategies).
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: 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 strives for parity between Windows and Linux, but there are several instances of Windows bias. Windows tools and patterns (e.g., Windows Storage Spaces, drive D:) are often mentioned before or in more detail than their Linux equivalents. In some cases, Windows-specific guidance is more prominent, and Linux alternatives are referenced but not always explained as thoroughly. Some example links and explanations are Windows-centric, and the use of PowerShell or Windows-specific terminology is more prevalent. Linux examples are present but sometimes less detailed or referenced after Windows.
Recommendations
  • Ensure that Linux tools (e.g., LVM, MDADM) are described with equal detail and prominence as Windows tools like Storage Spaces.
  • When presenting examples or recommendations, alternate the order or present both Windows and Linux in parallel, rather than always listing Windows first.
  • Provide direct Linux command-line examples (not just links) where Windows PowerShell or GUI steps are described.
  • Expand Linux-specific notes and best practices to match the depth given to Windows, especially for storage, disk striping, and nonpersistent disk usage.
  • Where Windows-specific terminology is used (e.g., drive letters), provide the Linux equivalent (e.g., mount points) in the same context.
  • Review all referenced articles and ensure Linux parity in linked content as well.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-sapase.md .../blob/main/articles/sap/workloads/dbms-guide-sapase.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 generally provides parity between Windows and Linux in terms of configuration tables and recommendations, but there are several areas where a Windows bias is evident. Windows is often mentioned first in lists and configuration tables, and Windows-specific tools (e.g., Storage Spaces, NTFS, Windows Firewall) are referenced explicitly, sometimes with more detail than their Linux equivalents. Some operational instructions (such as firewall configuration) are only given for Windows, and the section on installing SAP ASE provides a direct link to the Windows installation guide but not to the Linux equivalent. There are also areas where Linux-specific operational guidance is less detailed or missing.
Recommendations
  • Alternate the order of Windows and Linux in configuration tables and lists, or list Linux first in some sections to avoid implicit prioritization.
  • Provide equivalent detail for Linux tools (e.g., LVM2, XFS, firewalld/iptables) as is given for Windows tools like Storage Spaces and NTFS.
  • Add explicit instructions or links for Linux firewall configuration (e.g., firewalld, iptables) where Windows Firewall is mentioned.
  • Include a direct link to the SAP ASE Installation Guide for Linux, as is done for Windows.
  • Ensure operational examples (such as commands, tuning, or troubleshooting) are provided for both platforms where relevant.
  • Where possible, provide sample shell commands for Linux alongside PowerShell or Windows command examples.
GitHub Create Pull Request
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: 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 demonstrates a Windows bias in several ways: Windows tools and clustering frameworks are often mentioned first or in greater detail, with Windows-specific technologies (e.g., Windows Failover Cluster, Windows Scale-Out File Services, SIOS Datakeeper) described before their Linux equivalents. Some sections provide detailed guidance or links for Windows but only brief or less prominent coverage for Linux (e.g., Oracle Linux high availability is not supported, and users are referred to third-party solutions). There are also more explicit recommendations and configuration details for Windows-based scenarios, while Linux alternatives are sometimes less emphasized or require external documentation. Powershell or Windows-centric patterns are implied as defaults in some areas. In a few cases, Linux examples or tools are missing or less detailed.
Recommendations
  • Ensure Linux and Windows solutions are presented with equal prominence and detail, ideally alternating which OS is described first in each section.
  • Provide equivalent step-by-step examples, diagrams, and links for Linux (SUSE, Red Hat, Oracle Linux) as are given for Windows, especially for high availability and disaster recovery scenarios.
  • Include explicit Linux command-line examples (e.g., using shell scripts or systemd) where Windows/Powershell commands or tools are referenced.
  • Clarify support status and recommended patterns for Linux distributions, including Oracle Linux, and provide direct links to official documentation for Linux-based clustering and HA solutions.
  • Where third-party solutions are required for Linux (e.g., SIOS for Oracle Linux), provide more guidance or references to help users achieve parity with Windows-based solutions.
  • Review the order of presentation to avoid always listing Windows first, which can reinforce a perception of Windows as the default or preferred platform.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/deployment-guide.md ...s/blob/main/articles/sap/workloads/deployment-guide.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, while covering both Windows and Linux scenarios, frequently presents Windows tools, requirements, and workflows before their Linux equivalents. PowerShell and Windows-specific tools are often referenced as primary management methods, with Linux alternatives mentioned secondarily or as exceptions. Some sections (e.g., domain join, prerequisites) are Windows-centric or lack Linux parity in detail. There are also more explicit and detailed instructions for Windows tasks (e.g., VM Agent installation, domain join), while Linux instructions are sometimes less detailed or presented as secondary.
Recommendations
  • Present Linux and Windows options in parallel, rather than listing Windows first or as the default.
  • Where PowerShell is referenced, ensure equivalent Azure CLI or Linux-native commands are provided with equal prominence and detail.
  • Avoid language that assumes a Windows management workstation by default; clarify that both Windows and Linux can be used for management tasks.
  • For every Windows-specific example or tool, provide a Linux equivalent (e.g., for joining domains, managing VMs, configuring proxies).
  • Expand Linux sections to match the detail and clarity of Windows instructions, especially for tasks like agent installation, proxy configuration, and post-deployment steps.
  • Where a feature is 'Windows only', clarify if there is a Linux alternative or explicitly state the limitation.
  • Review and update prerequisites to reflect that Linux workstations are fully supported for management and deployment, not just as an exception.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-netweaver.md ...s/blob/main/articles/sap/monitor/provider-netweaver.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 demonstrates a Windows bias by presenting Windows-specific tools (e.g., Microsoft Management Console, PowerShell scripts) before or more prominently than Linux equivalents. PowerShell is used for validation examples, and links/scripts are provided specifically for Windows. Linux instructions are present but sometimes less detailed or secondary. Some automation (e.g., unprotecting web methods) is only referenced for Windows, and troubleshooting steps often lead with Windows approaches.
Recommendations
  • Provide Linux shell script equivalents for all PowerShell scripts and automation steps (e.g., unprotecting web methods).
  • When describing service restarts or management, present Linux and Windows instructions in parallel or in a neutral order.
  • Include references and links to Linux-specific resources and scripts where Windows ones are given.
  • Ensure troubleshooting and validation examples (such as querying SAP Control web methods) are shown for both Windows (PowerShell) and Linux (bash/curl/python).
  • Avoid using Windows tools (MMC, Windows Defender Firewall) as the primary example; instead, offer cross-platform or OS-agnostic instructions.
  • Explicitly state when a step is OS-specific and provide parity in detail and automation for both platforms.
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: 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 demonstrates a moderate Windows bias. While it covers both Windows and Linux high availability scenarios in referenced documents, the main text and examples often mention Windows-specific tools and procedures first or exclusively. For instance, the only automation script for network latency measurement is provided as a PowerShell script, with no mention of a Linux/bash alternative. The 'Next steps' section lists only Windows failover cluster guides, omitting Linux Pacemaker equivalents. Some cluster solution explanations refer to Windows Server Failover Clustering before Linux Pacemaker. This can give the impression that Windows is the primary or preferred platform, and Linux is secondary.
Recommendations
  • Provide Linux/bash equivalents for all automation scripts and procedures (e.g., a bash script for network latency measurement alongside the PowerShell script).
  • Ensure that references to high availability solutions mention Linux Pacemaker and Windows Server Failover Clustering equally and in parallel, rather than listing Windows first.
  • In the 'Next steps' section, add links to Linux high availability guides (e.g., clustering SAP ASCS/SCS with Pacemaker on SUSE/Red Hat).
  • Where possible, use cross-platform terminology (e.g., 'cluster solution' instead of 'Windows failover cluster') and clarify when instructions apply to both Windows and Linux.
  • When mentioning tools or scripts, specify their compatibility (e.g., 'This script is available in both PowerShell for Windows and bash for Linux').
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: 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 covers both Windows and Linux scenarios, but there are subtle biases. Windows tools and patterns (such as Storage Spaces) are mentioned before Linux equivalents (LVM). Some example references and high-availability guides list Windows before Linux, and Windows-specific technologies (e.g., SMB for Windows) are sometimes highlighted first. There are no explicit command-line examples, but where tooling is mentioned, Windows is often foregrounded. Linux-specific details are sometimes less prominent or only mentioned as an afterthought.
Recommendations
  • Ensure Linux and Windows are given equal prominence in all lists and examples, alternating order or grouping by OS where appropriate.
  • When referencing tools for striping or storage management, mention Linux LVM and Windows Storage Spaces together, with equal detail and priority.
  • Where high-availability guides or scenario links are provided, list Linux and Windows guides in parallel, not with Windows first.
  • Add explicit Linux command-line examples (e.g., LVM setup, NFS mounting) alongside any Windows or PowerShell examples.
  • In capability matrices and feature tables, clarify which features apply to Linux, Windows, or both, and avoid defaulting to Windows terminology.
  • For shared storage, ensure NFS (Linux) and SMB (Windows) are described with equal depth and clarity.
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: 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 exclusively focused on Windows Server Failover Clustering (WSFC) for SAP ASCS/SCS high availability in Azure, with all examples, architectures, and tooling (e.g., SIOS DataKeeper, Windows Scale-Out File Server, WSFC) being Windows-specific. There are no references to Linux-based clustering solutions, nor any examples or guidance for Linux environments, despite SAP being widely deployed on Linux. The document assumes a Windows-only context throughout.
Recommendations
  • Include a parallel section or separate documentation for clustering SAP ASCS/SCS on Linux in Azure, covering Pacemaker/Corosync or SUSE HAE/Red Hat HA solutions.
  • Provide Linux-specific examples for shared disk configuration, fencing, and load balancer integration in Azure.
  • Mention Linux support and alternatives wherever Windows tools or patterns (e.g., WSFC, SIOS DataKeeper, Windows Scale-Out File Server) are discussed.
  • Add a comparison table or guidance on choosing between Windows and Linux clustering approaches for SAP on Azure.
  • Ensure that prerequisites and supported OS versions mention Linux distributions and their requirements for SAP clustering.
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: 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 frequently lists Windows before Linux when discussing supported operating systems, and in some cases (such as Oracle DBMS support and SAP Hybris Commerce Platform), Windows is emphasized or described in more detail than Linux. There are also sections where only Windows or Oracle Linux are mentioned as supported OSes, with less clarity or detail for other Linux distributions. No Linux-specific tools, commands, or examples are provided, and the document lacks parity in examples or guidance for Linux users.
Recommendations
  • List Linux distributions before or alongside Windows when enumerating supported operating systems to avoid the impression of Windows primacy.
  • Provide equal detail for all supported Linux distributions, including explicit mention of supported versions and any special considerations, not just for Oracle Linux.
  • Where examples or scenarios are given (e.g., for Oracle DBMS or SAP Hybris Commerce Platform), ensure Linux scenarios are described with the same depth as Windows scenarios.
  • Include Linux-specific guidance, tools, or troubleshooting tips where relevant, not just general or Windows-focused information.
  • Clarify any restrictions or differences for Linux platforms in all relevant sections, ensuring Linux users have clear, actionable information.
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: 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 page exhibits a Windows bias in several ways. Windows-specific tools and patterns (such as Windows Server Failover Clustering, WSFC) are mentioned first and in greater detail, while Linux equivalents (such as Pacemaker) are only briefly referenced and with limited scope (only for SUSE Linux Enterprise Server 12+). The document references many figures and guides related to Windows clustering (WSFC), with no equivalent Linux diagrams or walkthroughs. There are no Linux-specific examples, commands, or step-by-step instructions, and the overall structure and linked resources are heavily skewed toward Windows environments.
Recommendations
  • Provide equivalent Linux examples and walkthroughs, including commands and configuration steps for Pacemaker and other Linux HA solutions.
  • Include diagrams and architecture figures for Linux-based SAP high availability scenarios, not just Windows/WSFC.
  • Mention Linux tools and patterns (such as Pacemaker, Corosync, systemd) alongside Windows tools, and not only as an afterthought or with limited support.
  • Ensure that references, links, and figures are balanced between Windows and Linux, or clearly indicate when a feature is Windows-only.
  • Expand the discussion of Linux support beyond SUSE Linux Enterprise Server, if possible, or clarify the support matrix for other distributions.
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: 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 demonstrates a moderate Windows bias. Windows and PowerShell tools are frequently mentioned first, and in some sections, Windows-specific instructions or links are provided before Linux equivalents. The manual configuration section links only to Windows VM identity guides for Azure portal, CLI, PowerShell, and templates, omitting direct links to Linux VM identity configuration. While most command examples do include both Windows and Linux variants, the ordering and linking patterns prioritize Windows. There is also a heavier emphasis on PowerShell, with more detailed steps and references compared to Linux/CLI.
Recommendations
  • Ensure that all identity configuration links in the manual configuration section include both Windows and Linux VM guides for Azure portal, CLI, PowerShell, and templates.
  • Wherever examples are given for both Windows and Linux, alternate the order or present them in parallel tabs to avoid always listing Windows first.
  • Add explicit Linux-focused instructions and links where only Windows examples or references are currently provided.
  • Review the balance of PowerShell and CLI coverage to ensure Linux users have equally detailed guidance.
  • In summary tables or lists, avoid using 'Windows' as the default or first option; instead, clarify applicability to both platforms.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/proximity-placement-scenarios.md ...rticles/sap/workloads/proximity-placement-scenarios.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for deployment tasks, without any equivalent Azure CLI (cross-platform/Linux-friendly) examples. The PowerShell examples are presented as the default and only method for resource creation and management, and there is no mention or illustration of Linux-native tools or workflows. Although the page links to both Linux (Azure CLI) and Windows (PowerShell) guides at the end, the in-page walkthroughs and code samples exclusively use PowerShell, potentially disadvantaging Linux users.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI example, especially for resource creation and management tasks (e.g., New-AzVm, New-AzAvailabilitySet).
  • When introducing command-line examples, present Azure CLI (cross-platform) examples first or in parallel with PowerShell to avoid implicit prioritization of Windows tooling.
  • Explicitly mention that all operations can be performed on Linux/macOS using Azure CLI, and link to relevant CLI documentation inline.
  • Consider including a section or callout that highlights cross-platform deployment options and best practices for Linux users.
  • Audit the documentation for other instances where Windows-specific tools or workflows are assumed, and ensure Linux parity throughout.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap-standard.md ...rticles/sap/workloads/vm-extension-for-sap-standard.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 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-specific tools (such as azperflib.exe and Windows services) are introduced and explained before their Linux or cross-platform equivalents. The PowerShell workflow is described in greater detail and with more context than the corresponding Azure CLI/Linux instructions. Some troubleshooting and error resolution steps refer to Windows tools or directories first, and the overall structure often presents Windows approaches before Linux ones.
Recommendations
  • Ensure Linux and Windows instructions are presented in parallel or in a consistent order (e.g., always Linux first if the service is Linux-focused, or alternate).
  • Provide equal depth and detail for both PowerShell (Windows) and Azure CLI (Linux/cross-platform) workflows, including troubleshooting steps.
  • Where possible, use cross-platform tools (like Azure CLI) as the primary example, with OS-specific notes as needed.
  • Avoid referencing Windows-specific tools (e.g., azperflib.exe, Windows service directories) without providing equivalent Linux details (e.g., Linux daemons, log locations) in the same section.
  • When describing error codes and solutions, ensure both Windows and Linux log file locations and commands are mentioned together.
  • Review the order of sections and examples to avoid always listing Windows/PowerShell first, especially when the service is available on both platforms.
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: 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) and Scale-Out File Server (SOFS). All configuration steps, code samples, and screenshots are Windows-specific, using PowerShell scripts and Windows administrative tools. There are no Linux equivalents, examples, or even references to Linux-based clustering or file sharing solutions. The documentation assumes a Windows-only approach and does not provide guidance for users operating SAP on Linux or mixed environments.
Recommendations
  • Add a section or parallel documentation for Linux-based SAP high availability, using Pacemaker/Corosync clusters and NFS or other Linux file sharing solutions.
  • Provide Linux shell script examples for file system preparation, permissions, and cluster resource management.
  • Reference Linux-native tools and patterns (e.g., systemd, crmsh, pcs) alongside Windows tools.
  • Clearly state in the introduction if the guide is Windows-only, and link to Linux-specific guides if available.
  • Include comparative diagrams and workflows for both Windows and Linux high availability architectures.
  • Ensure that all major steps (cluster setup, file share configuration, permissions) have Linux equivalents or cross-references.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap-troubleshooting.md .../sap/workloads/vm-extension-for-sap-troubleshooting.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 Powershell Heavy
Summary
The documentation presents Windows troubleshooting steps and directory paths before Linux equivalents, and references Windows-specific tools and log file locations. While Linux troubleshooting is included, Windows is consistently prioritized in order and detail, and there is a lack of parity in example commands or scripts for both platforms.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel tables to avoid implicit prioritization.
  • Provide equivalent example commands or scripts for both Windows (e.g., PowerShell) and Linux (e.g., Bash) where relevant.
  • Reference both Windows and Linux log file paths and tools together when describing troubleshooting steps.
  • Ensure that any mention of support components or log files always lists both Windows and Linux options together, or in alphabetical order.
  • If setup scripts or automation are mentioned, clarify if they are cross-platform or provide separate instructions for each OS.
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: 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, providing only Windows Server Failover Cluster (WSFC) instructions, PowerShell scripts, and references to Windows-specific tools (DNS Manager, Windows Firewall, Failover Cluster Manager). There are no Linux or cross-platform examples, and Linux high-availability patterns (such as Pacemaker/Corosync or SUSE HA) are not mentioned or linked, despite SAP NetWeaver being supported on Linux in Azure. All configuration and troubleshooting steps assume a Windows environment.
Recommendations
  • Add equivalent Linux high-availability installation and configuration steps, referencing Pacemaker/Corosync and SUSE/RHEL HA clusters.
  • Provide Linux shell (bash) command examples alongside PowerShell for tasks such as firewall configuration, cluster management, and DNS updates.
  • Include links to Linux-specific SAP HA documentation (e.g., SAP high-availability guide for SUSE, Red Hat).
  • Clearly indicate in the introduction that this guide is Windows-specific, and cross-reference a Linux-focused guide if available.
  • Where possible, use Azure-native tooling or cross-platform scripts (e.g., Azure CLI) in examples, or provide both Windows and Linux variants.
GitHub Create Pull Request
← Previous Page 14 of 26 Next →