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 626-639 of 639 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally maintains platform neutrality, but there are several instances of Windows bias. Windows terminology (e.g., VHD, SMB) is used as the default, and Windows-specific tools and patterns (such as Storage Spaces and SMB shares) are mentioned before or more prominently than their Linux equivalents. In some capability matrices and scenario lists, Windows options (SMB) are listed before Linux (NFS), and Windows-specific high availability guides are referenced first. There is also a tendency to mention Windows tools (Storage Spaces) before Linux tools (LVM) when discussing disk striping. However, Linux support is present and documented, and most critical tasks can be completed on Linux.
Recommendations
- Ensure that Linux/NFS examples and terminology are presented alongside or before Windows/SMB examples in tables and scenario lists.
- When referencing high availability guides, alternate the order or explicitly mention Linux guides first in some cases.
- When discussing disk striping, mention Linux LVM before or alongside Windows Storage Spaces, and provide example commands for both platforms.
- Add explicit Linux command-line examples (e.g., using LVM, mounting NFS shares) where only Windows/PowerShell or SMB examples are given.
- Clarify that all major SAP scenarios are supported on Linux and provide parity in documentation links and references.
Create Pull Request
Sap
SAP HANA availability on Azure VMs - Overview | Microsoft Docs
...ticles/sap/workloads/sap-hana-availability-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a minor Windows bias by referencing Windows-specific VM availability guidance before any Linux equivalent, and by linking to a Windows VM tutorial for availability sets. However, it does mention the Azure CLI as a cross-platform tool and does not provide examples or instructions that are exclusively Windows or PowerShell-based.
Recommendations
- Include explicit references and links to Linux VM availability documentation alongside or before Windows equivalents.
- Ensure that examples and tutorials for VM deployment and management mention both PowerShell and Azure CLI, with CLI shown first for cross-platform parity.
- Add guidance or links for Linux-specific SAP HANA deployment and high availability best practices on Azure.
Sap
Azure VMs high availability for SAP NetWeaver | Microsoft Docs
...les/sap/workloads/sap-high-availability-guide-start.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently listing Windows/WSFC scenarios and installation steps before Linux equivalents, and by emphasizing Windows-specific tools (WSFC) in headings and links. While Linux (SUSE, RHEL) options are present and covered, the ordering and prominence favor Windows, potentially creating friction for Linux users seeking parity.
Recommendations
- Alternate the order of Windows and Linux sections/examples so Linux is sometimes presented first.
- Provide equal detail and visual prominence for Linux cluster frameworks (e.g., Pacemaker, SUSE HA, RHEL HA) as is given to WSFC.
- Explicitly state that Linux is a first-class platform for SAP NetWeaver on Azure, and highlight Linux-specific advantages where relevant.
- Ensure that all diagrams, figures, and step-by-step guides are available and equally detailed for Linux scenarios.
- Consider a landing page or summary table that presents Windows and Linux options side-by-side, rather than sequentially.
Sap
SAP HANA scale-out with standby with Azure NetApp Files on SLES | Microsoft Docs
...kloads/sap-hana-scale-out-standby-netapp-files-suse.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows in several places, such as SAP kernel version requirements and SAP Note references, but all configuration, deployment, and operational examples are exclusively for SUSE Linux Enterprise Server (SLES). There are no PowerShell or Windows-specific commands, and all instructions use Linux tools and patterns. The only evidence of bias is that Windows is sometimes mentioned first in lists or notes, but the actual guidance is Linux-centric.
Recommendations
- When listing supported platforms or SAP notes, mention Linux before or alongside Windows to reinforce the Linux focus.
- Remove or clarify references to Windows in SAP notes if they are not relevant to the procedure.
- Ensure that any platform-agnostic prerequisites or requirements are clearly separated from Windows-specific information.
- If Windows is not supported for this scenario, explicitly state this to avoid confusion.
Sap
Troubleshoot the Azure VM Extension for SAP | Microsoft Docs
.../sap/workloads/vm-extension-for-sap-troubleshooting.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows troubleshooting steps before Linux, and references Windows-specific paths and tools (e.g., C:\Packages\Plugins\...) before their Linux equivalents. While Linux troubleshooting is covered, the ordering and initial focus on Windows may create minor friction for Linux users.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel for each troubleshooting scenario.
- Ensure examples and log file paths for both platforms are presented together or in a side-by-side format.
- Explicitly mention Linux tools and commands where relevant, not just directory paths.
- Add a summary table comparing Windows and Linux troubleshooting steps for quick reference.
Sap
SAP HANA scale-out with standby with Azure NetApp Files on SLES | Microsoft Docs
...kloads/sap-hana-scale-out-standby-netapp-files-suse.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is focused on deploying SAP HANA scale-out with standby on SUSE Linux Enterprise Server (SLES) using Azure NetApp Files. While the technical content and examples are entirely Linux-centric, there is evidence of Windows bias in the metadata: the 'ms.tgt_pltfrm' field is set to 'vm-windows', and several SAP notes and references mention Windows before Linux (e.g., kernel version requirements for Windows and Linux). However, all configuration steps, code samples, and operational guidance are exclusively for Linux, with no PowerShell, Windows tools, or Windows-specific patterns presented.
Recommendations
- Update metadata ('ms.tgt_pltfrm') to reflect Linux as the target platform, or include both Windows and Linux if appropriate.
- Ensure that references to SAP notes or requirements list Linux before Windows when the documentation is Linux-focused.
- Review and remove any residual Windows-centric language or ordering in lists, notes, or references.
- If Windows is not supported for this scenario, clarify this explicitly to avoid confusion.
- If Windows support is planned, provide equivalent Windows examples and instructions for parity.
Sap
SAP HANA scale-out with standby with Azure NetApp Files on RHEL| Microsoft Docs
...kloads/sap-hana-scale-out-standby-netapp-files-rhel.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on SAP HANA deployment on Red Hat Enterprise Linux (RHEL) and provides Linux-specific instructions and examples throughout. However, there is evidence of Windows bias in the metadata: the 'ms.tgt_pltfrm' field is set to 'vm-windows', and several SAP notes and references mention Windows before Linux (e.g., kernel version requirements for Windows and Linux). No PowerShell examples, Windows tools, or Windows-only patterns are present in the main content, and all technical steps use Linux commands and conventions.
Recommendations
- Update metadata to accurately reflect the Linux focus (e.g., set 'ms.tgt_pltfrm' to 'vm-linux' or remove if not relevant).
- Where SAP notes or references mention both Windows and Linux, consider listing Linux first or providing Linux-specific context.
- Review cross-references and ensure that Linux documentation is prioritized or equally represented in related links and guides.
- Ensure that any mention of Windows is only present where relevant for mixed environments, and clarify when instructions are Linux-only.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-scale-out-standby-netapp-files-suse.md
...kloads/sap-hana-scale-out-standby-netapp-files-suse.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is focused on deploying SAP HANA scale-out with standby on SUSE Linux Enterprise Server (SLES) using Azure NetApp Files. The content and all examples are Linux-centric, with explicit instructions for SLES and Linux commands. However, there is minor evidence of Windows bias: in the SAP Notes section, Windows is mentioned before Linux when listing required SAP kernel versions for Azure, and the metadata field 'ms.tgt_pltfrm' is set to 'vm-windows', which could indicate a default Windows platform targeting. No PowerShell, Windows-specific tools, or missing Linux examples are present; all operational steps use Linux commands and tools.
Recommendations
- In SAP Notes and references, mention Linux before Windows when the guide is Linux-focused.
- Update metadata (e.g., ms.tgt_pltfrm) to reflect Linux as the primary target platform for this guide.
- Ensure that any cross-platform references or prerequisites are clearly separated and Linux is prioritized in Linux-specific documentation.
- Review all introductory and summary sections to confirm that Linux is presented as the default context for this scenario.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/manage-with-azure-rbac.md
...les/sap/center-sap-solutions/manage-with-azure-rbac.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation is platform-neutral in its description of Azure RBAC roles and permissions for SAP workloads, focusing exclusively on Azure resource roles, permissions, and actions. However, it lacks any practical command-line examples or tool references for managing these permissions, such as Azure CLI, PowerShell, or REST API. This absence means there is no explicit Windows bias, but also no Linux parity: users are not shown how to perform these tasks using either Windows (PowerShell) or Linux (Azure CLI, Bash) tools.
Recommendations
- Add practical examples for assigning roles and permissions using both Azure CLI (cross-platform, Linux-friendly) and PowerShell (Windows-centric).
- When showing command-line examples, present Azure CLI first or alongside PowerShell to ensure Linux parity.
- Explicitly mention that all Azure RBAC operations can be performed from Linux, macOS, and Windows using Azure CLI and REST API.
- Include links to Azure CLI documentation for role assignment and permission management.
- If scripting is discussed, provide sample scripts in Bash (for Linux) and PowerShell (for Windows).
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/enable-dedicated-hosting-plan.md
.../articles/sap/monitor/enable-dedicated-hosting-plan.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation avoids explicit Windows bias by not mentioning Windows-specific tools or PowerShell. However, it also does not provide any OS-specific command-line examples or considerations. The only CLI instructions use Azure CLI, which is cross-platform, but there are no examples or notes about running these commands on Linux or macOS, nor are there screenshots or troubleshooting steps for non-Windows environments. This could lead to a subtle bias by omission, as Linux users may not feel fully supported.
Recommendations
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- Add a note or example showing how to install Azure CLI on Linux (e.g., using apt, yum, or Homebrew).
- Include screenshots or terminal examples from a Linux shell (e.g., bash) in addition to or instead of GUI screenshots.
- Mention any OS-specific considerations (such as shell differences, permissions, or environment variables) if relevant.
- Ensure troubleshooting steps are inclusive of both Windows and Linux environments.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/devops-tutorial.md
...s/blob/main/articles/sap/automation/devops-tutorial.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line examples or tool references, but it lacks any mention of the operating system used for the self-hosted agent or the pipelines. There are no examples or guidance for Linux users, nor is there clarification on whether the steps are OS-agnostic. This omission may leave Linux users uncertain about compatibility or required setup.
Recommendations
- Explicitly state which operating systems are supported for the self-hosted agent and pipelines (e.g., Windows, Linux, macOS).
- Provide setup instructions or references for both Windows and Linux self-hosted agents.
- Include example commands or screenshots for both Windows and Linux environments where relevant (e.g., agent installation, file paths).
- Clarify any OS-specific requirements or differences in the deployment process.
- If the process is OS-agnostic, explicitly state this to reassure users on all platforms.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-information-lifecycle-management.md
.../sap/workloads/sap-information-lifecycle-management.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or commands, but it also does not include any Linux-specific guidance, scripts, or CLI instructions, despite being tagged for both Linux and Windows. The instructions are generic and do not reference Windows tools or PowerShell, but the lack of explicit Linux (or cross-platform) command-line examples may disadvantage Linux users.
Recommendations
- Add explicit Azure CLI examples for each step, as Azure CLI is cross-platform and commonly used on Linux.
- Include sample shell (bash) commands for Linux environments, especially for steps like registering applications and assigning roles.
- If any PowerShell or Windows-specific steps are relevant, ensure equivalent Linux/bash instructions are provided and presented with equal prominence.
- Clarify in each step whether the instructions are platform-agnostic or if there are differences between Windows and Linux environments.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/devops-tutorial.md
...s/blob/main/articles/sap/automation/devops-tutorial.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not explicitly show Windows bias in the form of Windows/Powershell examples or tools, but it also does not mention or provide examples for Linux environments, tools, or shell commands. There is a lack of OS-specific guidance, which may implicitly assume a Windows-centric approach, especially given Azure DevOps' historical ties to Windows. The only mention of agents is 'self-hosted agent virtual machine,' with no indication of supported operating systems or setup instructions for Linux-based agents.
Recommendations
- Explicitly state which operating systems are supported for self-hosted agents (e.g., Windows, Linux, macOS).
- Provide setup instructions or references for both Windows and Linux self-hosted agents in the prerequisites section.
- If any scripts, commands, or pipelines require OS-specific steps, include both Windows (e.g., PowerShell) and Linux (e.g., Bash) examples.
- Clarify if the SAP Deployment Automation Framework or any pipelines have OS dependencies or recommended platforms.
- Add notes or links to Azure DevOps documentation on configuring self-hosted agents for Linux.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references the Azure portal and PowerShell quickstarts in the prerequisites, listing the portal (GUI, cross-platform) first and PowerShell (primarily Windows-centric) second. There are no explicit Linux CLI (such as Azure CLI/bash) examples or references, and no mention of Linux-specific tools or workflows. However, the main configuration steps are platform-agnostic SQL scripts and portal instructions, so the bias is subtle and limited to the quickstart references.
Recommendations
- Add a quickstart link or reference for Azure CLI (az) usage alongside the portal and PowerShell quickstarts, to provide parity for Linux and cross-platform users.
- Explicitly mention that the steps can be performed from any OS, and provide examples or notes for Linux users where relevant.
- If any scripts or automation are provided in future updates, ensure both PowerShell and Bash (or shell-agnostic) examples are included.