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 551-575 of 639 flagged pages
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration-network.md ...ain/articles/sap/workloads/rise-integration-network.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation discusses Azure network connectivity options for SAP RISE but does not provide any OS-specific configuration examples, scripts, or tooling references. However, there is subtle Windows bias: the only DNS server example given is AD DS (Active Directory Domain Services), a Windows technology, and the documentation links to Windows Server AD DS documentation before mentioning BIND (the most common Linux DNS server). No Linux-specific examples, tools, or configuration patterns are provided, and the order of mention prioritizes Windows solutions.
Recommendations
  • Provide explicit Linux/BIND DNS server configuration examples alongside AD DS references.
  • Include links to BIND documentation and guides for DNS integration in Azure.
  • When mentioning DNS solutions, list BIND and AD DS together, or alternate the order to avoid Windows-first bias.
  • Add example scripts or configuration snippets for Linux environments (e.g., shell commands, BIND zone transfer setup).
  • Ensure parity in references to OS-specific tools and patterns throughout the documentation, especially in sections on DNS, firewalls, and network appliances.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-high-availability-netapp-files-suse.md ...kloads/sap-hana-high-availability-netapp-files-suse.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is focused on SAP HANA high availability on SUSE Linux Enterprise Server (SLES) and provides Linux-centric instructions and examples throughout. However, there is evidence of Windows bias in the following areas: (1) The 'services' metadata lists 'virtual-machines-windows' before Linux equivalents, and (2) Load balancer configuration instructions are provided for Azure portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) included as a primary method, even though the scenario is Linux-only. The referenced SAP Notes also mention Windows before Linux in some cases.
Recommendations
  • Remove 'virtual-machines-windows' from the 'services' metadata or list Linux services first, as the guide is exclusively for SLES.
  • In sections describing Azure Load Balancer configuration, prioritize Linux-native tools (Azure CLI, portal) and move PowerShell instructions to a secondary position or a separate note for completeness, clarifying that PowerShell is not required for Linux deployments.
  • Review referenced SAP Notes and documentation links to ensure Linux resources are listed before Windows when the context is Linux-only.
  • Explicitly state that all operational examples and steps are for Linux, and clarify that Windows tools are not required for any part of the process.
  • Audit future documentation for unnecessary inclusion of Windows tooling or terminology in Linux-focused guides.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/manage-virtual-instance.md ...es/sap/center-sap-solutions/manage-virtual-instance.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes management of SAP resources via the Azure portal GUI, with no mention of command-line or automation options. There are no examples or references to platform-specific tools, but the lack of CLI or script-based instructions (such as Azure CLI, Bash, or PowerShell) means that users on Linux are not provided with parity for automation or headless management. The documentation implicitly favors Windows users by focusing solely on the portal experience, which is more commonly used on Windows desktops.
Recommendations
  • Add instructions for managing VIS resources using Azure CLI, including example commands for viewing, monitoring, and deleting VIS resources.
  • Provide script-based examples for common tasks (e.g., retrieving secrets from Key Vault, monitoring resource metrics) using Bash and PowerShell, and clearly indicate platform compatibility.
  • Include references to automation options (such as ARM templates, Terraform, or Ansible) for Linux users who may prefer infrastructure-as-code approaches.
  • Explicitly mention that all portal operations can be performed from any OS with a supported browser, and clarify any limitations or differences for Linux users.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/archived-hli-docs/hana-certification.md ...arge-instances/archived-hli-docs/hana-certification.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page, while focused on SAP HANA on Azure (Large Instances) with Linux as the target platform, references Windows-centric tools and patterns such as RDP servers and Active Directory before mentioning Linux equivalents or alternatives. There is an implicit assumption of Windows infrastructure integration (Active Directory, RDP) without explicit mention of Linux-native options (e.g., SSH, LDAP). No Linux-specific administration or connectivity examples are provided, and Windows tools are listed before Linux alternatives.
Recommendations
  • Include Linux-native connectivity and management options (e.g., SSH jump hosts, LDAP for identity management) alongside or before Windows tools like RDP and Active Directory.
  • Provide examples or references for Linux administration and monitoring tools relevant to SAP HANA on Azure (Large Instances).
  • Clarify that while RDP and Active Directory are supported, Linux-native solutions are equally viable and may be preferred in Linux-centric environments.
  • Ensure parity in documentation by listing Linux tools and patterns first or alongside Windows options, especially given the Linux focus of SAP HANA deployments.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/get-started.md ...e-docs/blob/main/articles/sap/workloads/get-started.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page provides coverage for both Windows and Linux (SLES, RHEL) platforms for SAP on Azure, but there is evidence of Windows bias. Windows-specific tools and patterns (such as Windows Failover Clustering and SMB) are mentioned explicitly and sometimes before their Linux equivalents (Pacemaker, NFS). Windows scenarios (e.g., SQL Server on Windows, AD integration) are called out in dedicated sections and change log entries, while Linux examples are present but not always equally highlighted. There are references to Windows guest OS and Windows clustering, and some change log entries focus on Windows-specific deployments and retirements.
Recommendations
  • Ensure Linux (SLES, RHEL, Oracle Linux) examples and scenarios are presented with equal prominence and detail as Windows examples.
  • When listing supported high availability frameworks, mention Pacemaker and Linux clustering before or alongside Windows Failover Clustering.
  • Provide parity in example walkthroughs, scripts, and troubleshooting steps for both Windows and Linux platforms.
  • Highlight Linux-specific features and optimizations (such as systemd integration, nconnect mount options, Azure fence agents) in summary sections, not just in change logs.
  • Include cross-platform comparison tables for features, limitations, and best practices.
  • Avoid language that implies Windows is the default or preferred platform for SAP on Azure.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration.md ...s/blob/main/articles/sap/workloads/rise-integration.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references both Linux and Windows virtual machines in its metadata, but the main content and examples focus on Microsoft-centric tools and services (e.g., Power App, Power BI, Microsoft Entra ID, Sentinel) without providing Linux-specific integration examples or mentioning Linux-native tools. There are no explicit PowerShell commands or Windows-only instructions, but the examples and integration scenarios are all oriented toward Microsoft/Azure services, with no parity for Linux workflows or open-source alternatives.
Recommendations
  • Include examples of integrating SAP RISE with Azure using Linux-native tools (e.g., CLI, Bash scripts, Ansible, Terraform).
  • Provide sample workflows for Linux administrators, such as configuring network peering or security using Azure CLI on Linux.
  • Mention open-source or cross-platform alternatives to Microsoft-centric services where applicable (e.g., alternatives to Power App, Power BI).
  • Ensure that documentation sections explicitly address both Windows and Linux environments, with step-by-step instructions for each.
  • Add references to Linux-specific troubleshooting and support scenarios in the context of SAP RISE on Azure.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel.md ...articles/sap/workloads/high-availability-guide-rhel.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is focused on SAP NetWeaver high availability on Red Hat Enterprise Linux (RHEL) and provides extensive Linux-specific guidance and examples. However, there is evidence of Windows bias in the prerequisites section, where Windows is mentioned before Linux in the context of supported SAP kernel versions. Additionally, some SAP Notes and references discuss Windows and Linux together, with Windows often listed first. There are no PowerShell-heavy examples, and all technical steps, commands, and configuration instructions are exclusively for Linux. No Linux examples are missing, and no Windows-specific tools or patterns are used in the technical implementation.
Recommendations
  • In the prerequisites section, list Linux before Windows when discussing supported SAP kernel versions to reflect the Linux focus of the guide.
  • Where SAP Notes or documentation mention both Windows and Linux, consider splitting or emphasizing the Linux-specific content first.
  • Ensure that all references, examples, and guidance are tailored to Linux, and avoid mentioning Windows unless directly relevant to the scenario.
  • Review other related documentation pages to ensure consistent Linux-first ordering and parity in examples.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/manual-deployment.md ...blob/main/articles/sap/automation/manual-deployment.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally Linux/CLI-focused, with all command examples using bash, Azure CLI, and Ansible. However, there is evidence of Windows bias in the 'Library configuration' section, where PuTTY (a Windows SSH client) is mentioned as the example SSH client and instructions are given to convert SSH keys to .ppk format for PuTTY. No Linux SSH client (such as OpenSSH) is mentioned, and the Windows tool is referenced first and exclusively. Additionally, the file upload/download instructions reference the Azure Cloud Shell menu, which is more commonly used in browser-based or Windows environments, without mentioning equivalent Linux CLI methods.
Recommendations
  • Mention Linux-native SSH clients (such as OpenSSH) alongside or before PuTTY, and provide instructions for using SSH keys directly with these clients.
  • Include instructions for converting SSH keys for Linux and macOS users, or clarify that conversion is only needed for PuTTY.
  • For file upload/download, provide Linux CLI alternatives (such as scp or rsync) in addition to Cloud Shell menu instructions.
  • Review all tool references to ensure Linux and macOS users are equally supported and not required to use Windows-specific tools.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-webapp.md .../blob/main/articles/sap/automation/configure-webapp.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for app registration, but the Windows example appears after the Linux example, indicating a 'windows_first' bias is not present. However, the PowerShell example is detailed and uses Windows-specific patterns (e.g., Add-Content, Write-Host), which may be unfamiliar to Linux users. There is no evidence of exclusive use of Windows tools or missing Linux examples, as both platforms are covered. The rest of the documentation is platform-neutral, focusing on Azure CLI, Azure Pipelines, and web portal instructions.
Recommendations
  • Ensure that both Linux and Windows examples are equally detailed and use analogous commands where possible.
  • Consider providing a brief explanation of PowerShell-specific commands for users unfamiliar with Windows scripting.
  • Add a note clarifying that Azure CLI commands work in both Bash and PowerShell, and highlight any platform-specific differences.
  • Maintain parity by updating both tabs simultaneously when making changes to example scripts.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-system.md .../blob/main/articles/sap/automation/configure-system.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates mild Windows bias by mentioning Windows failover clustering as a high-availability option before Linux alternatives (Pacemaker), and by listing Windows licensing options in detail. However, most examples and configuration guidance focus on Linux (SUSE, Red Hat), and the only command-line examples are for Azure CLI, which is cross-platform. No PowerShell-specific or Windows-only configuration examples are present, and Linux patterns/tools (Pacemaker, SUSE, RHEL) are well represented.
Recommendations
  • When listing high-availability options, mention Pacemaker (Linux) before or alongside Windows failover clustering to avoid Windows-first ordering.
  • Provide explicit Linux configuration examples where possible, especially for high-availability scenarios, to reinforce parity.
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide any OS-specific notes if needed.
  • Ensure that licensing and configuration options for Linux are described with equal detail as Windows options.
  • If Windows-specific tools or patterns are mentioned, add equivalent Linux guidance or references.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/deploy-s4hana.md ...ain/articles/sap/center-sap-solutions/deploy-s4hana.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for listing available OS image versions, with no equivalent Linux (Bash/Azure CLI) example. This could disadvantage users who primarily use Linux environments or prefer Bash/Azure CLI tools, especially since S/4HANA is typically deployed on Linux. No other Windows-specific tools or patterns are present, and the rest of the instructions are platform-neutral or Azure Portal-based.
Recommendations
  • Provide equivalent Azure CLI (az) and/or Bash examples alongside PowerShell commands for tasks such as listing VM images.
  • Explicitly state that both Windows and Linux command-line tools are supported, and link to relevant Azure CLI documentation.
  • Consider including a note that S/4HANA is typically deployed on Linux, and that Linux-native tools are fully supported for deployment and management.
  • Review other command-line or scripting instructions to ensure parity between Windows and Linux tooling throughout the documentation.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/archived-hli-docs/hana-example-installation.md ...stances/archived-hli-docs/hana-example-installation.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only Windows-based examples for downloading SAP HANA installation packages to the jump box virtual machine. The initial example explicitly states that the operating system is Windows, and there are no equivalent instructions or examples for Linux jump boxes, despite the service being targeted at Linux (as indicated by 'vm-linux' and other metadata). The rest of the installation steps are Linux-centric, but the critical initial download step lacks Linux parity.
Recommendations
  • Add equivalent instructions and examples for downloading SAP HANA installation packages on a Linux jump box, including relevant commands (e.g., using wget, curl, or SAP's download manager for Linux).
  • Ensure screenshots and directory extraction examples are provided for both Windows and Linux environments.
  • Explicitly mention that both Windows and Linux jump boxes are supported, and provide guidance for choosing between them based on user environment.
  • Review and update the documentation to present Linux examples first or in parallel with Windows, given the Linux-centric nature of the service.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse-nfs-simple-mount.md ...loads/high-availability-guide-suse-nfs-simple-mount.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on deploying SAP NetWeaver high availability on SUSE Linux Enterprise Server (SLES) and provides Linux-centric instructions throughout. However, there are signs of Windows bias: (1) The 'services' metadata lists 'virtual-machines-windows', which may mislead readers about platform focus; (2) SAP Notes and prerequisites mention Windows before Linux in supported OS/kernels, and (3) PowerShell is included as a tab for load balancer configuration before Linux CLI, even though the main guide is for Linux. These subtle cues prioritize Windows tools and patterns, despite the content being Linux-oriented.
Recommendations
  • Remove or clarify the 'virtual-machines-windows' service tag in metadata to avoid confusion about platform focus.
  • In prerequisite sections, list Linux before Windows when describing supported OS/kernels for SAP on Azure.
  • For Azure Load Balancer configuration, present Linux CLI examples before PowerShell, or omit PowerShell if not relevant for SLES deployments.
  • Review all SAP Notes and references to ensure Linux instructions are not secondary to Windows, and highlight Linux-specific requirements first.
  • Ensure that all tooling and example commands are relevant to Linux/SLES, and avoid referencing Windows tools unless explicitly needed for hybrid scenarios.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-high-availability.md ...n/articles/sap/workloads/sap-hana-high-availability.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is focused on SAP HANA high availability on SUSE Linux Enterprise Server and provides comprehensive Linux-specific instructions and examples. However, there is evidence of Windows bias in the SAP Notes section, where Windows is mentioned before Linux in the context of supported SAP kernel versions. Additionally, some references and links include Windows alongside Linux, and Windows is mentioned in the context of SAP kernel versions and supported OS combinations. There are no PowerShell-heavy examples, nor are Windows tools or patterns used in the technical steps, which are all Linux-centric.
Recommendations
  • When listing supported platforms or SAP Notes, mention Linux before Windows, or group them together to avoid implying priority.
  • If referencing SAP kernel versions for both Windows and Linux, provide equal detail for both, or focus on Linux if the guide is Linux-specific.
  • Review all references and links to ensure Linux is not secondary to Windows in any context.
  • If Windows is not relevant to the scenario, consider removing Windows mentions from the documentation to maintain focus and avoid confusion.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel-nfs-azure-files.md ...kloads/high-availability-guide-rhel-nfs-azure-files.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on SAP NetWeaver high availability on RHEL with NFS on Azure Files, and is overall Linux-centric. However, there are minor traces of Windows bias: Windows is mentioned in SAP Note 1928533 as a supported OS before Linux, and there are references to required SAP kernel versions for Windows and Linux. Additionally, the documentation includes PowerShell as a tracked devx tool, and PowerShell instructions are provided for configuring the Azure Load Balancer alongside Azure CLI and portal methods, even though the main scenario is Linux-based. No Windows-only examples or tools are used in the actual configuration steps, which are all Linux commands.
Recommendations
  • In SAP Note references and prerequisites, list Linux before Windows when describing supported OS combinations to match the main scenario.
  • In tracked devx tools and example tabs, consider omitting PowerShell or placing Azure CLI and portal instructions before PowerShell, as PowerShell is less relevant for Linux-based deployments.
  • Clarify that PowerShell is included for completeness but is not required for Linux scenarios.
  • Ensure that all example commands and configuration steps remain Linux-focused, and avoid introducing Windows-specific tools or patterns unless strictly necessary for cross-platform parity.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse.md ...articles/sap/workloads/high-availability-guide-suse.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is focused on SAP NetWeaver high availability on SUSE Linux Enterprise Server (SLES) and provides extensive Linux-specific instructions and examples. However, there is evidence of Windows bias: Windows is mentioned first in several places (e.g., in the 'services' metadata and SAP Note summaries), and Windows-specific tools (such as PowerShell) are referenced in the load balancer configuration section before Linux equivalents. The page includes tabs for Azure portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to Linux-native tools. There are no Linux examples missing, and the technical content is strongly Linux-oriented, but the ordering and tool references reflect a subtle Windows-first bias.
Recommendations
  • In SAP Note summaries and service metadata, mention Linux before Windows when the content is Linux-specific.
  • In multi-platform example sections (e.g., load balancer configuration), list Linux-native tools (Azure CLI) before Windows tools (PowerShell), or provide a clear rationale for the ordering.
  • Consider adding a note clarifying that PowerShell is optional and primarily for users on Windows, while Azure CLI is cross-platform.
  • Review and adjust metadata and introductory text to reinforce the Linux focus and avoid unnecessary references to Windows services or tools.
  • Ensure that all example code and instructions are equally detailed for Linux and Windows, and avoid giving Windows tools equal prominence when the target audience is Linux administrators.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration-services.md ...in/articles/sap/workloads/rise-integration-services.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the SAP .NET connector (a Windows-only technology) for RFC/BAPI/IDoc calls and on-premises data gateway scenarios. There are no examples or mentions of Linux-native connectors (such as SAP Java Connector or Python RFC libraries), nor are Linux deployment patterns or tools discussed, despite the page targeting both Linux and Windows virtual machines.
Recommendations
  • Include examples and guidance for integrating SAP RISE with Azure services using Linux-native connectors (e.g., SAP Java Connector, PyRFC).
  • Describe how to deploy and operate the on-premises data gateway on Linux VMs, including any required configuration steps.
  • Mention alternative cross-platform integration runtimes and connectors, and clarify which scenarios support Linux deployments.
  • Add parity in documentation by providing both Windows and Linux examples for connector installation, configuration, and troubleshooting.
  • Explicitly state any limitations or requirements for Linux users when using Azure integration services with SAP RISE.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-start.md ...les/sap/workloads/sap-high-availability-guide-start.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows/WSFC options before Linux equivalents in all major sections (infrastructure preparation, installation). Windows-specific tools and terminology (WSFC, shared disk, file share) are emphasized and described in detail, while Linux options are grouped and referenced with less prominence. The page structure and ordering suggest a primary focus on Windows environments.
Recommendations
  • Alternate the order of Windows and Linux examples in each section, or present them in parallel to avoid implicit prioritization.
  • Provide equal detail and visibility for Linux cluster frameworks and tools (e.g., Pacemaker, GlusterFS, SUSE/RHEL specifics) as is given to Windows/WSFC.
  • Add introductory context that explicitly states parity and support for both Windows and Linux, rather than implying Windows as the default.
  • Include direct links and visual cues for Linux documentation and guides, matching those provided for Windows.
  • Review and update figures and illustrations to ensure Linux scenarios are equally represented.
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows troubleshooting steps before Linux, and references Windows-specific paths and tools (such as C:\Packages\... and Windows process names) before their Linux equivalents. While Linux sections are present and reasonably complete, Windows is prioritized in order and detail, and Windows-specific terminology is used as the default in some instructions.
Recommendations
  • Alternate the order of Windows and Linux sections or present them in parallel to avoid implicit prioritization.
  • Use neutral or dual-platform terminology where possible (e.g., 'process/daemon', 'installation directory').
  • When referencing log files or installation paths, provide both Windows and Linux examples together.
  • Ensure that troubleshooting steps and escalation instructions are equally detailed for both platforms.
  • Consider including a summary table or section that highlights differences and commonalities between Windows and Linux troubleshooting for quick reference.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/hana-example-installation.md ...icles/sap/large-instances/hana-example-installation.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a Windows-centric example for downloading and extracting SAP HANA installation packages, specifically stating that the jump box is a Windows VM and showing screenshots of Windows file extraction. There are no equivalent instructions or examples for Linux-based jump boxes, despite the overall context being SAP HANA on Linux. This may confuse or disadvantage users who are using a Linux jump box, which is common in SAP HANA environments.
Recommendations
  • Provide parallel Linux-based instructions and examples for downloading and extracting SAP HANA installation packages on a Linux jump box.
  • Include Linux command-line examples (e.g., using wget/curl for download, tar for extraction) alongside or before Windows examples.
  • Clarify that both Windows and Linux jump boxes are supported, and structure the documentation to address both use cases equally.
  • Add screenshots or terminal output for Linux-based extraction and file management steps.
  • Review the prerequisites and initial setup sections to ensure they do not implicitly assume a Windows environment.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-ibm-db2.md ...ocs/blob/main/articles/sap/monitor/provider-ibm-db2.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references the Azure portal and provides a quickstart link for both the Azure portal and PowerShell, but does not mention or provide any Linux/CLI (such as Azure CLI or Bash) examples. There is a subtle Windows-first bias by listing PowerShell as the only command-line alternative, with no equivalent Linux-native tooling or instructions. No Linux-specific tools, commands, or patterns are mentioned, and there are no examples for Linux users.
Recommendations
  • Add instructions and examples for creating the IBM Db2 provider using the Azure CLI, which is cross-platform and commonly used on Linux.
  • Where PowerShell is referenced, also provide Bash or shell script equivalents for Linux users.
  • Ensure that all quickstart links and command-line instructions have both Windows (PowerShell) and Linux (Bash/Azure CLI) options, presented with equal prominence.
  • Explicitly mention that the steps are applicable to both Windows and Linux environments, or clarify any OS-specific requirements.
  • If any scripts or tools are required, provide platform-agnostic or dual-platform guidance.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-edge-integration-cell-with-azure.md .../sap/workloads/sap-edge-integration-cell-with-azure.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure Kubernetes Service (AKS) and Azure ARC, both of which are cross-platform but are presented from a Microsoft/Azure-centric perspective. There are no explicit Windows-only tools or PowerShell examples, but there is a lack of Linux-specific guidance, examples, or parity in tooling references. The documentation assumes the use of Azure-managed services and does not mention or provide examples for deploying on non-Azure Kubernetes distributions or using Linux-native tools, which may be relevant for SAP Edge Integration Cell deployments in hybrid or on-premises Linux environments.
Recommendations
  • Include explicit Linux-native deployment examples or references, such as using kubectl on Linux, or integrating with Linux-based Kubernetes distributions outside Azure.
  • Provide parity in tooling instructions, e.g., mention both Azure CLI (which is cross-platform) and Linux shell commands where appropriate.
  • Add a section or note on considerations for Linux administrators, such as SELinux/AppArmor, systemd integration, or Linux networking specifics.
  • Reference or link to SAP Edge Integration Cell documentation for Linux environments, if available.
  • Clarify that AKS and Azure ARC can be managed from both Windows and Linux environments, and provide examples for both.
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/manual-deployment.md ...blob/main/articles/sap/automation/manual-deployment.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely Linux/CLI-centric, using Azure CLI, Bash, and Linux file paths throughout. However, there is a subtle Windows bias in the 'Library configuration' section, where PuTTY (a Windows SSH client) is mentioned as the example for SSH access, and the need to convert SSH keys to .ppk format is called out. No equivalent guidance is given for Linux or macOS SSH clients, and PuTTY is mentioned before any other SSH tool. There are no PowerShell or Windows command prompt examples, but the only explicit client tool mentioned is a Windows one.
Recommendations
  • When referencing SSH clients, mention both Windows (PuTTY) and Linux/macOS (native ssh command) options, and provide guidance for each.
  • Include a note that on Linux and macOS, the SSH keys can be used directly with the ssh command, and conversion to .ppk is only necessary for PuTTY on Windows.
  • If mentioning PuTTY, also mention other popular SSH clients for Windows (e.g., Windows Terminal, OpenSSH for Windows) and clarify that Windows 10+ includes an OpenSSH client.
  • Consider adding a short section or tip box outlining SSH access from all major platforms to ensure parity.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Bash (Linux) and PowerShell (Windows) examples for deployment steps, generally presenting Bash first. However, there is a notable Windows bias in the 'Existing environment scenario', where the SAP system example uses a Microsoft SQL Server back-end running Windows Server 2016, with no mention of a Linux-based alternative. Additionally, some PowerShell examples reference Windows-specific modules and paths, and the documentation references Microsoft SQL Server on Windows as the default database example.
Recommendations
  • In the 'Existing environment scenario', provide an example using a Linux-based database (e.g., HANA on SUSE or Red Hat) to balance the Windows SQL Server example.
  • When referencing database back-ends, mention both Windows and Linux-supported options where possible.
  • Ensure PowerShell examples use cross-platform compatible modules or note any Windows-only dependencies.
  • Explicitly state that both Linux and Windows are supported for all deployment scenarios, and provide parity in example scenarios (e.g., not only Windows Server for databases).
GitHub Create Pull Request
Sap https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/troubleshooting.md ...s/blob/main/articles/sap/automation/troubleshooting.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides troubleshooting steps and command-line examples that are generally platform-agnostic, but there is a subtle Windows bias: there are no explicit Linux shell or bash-specific examples, and no mention of Linux tools or patterns. The only shell commands shown use Azure CLI, which is cross-platform, but there are no clarifications or examples for Linux users (e.g., bash vs. PowerShell syntax differences, environment variable handling). There are no PowerShell-specific commands, but the absence of Linux-specific guidance or examples can be considered a bias.
Recommendations
  • Add explicit Linux (bash) and Windows (PowerShell) command examples where environment variable export or command syntax may differ.
  • Clarify that Azure CLI commands work on both Windows and Linux, and note any OS-specific considerations (such as environment variable syntax: $VAR vs %VAR%).
  • Include troubleshooting steps or references for common Linux environments (e.g., Ubuntu, CentOS) where relevant.
  • Where file paths or configuration locations are mentioned, specify both Windows and Linux path formats if they differ.
  • Add a note or section on how to run the SAP Deployment Automation Framework from both Windows and Linux hosts, including any prerequisites or differences.
GitHub Create Pull Request
← Previous Page 23 of 26 Next →