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 126-150 of 639 flagged pages
Sap
Configure SAP HANA provider for Azure Monitor for SAP solutions
...e-docs/blob/main/articles/sap/monitor/provider-hana.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell in the prerequisites and providing a quickstart link for PowerShell, while omitting equivalent Linux or cross-platform CLI examples. The ordering also places the Azure portal and PowerShell options before any mention of Linux tools or Azure CLI, and there are no explicit Linux instructions or screenshots.
Recommendations
- Add quickstart links and instructions for Azure CLI, which is cross-platform and commonly used on Linux.
- Include examples or references for configuring the SAP HANA provider using Linux-based tools or scripts.
- Ensure screenshots and step-by-step instructions are not Windows-specific and clarify that the Azure portal is accessible from any OS.
- Explicitly mention Linux compatibility in prerequisites and configuration steps.
- Balance references to PowerShell with Azure CLI or Bash alternatives.
Create Pull Request
Sap
Configure SAP NetWeaver for Azure Monitor for SAP solutions
...s/blob/main/articles/sap/monitor/provider-netweaver.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools (MMC, MC, Windows Defender Firewall) are mentioned before their Linux equivalents, and PowerShell scripts are referenced for key configuration steps. Some troubleshooting and configuration instructions provide Windows-specific guidance or scripts, while Linux alternatives are present but less emphasized or detailed. In several places, Windows steps or tools are described first, and links to Windows-specific scripts are provided without equivalent Linux resources. There are also references to PowerShell for validation and configuration, but no corresponding Bash or shell script examples for Linux users.
Recommendations
- Ensure Linux instructions and tools are presented with equal prominence and detail as Windows equivalents, including screenshots and step-by-step guides.
- Provide Bash or shell script examples for configuration and validation tasks currently covered only by PowerShell scripts.
- When referencing external scripts or resources, offer both Windows and Linux versions, or clarify platform applicability.
- Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
- Include troubleshooting steps and examples for Linux environments with the same level of detail as for Windows.
- Review all links and resources to ensure Linux users have access to equivalent guidance and automation.
Sap
Set up a network for Azure Monitor for SAP solutions
...-docs/blob/main/articles/sap/monitor/set-up-network.md
High Priority
View Details →
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 providing a quickstart specifically for PowerShell, while omitting equivalent Linux/CLI examples. The workflow instructions and portal navigation are presented in a way that assumes use of the Azure portal (which is platform-agnostic but often associated with Windows environments), and there is no mention of Linux-specific tools or command-line instructions (such as Azure CLI or Bash scripts). Additionally, examples for configuring network rules and integration are described in terms of Azure portal UI navigation, with no alternative for Linux users who may prefer scripting or CLI approaches.
Recommendations
- Add Linux/CLI examples alongside PowerShell instructions, such as using Azure CLI or Bash scripts for network setup and configuration.
- Include a 'Quickstart: Set up Azure Monitor for SAP solutions with Azure CLI' in the Next steps section.
- Provide explicit instructions for configuring NSG rules and subnet integration using CLI commands, not just portal navigation.
- Ensure that references to PowerShell are balanced with equivalent Linux tooling (e.g., Bash, Azure CLI) throughout the documentation.
- Where screenshots or UI instructions are used, offer parallel command-line alternatives for users on non-Windows platforms.
Sap
Microsoft Azure certifications for SAP | Microsoft Docs
...ocs/blob/main/articles/sap/workloads/certifications.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation lists both Windows and Linux as supported platforms for many SAP workloads on Azure, but Windows is frequently mentioned first in tables and examples. Some products (e.g., SAP BusinessObjects BI, SAP Business One on SQL Server, SAP Hybris Commerce Platform) are described with Windows-only support or Windows as the primary/initial option, with Linux equivalents listed separately or later. There are references to Windows-specific tools (e.g., SQL Server, Oracle on Windows) and no Linux command-line or configuration examples are provided.
Recommendations
- Ensure Linux platforms are listed first or alongside Windows in tables and examples to avoid implicit prioritization.
- Provide Linux-specific examples, such as shell commands or configuration steps, where applicable.
- Highlight Linux database options and tools (e.g., PostgreSQL, MySQL) if supported, not just Windows-centric ones like SQL Server.
- Clarify parity between Windows and Linux support for each SAP product, including any limitations or differences.
- Include links to Linux-focused documentation or guides for SAP on Azure.
Sap
Implement SAP BW NLS with SAP IQ on Azure | Microsoft Docs
...s/blob/main/articles/sap/workloads/dbms-guide-sapiq.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as Windows Server Failover Cluster and UNC path examples) are described in detail, often before or with more depth than their Linux equivalents. Windows deployment and high-availability solutions are discussed first, and examples (e.g., backup UNC path) are provided only for Windows. Linux equivalents (e.g., Pacemaker for HA, NFS for storage) are mentioned, but with less detail and no concrete command or configuration examples. There is also a lack of Linux-specific examples for backup paths and automation scripts.
Recommendations
- Provide Linux-specific examples for backup and restore operations, such as NFS mount paths and shell commands.
- Ensure parity in detail and step-by-step instructions for Linux high-availability setups (e.g., Pacemaker configuration), matching the depth given to Windows/WSFC.
- Include Linux automation examples for backup scheduling (e.g., using cron or systemd timers), similar to any Windows automation guidance.
- Present Windows and Linux options side-by-side in all relevant sections, rather than discussing Windows first.
- Add troubleshooting and best practices sections for Linux deployments, matching those provided for Windows.
Sap
SAP BusinessObjects BI Platform Deployment on Azure | Microsoft Docs
...cles/sap/workloads/businessobjects-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows and Azure SQL Database are frequently mentioned first or exclusively, especially in architecture, sizing, and database sections. Examples and recommendations for Windows deployments are more detailed, while Linux equivalents are referenced but not elaborated. Some Azure services (e.g., Azure SQL Database) are noted as only supported for Windows, and Linux-specific deployment guidance is deferred to a separate document, with few direct examples or instructions present in the main text.
Recommendations
- Provide side-by-side examples for both Windows and Linux deployments throughout the guide, not just in separate documents.
- Ensure Linux tools, patterns, and configuration steps are described with equal detail and prominence as Windows equivalents.
- Explicitly mention Linux compatibility and best practices in all relevant sections (e.g., storage, networking, high availability).
- Clarify any Azure service limitations for Linux and suggest alternative approaches or workarounds.
- Include direct links and summaries from the Linux deployment guide within this main document to improve parity and visibility.
Sap
Considerations for Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
...blob/main/articles/sap/workloads/dbms-guide-general.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays a moderate Windows bias: Windows-specific tools (Storage Spaces) are mentioned before Linux equivalents (MDADM/LVM), and Windows examples or terminology (e.g., drive D, Windows Server versions) are presented first or exclusively in some sections. Conversion instructions for managed disks list Windows before Linux. Some referenced guides and examples focus on Windows (e.g., SQL Server on Windows), and PowerShell/Windows-centric patterns are more prominent. Linux equivalents are present but sometimes secondary or less detailed.
Recommendations
- Ensure Linux tools and patterns (e.g., MDADM, LVM) are described with equal detail and prominence as Windows tools (Storage Spaces).
- Present Linux and Windows examples side-by-side, alternating which comes first in each section.
- Include explicit Linux command-line examples (e.g., shell commands for disk management, network configuration) where Windows PowerShell or GUI steps are shown.
- Reference Linux-specific guides and best practices with the same frequency and visibility as Windows ones.
- Avoid Windows-centric terminology (e.g., 'drive D') without immediately providing the Linux equivalent ('/mnt/resource').
- Where possible, provide parity in troubleshooting, migration, and configuration steps for both platforms.
Sap
SAP MaxDB, liveCache, and Content Server deployment on Azure VMs | Microsoft Docs
...s/blob/main/articles/sap/workloads/dbms-guide-maxdb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: all deployment, configuration, and backup examples are exclusively for Windows, with no mention of Linux equivalents or support. Windows-specific tools and features (such as Windows Storage Pools/Spaces and VSS integration) are referenced without Linux alternatives. The document does not provide guidance for deploying SAP MaxDB, liveCache, or Content Server on Linux VMs, nor does it mention supported Linux distributions or best practices for Linux environments.
Recommendations
- Add equivalent sections for SAP MaxDB, liveCache, and Content Server deployments on supported Linux distributions (e.g., SUSE, Red Hat).
- Provide Linux-specific configuration guidelines for storage, backup, and restore, including recommended tools (e.g., LVM, mdadm, native Linux backup utilities).
- List supported Linux OS versions and Azure VM types for SAP workloads, referencing SAP PAM and relevant SAP Notes.
- Include examples and diagrams for Linux disk/volume management and backup strategies.
- Mention Linux-specific considerations for Azure VM deployment, monitoring, and availability.
- If certain features (e.g., VSS integration) are not available on Linux, clarify alternatives or limitations.
Sap
SAP ASE Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
.../blob/main/articles/sap/workloads/dbms-guide-sapase.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Windows Firewall
Windows Specific Guides
Summary
The documentation generally maintains parity between Windows and Linux, providing configuration tables and recommendations for both platforms. However, there are several instances of Windows bias: Windows is often mentioned first in lists and configuration tables; Windows-specific tools (Storage Spaces, NTFS, Windows Firewall) are referenced before their Linux equivalents (LVM2, XFS, Linux firewall); and installation guidance for Windows is linked explicitly, while Linux installation guidance is less direct. Additionally, some operational procedures (e.g., firewall configuration) are described only for Windows, and troubleshooting or advanced configuration links are more detailed for Windows.
Recommendations
- Alternate the order of Windows and Linux references in tables and lists to avoid implicit prioritization.
- Provide equally explicit installation guidance and links for Linux (e.g., link to SAP ASE Installation Guide for Linux).
- Include Linux firewall configuration steps alongside Windows Firewall instructions.
- Ensure that advanced configuration and troubleshooting sections reference both Windows and Linux tools and procedures with equal detail.
- Where Windows-specific features (e.g., Storage Spaces) are mentioned, ensure Linux equivalents (e.g., LVM2) are described with similar depth and examples.
- Add Linux-specific operational notes, such as SELinux/AppArmor considerations, and reference Linux system administration best practices.
Sap
SAP workload planning and deployment checklist
...ob/main/articles/sap/workloads/deployment-checklist.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several instances of Windows bias. Windows-specific examples, registry settings, and tools (such as LogMan, NotMyFault, and references to Windows failover clustering) are mentioned before or more prominently than their Linux equivalents. PowerShell is listed first among automation tools, and some configuration examples (e.g., registry keys for TCP keepalive) are only given for Windows, with Linux equivalents either missing or less detailed. Some monitoring and performance tools are Windows-centric, and certain recommendations (e.g., failover cluster tuning) are only described for Windows environments.
Recommendations
- Provide Linux equivalents for all Windows-specific configuration examples, such as TCP keepalive settings and failover cluster parameters.
- Ensure Linux tools (e.g., sysstat, sar, nmon) are mentioned alongside or before Windows tools in relevant sections.
- Include Bash, CLI, and Ansible examples equally or before PowerShell when discussing automation approaches.
- Add explicit instructions for Linux-based high availability and disaster recovery configurations, matching the detail given for Windows clusters.
- Reference Linux monitoring and troubleshooting tools (e.g., journalctl, systemd, iptables) where appropriate.
- Review all checklist items to ensure Linux parity and avoid Windows-first ordering.
- Where a tool or method is Windows-only, clearly state the Linux alternative or note any gaps.
Sap
Disaster Recovery overview and infrastructure guidelines for SAP workload
...cles/sap/workloads/disaster-recovery-overview-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits several signs of Windows bias. Windows-specific tools (such as RoboCopy) are mentioned for SMB storage replication, and PowerShell is referenced as the only supported method for configuring disaster recovery for certain VM deployments. The document provides explicit guidance for SAP on Windows (e.g., Azure Shared Disk scenarios) but does not offer equivalent Linux-specific examples or alternatives. Linux-native tools (such as rsync) are mentioned, but only after Windows tools or in less detail, and there are no step-by-step Linux command examples. Overall, the document prioritizes Windows approaches and omits Linux parity in several areas.
Recommendations
- Provide equivalent Linux examples and step-by-step instructions (e.g., using rsync for NFS/SMB replication, bash scripting for automation).
- Mention Linux-native tools and approaches before or alongside Windows tools, not after.
- Where PowerShell is required, clarify if Azure CLI or other cross-platform tools can be used, and provide guidance for Linux administrators.
- Add explicit references and examples for SAP workloads running on Linux, especially in sections currently focused on Windows scenarios.
- Ensure all DR strategies and tooling recommendations are applicable to both Windows and Linux environments, or clearly state platform limitations.
Sap
Azure Virtual Machines deployment for SAP NetWeaver | Microsoft Docs
...s/blob/main/articles/sap/workloads/deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates several types of Windows bias. Windows tools and patterns (such as PowerShell and sysprep) are frequently mentioned first or exclusively, sometimes with more detailed steps than their Linux equivalents. Windows-specific requirements (such as needing a Windows computer for PowerShell) are stated before Linux alternatives. Some examples and instructions (e.g., domain join, VM agent installation, proxy configuration) provide more detail for Windows, while Linux instructions are more concise or referenced externally. In some cases, Linux examples are missing or less emphasized compared to Windows.
Recommendations
- Ensure Linux instructions are as detailed and explicit as Windows instructions, including step-by-step guides for common tasks (e.g., joining a Linux VM to an LDAP/AD domain, agent installation, troubleshooting).
- Present Linux and Windows options in parallel, rather than listing Windows first or exclusively. For example, mention Azure CLI and Linux tools before or alongside PowerShell.
- Where Windows-only features are described (e.g., domain join), clarify Linux alternatives or explicitly state limitations.
- Provide Linux command-line examples for all major deployment and configuration scenarios, not just references to external guides.
- Review prerequisites to avoid implying that a Windows computer is required for all management tasks; clarify that Linux workstations can be used with Azure CLI and SSH.
- Balance the use of Windows and Linux logos and visual cues throughout the documentation.
- Add troubleshooting and best practices sections specific to Linux deployments, matching the depth provided for Windows.
Sap
Disaster Recovery recommendation for SAP workload
.../articles/sap/workloads/disaster-recovery-sap-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides recommendations for disaster recovery of SAP workloads on Azure, with both Linux and Windows sections. However, there is evidence of Windows bias: Windows tools and patterns (e.g., Robocopy, Windows Server Failover Cluster) are mentioned explicitly and with direct links, while Linux equivalents (e.g., rsync, Pacemaker) are referenced more abstractly or as 'custom' solutions. Windows examples and tools are often listed before Linux ones, and some Linux replication methods are described less concretely. There is also a lack of detailed Linux command examples compared to Windows (e.g., no rsync command line shown, while Robocopy is linked).
Recommendations
- Provide concrete Linux examples (e.g., rsync command lines, Pacemaker configuration snippets) similar to the detail given for Windows tools.
- Ensure Linux solutions (e.g., NFS replication, Pacemaker cluster setup) are described with actionable steps and direct links to official documentation, not just blogs.
- Present Linux and Windows recommendations in parallel, giving equal prominence and detail to both, rather than listing Windows tools first or in more detail.
- Include references to Linux-native backup and restore tools and methodologies where appropriate.
- Clarify any limitations or differences for Linux workloads (e.g., Azure Backup support for NFS) with guidance on alternatives.
Sap
Exchange Online Integration for Email-Outbound from SAP NetWeaver | Microsoft Docs
...oads/exchange-online-integration-sap-email-outbound.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft 365 Admin Center and Exchange Online PowerShell for configuration steps, without mentioning or providing equivalent Linux-based tools or CLI examples. All administrative instructions and screenshots are based on Windows-centric interfaces, and there is no guidance for performing these tasks from Linux environments or with cross-platform tools. The lack of Linux-specific examples or parity in instructions may hinder SAP administrators working on Linux-based SAP servers, which are common in enterprise deployments.
Recommendations
- Provide Linux-based examples for SMTP connectivity tests (e.g., using 'nc', 'openssl', or 'telnet' from Linux shell).
- Include instructions for configuring Exchange Online settings using cross-platform tools such as Microsoft Graph API or REST endpoints, rather than only PowerShell.
- Add guidance for managing DNS and SPF records from Linux or cloud-native CLI tools.
- Reference open-source mail relay solutions (e.g., Postfix, Exim) with configuration steps for integration with Exchange Online.
- Ensure screenshots and step-by-step instructions are not exclusively tied to Windows GUIs; offer CLI alternatives where possible.
- Explicitly mention Linux compatibility and provide troubleshooting steps for common Linux-based SAP deployments.
Sap
SAP HANA infrastructure configurations and operations on Azure | Microsoft Docs
...blob/main/articles/sap/workloads/hana-vm-operations.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows tools and patterns (such as Azure PowerShell cmdlets and Windows failover cluster references) are mentioned before or alongside Linux equivalents, and some examples or instructions are Windows-centric. There is a lack of explicit Linux command-line examples (e.g., Azure CLI, SSH, Linux-specific configuration steps) in several key operational sections, and Windows terminology (Jumpbox, SOFS, PowerShell) is used without always providing Linux alternatives or parity in detail.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for VM deployment, management, and networking (e.g., show Azure CLI and SSH usage, not just PowerShell).
- Ensure Linux tools and patterns (such as systemd, Pacemaker, mdadm, LVM) are described with equal detail and prominence as Windows tools.
- When listing deployment methods, alternate the order or explicitly mention Linux-first options (e.g., 'Azure CLI, Azure portal, Azure PowerShell').
- Add explicit Linux command-line examples for common operations (e.g., assigning static IPs, configuring disks, managing VMs).
- Where Windows-specific features (SOFS, failover cluster) are referenced, ensure Linux equivalents (NFS, Pacemaker, etc.) are also described and linked.
- Review terminology to ensure cross-platform neutrality (e.g., clarify 'Jumpbox' applies to both Windows and Linux, or use 'bastion host').
Sap
Set up Pacemaker on RHEL in Azure | Microsoft Docs
...ap/workloads/high-availability-guide-rhel-pacemaker.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is generally focused on Linux (RHEL) cluster setup, but there is evidence of Windows bias. The Azure shared disk setup section provides only PowerShell examples for disk creation and attachment, with CLI and Portal methods relegated to a reference link. The use of PowerShell and references to Windows-centric Azure tools appear before Linux-native alternatives. Additionally, the services metadata includes 'virtual-machines-windows', and some links or references are Windows-focused, despite the target platform being Linux.
Recommendations
- Provide full Azure CLI examples for shared disk creation and attachment alongside PowerShell, not just as a reference link.
- Include step-by-step instructions for using the Azure Portal for disk setup, with screenshots or explicit steps, to match the detail of PowerShell examples.
- Ensure that Linux-native tooling and patterns (e.g., Azure CLI, bash scripts) are presented before or alongside Windows/PowerShell equivalents.
- Review metadata and service tags to ensure they accurately reflect the Linux focus (remove 'virtual-machines-windows' if not relevant).
- Where possible, avoid referencing Windows-specific documentation or tools unless strictly necessary for the Linux workflow.
Sap
Azure Virtual Machines HA for SAP NW on RHEL with Azure NetApp Files| Microsoft Docs
...workloads/high-availability-guide-rhel-netapp-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows evidence of Windows bias primarily in the load balancer configuration section, where PowerShell is presented as a top-level tab alongside Azure CLI and Portal, and the custom metadata includes 'devx-track-azurepowershell' before 'devx-track-azurecli'. Additionally, references to SAP kernel versions and prerequisites mention Windows before Linux. However, the technical steps and examples throughout the guide are almost exclusively Linux-focused, with commands and configuration instructions tailored to RHEL environments.
Recommendations
- Present Azure CLI examples before PowerShell in all tabbed sections, or at least in parallel, to avoid implying PowerShell primacy.
- Ensure that Linux tools and patterns are always mentioned before or alongside Windows equivalents in prerequisites and SAP Notes references.
- Remove or balance metadata tags such as 'devx-track-azurepowershell' and 'devx-track-azurecli' to reflect Linux parity.
- Where Windows-specific prerequisites or kernel versions are mentioned, provide direct Linux equivalents and clarify their relevance.
- Audit all cross-referenced guides and ensure Linux examples are as complete and visible as any Windows or PowerShell instructions.
Sap
Azure Virtual Machines HA for SAP NW on RHEL | Microsoft Docs
...articles/sap/workloads/high-availability-guide-rhel.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page is focused on SAP NetWeaver high availability on Red Hat Enterprise Linux (RHEL) and provides extensive Linux-specific guidance and examples. However, there are subtle signs of Windows bias: Windows prerequisites and kernel versions are mentioned before Linux in the prerequisites section, and PowerShell is presented as a first-class option for Azure Load Balancer configuration, with tabs for Azure portal, Azure CLI, and PowerShell (but no Linux-specific shell example). Additionally, references to Windows tools and patterns (such as kernel version requirements and PowerShell) appear alongside or before Linux equivalents, even though the main content is Linux-centric.
Recommendations
- In the prerequisites section, list Linux kernel and requirements before Windows, or separate them clearly to avoid implying Windows primacy.
- For Azure Load Balancer configuration, provide Bash or Linux shell script examples alongside PowerShell, or clarify that Azure CLI commands are cross-platform.
- If PowerShell is mentioned, explicitly note that Azure CLI is recommended for Linux users and provide parity in example depth.
- Avoid referencing Windows-specific tools or patterns unless directly relevant; if mentioned, always provide the Linux equivalent first.
- Review all example tabs and ensure Linux-native tools (e.g., Bash, Azure CLI) are presented before or alongside Windows tools.
Sap
Azure VMs high availability for SAP NetWeaver on SLES multi-SID guide | Microsoft Docs
...ap/workloads/high-availability-guide-suse-multi-sid.md
High Priority
View Details →
Detected Bias Types
Windows Reference
Windows Notes
Windows Tools
Summary
The documentation is focused on SAP NetWeaver high availability on SUSE Linux in Azure and provides comprehensive Linux-specific instructions and examples. However, there are minor references to Windows, such as mentioning required SAP kernel versions for Windows and Linux, and listing Windows in the context of supported OS combinations. There are no Windows/Powershell examples, nor are Windows tools or patterns prioritized over Linux equivalents. The documentation is strongly Linux-centric, with all examples, commands, and tooling based on SUSE Linux and its ecosystem.
Recommendations
- Remove or clarify Windows references in SAP Notes if not relevant to the Linux scenario.
- Ensure that any mention of Windows is contextualized as background information and does not distract from the Linux focus.
- If Windows-specific guidance is needed, provide it in a separate section or document to maintain clarity for Linux users.
- Continue to provide Linux-first examples and tooling, as done throughout the document.
Sap
Set up Pacemaker on SUSE Linux Enterprise Server (SLES) in Azure | Microsoft Docs
...ap/workloads/high-availability-guide-suse-pacemaker.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
Although the documentation is focused on SUSE Linux Enterprise Server (SLES) and Pacemaker, there are several instances of Windows bias. The most notable is the use of PowerShell for Azure shared disk creation and attachment, with no equivalent Azure CLI or Linux-native example provided. The services metadata includes 'virtual-machines-windows', and links to Windows maintenance documentation are given alongside Linux links. Windows tools and patterns (PowerShell, Windows VM references) are mentioned before or instead of Linux alternatives in some places.
Recommendations
- Provide Azure CLI examples for disk creation and attachment alongside PowerShell, as CLI is cross-platform and more common for Linux users.
- Where PowerShell is referenced, explicitly note that Azure CLI or portal can be used and link to relevant Linux/CLI documentation.
- Review service metadata and links to ensure Linux-first or Linux-only focus where appropriate, especially in a Linux-specific guide.
- If referencing Windows documentation (e.g., maintenance), ensure Linux documentation is referenced first or exclusively, unless a direct comparison is needed.
- Consider removing or de-emphasizing Windows-specific tools and patterns unless they are required for the Linux workflow.
Sap
SAP workload configurations with Azure Availability Zones | Microsoft Docs
...main/articles/sap/workloads/high-availability-zones.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and patterns (e.g., Windows Server Failover Clustering, PowerShell scripts) are mentioned before or more prominently than their Linux equivalents. Example links and next steps focus on Windows failover clustering, with Linux alternatives referenced but not equally highlighted. The PowerShell-based latency test is described as the main automation method, with no mention of a Linux shell equivalent. Linux high availability solutions (e.g., Pacemaker) are mentioned but not given equal practical guidance or example scripts.
Recommendations
- Provide Linux shell (bash) equivalents for all PowerShell automation scripts, especially for latency testing.
- Balance example links and next steps to include both Windows and Linux high availability guides.
- When describing failover cluster solutions, mention Linux Pacemaker and its configuration steps alongside Windows Server Failover Clustering.
- Ensure that Linux tools and patterns (e.g., crmsh, pcs for Pacemaker) are referenced with equal prominence and detail.
- Where possible, offer side-by-side configuration examples for both Windows and Linux environments.
- Clarify that all major SAP deployment patterns are supported on both Windows and Linux, and link to relevant documentation for both.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several sections, Windows examples, tools, and patterns are presented before or more prominently than their Linux equivalents. For instance, SQL Server deployment and troubleshooting are covered in detail, with Windows-specific instructions and tools (such as Microsoft ODBC Driver, Visual C++ Redistributable, and NT AUTHORITY\SYSTEM permissions). Powershell and Windows paths are used in examples, sometimes without corresponding Linux alternatives. Some troubleshooting steps and error messages are Windows-centric, and Linux-specific guidance is less detailed or omitted in certain areas.
Recommendations
- Ensure that Linux examples are provided alongside Windows examples in all relevant sections, especially for deployment, configuration, and troubleshooting.
- Present Linux and Windows instructions in parallel, or alternate which platform is shown first to avoid implicit prioritization.
- Include Linux equivalents for all Windows-specific tools and patterns (e.g., clarify which ODBC drivers or libraries are needed for Linux, and provide installation steps).
- Expand troubleshooting guidance to cover common Linux-specific issues, permissions, and error messages.
- Review all code samples and ensure both Linux and Windows paths, commands, and environment variables are shown where applicable.
- Where screenshots or diagrams are Windows-specific, provide Linux versions or clarify platform differences.
Sap
Get started with SAP and Microsoft integration scenarios
...main/articles/sap/workloads/integration-get-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by consistently prioritizing Microsoft and Windows-centric integration scenarios, tools, and examples. Windows-based services (such as Microsoft Entra ID, Defender, Sentinel, Power Platform, Teams, Office, Universal Print) are presented as the default or only integration options, with little to no mention of Linux-native equivalents or cross-platform alternatives. Where endpoint protection is discussed, Windows and Linux are both referenced, but Windows examples and tools are often listed first or exclusively. There is a lack of Linux-specific integration patterns, troubleshooting, or examples, and no mention of open-source or non-Microsoft alternatives for key scenarios.
Recommendations
- Include Linux-specific integration examples and troubleshooting steps for SAP workloads, especially for endpoint protection, authentication, and automation.
- Present cross-platform tools and patterns (e.g., open-source connectors, Linux-native automation frameworks) alongside or before Windows/Microsoft tools.
- Add parity for Linux in sections discussing Microsoft Defender, Sentinel, and other security tools, with explicit guidance for Linux SAP hosts.
- Highlight open standards and non-Microsoft alternatives for integration (e.g., SSO via SAML/LDAP, open-source RPA tools, Linux printing solutions).
- Ensure that examples and tutorials are available for both Windows and Linux environments, and clearly indicate platform-specific requirements or limitations.
- Balance the documentation by referencing SAP integration scenarios on other clouds or on-premises Linux deployments where relevant.
Sap
Azure Premium Files NFS and SMB for SAP
...es/sap/workloads/planning-guide-storage-azure-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation covers both NFS (Linux) and SMB (Windows) usage for Azure Premium Files with SAP, but there is a noticeable Windows bias. SMB/Windows-specific tools and patterns (e.g., SWPM, SAPInst, Active Directory integration, Azure portal permissions) are described in detail, while Linux/NFS examples are limited to general recommendations and links. There are no explicit Linux command-line examples, and Windows/SMB guidance is more comprehensive and appears before equivalent Linux/NFS details.
Recommendations
- Add explicit Linux command-line examples for mounting NFS shares, including sample mount commands and troubleshooting steps.
- Provide parity in troubleshooting guidance for Linux/NFS scenarios, similar to the detailed steps given for Windows/SMB.
- Include Linux-specific permission and security configuration steps for NFS shares, analogous to the Active Directory and Azure portal instructions for SMB.
- Balance the order and depth of coverage so that Linux/NFS and Windows/SMB are treated equally, with parallel sections and examples.
- Reference Linux tools (e.g., nfs-utils, systemd mount units) and best practices for SAP workloads on NFS.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally maintains cross-platform coverage but exhibits subtle Windows bias. Windows terminology (e.g., VHD, SMB, Storage Spaces) is used as the default, with Linux equivalents (e.g., LVM, NFS) often mentioned second or in parentheses. Some examples and recommendations (such as striping with Windows Storage Spaces) are given for Windows first, with Linux alternatives referenced later. There is a lack of explicit Linux command-line examples (e.g., LVM setup), and some sections (e.g., high availability guides) link to Windows documentation before Linux. The documentation refers to Windows-specific tools and patterns (e.g., SMB, Storage Spaces) more frequently and in more detail than their Linux counterparts.
Recommendations
- Provide explicit Linux examples and command-line instructions (e.g., LVM striping, NFS mounting) alongside Windows/Powershell examples.
- Ensure Linux tools and patterns (e.g., LVM, NFS) are described with equal detail and prominence as Windows tools (e.g., Storage Spaces, SMB).
- When listing supported scenarios or guides, alternate the order between Windows and Linux, or present them together, to avoid implicit prioritization.
- Include links to Linux-specific documentation and troubleshooting guides as prominently as Windows equivalents.
- Clarify platform-specific recommendations (e.g., for striping, high availability) with step-by-step instructions for both Windows and Linux.