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 51-75 of 639 flagged pages
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 exclusively discusses deployment and configuration of SAP MaxDB, liveCache, and Content Server on Windows in Azure VMs. All examples, recommendations, and tooling references are for Microsoft Windows (e.g., Windows Storage Pools, Windows Storage Spaces, VSS integration, IIS), with no mention of Linux equivalents or guidance for Linux-based deployments. There are no Linux-specific instructions, examples, or best practices provided, despite SAP MaxDB and Content Server being supported on Linux in Azure. This results in a strong Windows bias, making the documentation less useful for administrators deploying on Linux.
Recommendations
- Add equivalent sections for SAP MaxDB, liveCache, and Content Server deployments on Linux, including supported distributions, VM types, and configuration guidelines.
- Provide Linux-specific storage configuration instructions, referencing tools like LVM, mdadm (RAID), and Linux disk caching options.
- Include backup and restore guidance for Linux, referencing native MaxDB tools and common Linux backup utilities.
- Discuss Linux alternatives to Windows-specific technologies (e.g., use Apache/Nginx instead of IIS, use Linux-native snapshot/backup solutions instead of VSS/Azure Backup with Windows integration).
- Ensure that examples and recommendations are provided for both Windows and Linux, or clearly indicate when a feature is Windows-only.
- Add links to relevant Linux documentation and SAP Notes for Linux deployments.
Create Pull Request
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
Windows Heavy Examples
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (such as Windows Server Failover Cluster and SMB/UNC paths) are described in detail, with explicit examples and links. Windows deployment and high-availability options are presented first, and the backup example uses a Windows UNC path without a Linux equivalent. Linux options are covered, but with less detail and fewer practical examples, especially for backup/restore scenarios and file system usage.
Recommendations
- Provide Linux-specific backup/restore examples, such as using NFS paths or Linux file system conventions.
- Ensure parity in detail between Windows and Linux sections, including step-by-step guides and practical configuration examples (e.g., Pacemaker cluster setup commands).
- Mention Linux equivalents for Windows tools (e.g., Pacemaker for clustering, NFS for network storage) wherever Windows tools are referenced.
- Present Windows and Linux options in parallel or side-by-side tables, rather than listing Windows first.
- Include troubleshooting tips and automation scripts for Linux environments, similar to those provided for Windows.
Sap
SQL Server Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
...ob/main/articles/sap/workloads/dbms-guide-sqlserver.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is strongly biased toward Windows, with explicit statements that SAP does not support SQL Server on Linux for SAP workloads. All configuration, deployment, and operational examples are Windows-centric, referencing Windows Server, NTFS, Windows command line tools, and Windows-specific Azure VM images. There are no Linux equivalents or examples, and Linux is only mentioned to clarify its lack of support. Windows tools and patterns (e.g., NTFS, D:\ drive, Windows command prompt, Windows Server versions) are referenced exclusively and repeatedly.
Recommendations
- Clearly state at the top that Linux is not supported for SAP workloads with SQL Server, and link to any official SAP or Microsoft documentation confirming this.
- If Linux support becomes available in the future, provide equivalent Linux examples, such as using ext4/xfs filesystems, Linux VM images, and Linux command line tools.
- Where possible, mention alternative approaches or limitations for Linux users, even if only to clarify that the guidance does not apply.
- Consider a separate section or page for Linux deployments (if/when supported), to ensure parity and avoid confusion.
- Review all command-line and configuration instructions to ensure they are not unnecessarily Windows-specific if cross-platform support is added.
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 page exhibits several Windows biases: Windows tools (PowerShell, sysprep) and patterns are mentioned first or exclusively in multiple sections, especially in prerequisites and deployment steps. Windows-specific instructions (such as joining a domain, proxy configuration, and VM agent installation) are more detailed and appear before Linux equivalents. PowerShell is referenced as a primary automation tool, while Linux CLI is mentioned as an alternative. Some examples and links (e.g., VM creation via PowerShell) are Windows-centric, and Linux instructions are sometimes less detailed or presented after Windows steps.
Recommendations
- Present Linux and Windows instructions in parallel, with equal detail and prominence.
- Include Linux CLI and automation examples (e.g., Bash, Azure CLI) wherever PowerShell is referenced.
- Ensure Linux prerequisites and management options are described first or alongside Windows, not as secondary.
- Expand Linux-specific troubleshooting and configuration steps to match the depth of Windows sections.
- Add links to Linux-focused quickstarts and tutorials in all relevant sections.
- Where Windows-only features are described (e.g., domain join), clarify Linux alternatives or explicitly state limitations.
- Review and balance the order of presentation so Linux is not consistently after Windows.
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 a moderate Windows bias. Windows-specific tools, registry settings, and references (e.g., LogMan, NotMyFault, Windows failover cluster tuning, registry tweaks) are mentioned before or in more detail than their Linux equivalents. Some examples and recommendations are Windows-centric or lack Linux parity (e.g., registry settings for timeouts, Windows LogMan for performance data, NotMyFault for failover simulation). While Linux is referenced (e.g., LVM, sysstat, nmon), Windows approaches are often presented first or exclusively, and some Linux alternatives are only briefly mentioned or omitted.
Recommendations
- Ensure every Windows-specific example or tool (e.g., LogMan, NotMyFault, registry settings) is paired with a Linux equivalent (e.g., sysstat, stress-ng, /etc/sysctl.conf or sysctl for TCP keepalive).
- Present Linux and Windows approaches side-by-side, or alternate which platform is presented first in examples and recommendations.
- Expand Linux-specific instructions for failover simulation, performance monitoring, and timeout/network tuning to match the detail given for Windows.
- Where PowerShell or Windows registry is referenced, provide Bash/CLI or Linux configuration file examples.
- Review all checklist items and ensure Linux-specific validation steps are as detailed as Windows ones (e.g., disk striping, failover cluster settings, performance data collection).
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
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific tools (e.g., RoboCopy) are mentioned as recommended solutions for SMB file replication, while Linux alternatives (e.g., rsync) are only suggested for NFS scenarios. PowerShell is referenced as the sole method for configuring disaster recovery in certain VM scale set scenarios, with no mention of CLI or Linux-native approaches. The section on Azure Shared Disk DR specifically calls out Windows scenarios, and there are no explicit Linux or Bash examples provided for common administrative or recovery tasks. Overall, Windows tools and patterns are mentioned first or exclusively, and Linux parity is lacking in example coverage and tool recommendations.
Recommendations
- Provide Linux/Bash equivalents for all Windows/Powershell examples, such as using az CLI or Bash scripts for DR configuration.
- Mention Linux-native tools (e.g., rsync, scp) alongside Windows tools like RoboCopy for SMB file replication, and clarify when each is appropriate.
- Include explicit guidance and examples for SAP workloads running on Linux, especially for Azure Site Recovery and storage replication scenarios.
- Where PowerShell is required, note any Linux-compatible alternatives or workarounds, or clarify platform limitations.
- Ensure that documentation sections do not assume Windows as the default platform, and provide parity in instructions and references for both OS types.
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 both Linux and Windows guidance for SAP disaster recovery, but there is a noticeable Windows bias. Windows terminology (Active Directory, DNS, Windows Server Failover Cluster, SMB, Robocopy) is introduced first and more frequently, with Windows-specific tools and patterns (WSFC, Robocopy) mentioned explicitly. Linux equivalents (Pacemaker, rsync) are referenced, but often after Windows tools or with less detail. Some examples and recommendations (e.g., backup support matrices, storage replication) prioritize Windows technologies or omit Linux-specific guidance.
Recommendations
- Present Linux and Windows guidance in parallel, giving equal prominence to both platforms.
- Include Linux-specific tools and commands (e.g., rsync, NFS, Pacemaker) with the same level of detail as Windows tools (e.g., Robocopy, WSFC).
- Add explicit Linux examples for backup, restore, and storage replication, including command-line snippets where appropriate.
- Avoid introducing Windows terminology (Active Directory, DNS, SMB, Robocopy) before Linux equivalents; use neutral language or present both together.
- Expand on Linux high availability and DR patterns, such as fencing mechanisms, cluster reconfiguration, and storage replication, with step-by-step guidance.
- Ensure parity in support matrices, clearly stating limitations and alternatives for both Linux and Windows workloads.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Microsoft 365 Admin Center, Exchange Admin Center, and PowerShell for administrative actions, without mentioning or providing Linux-based alternatives (such as using Linux mail relay servers, Postfix/Sendmail configuration, or command-line tools). All screenshots and step-by-step instructions assume a Windows-centric workflow, and there are no examples or guidance for Linux administrators or those running SAP on Linux hosts.
Recommendations
- Include examples and instructions for configuring SMTP relay using common Linux mail servers (e.g., Postfix, Sendmail, Exim) as intermediaries to Exchange Online.
- Provide Linux command-line equivalents for network connectivity checks (e.g., using 'nc' or 'telnet' on Linux) instead of only referencing Windows tools.
- Add guidance for managing Exchange Online settings via cross-platform tools (such as Microsoft Graph API or REST endpoints) rather than only PowerShell or GUI.
- Clarify that the SAP application server may be running on Linux and offer OS-agnostic steps for SAP SCOT configuration.
- Add troubleshooting steps and examples for Linux environments, including firewall and TLS configuration specifics.
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 First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (such as Azure PowerShell and Windows Failover Cluster) are mentioned before or alongside Linux equivalents, and Windows-specific scenarios are described in detail. While Linux is referenced (especially SUSE and Red Hat), examples and operational instructions often default to Windows-first or PowerShell-heavy approaches, with Linux-specific guidance sometimes relegated to linked documents or notes. There are few explicit Linux command-line examples, and some operational steps (e.g., VM deployment, network configuration) mention PowerShell before Azure CLI or Linux-native methods.
Recommendations
- Ensure Linux CLI (bash, Azure CLI) examples are provided alongside or before PowerShell examples for all operational steps.
- Where Windows-specific tools or patterns (e.g., Windows Failover Cluster, SOFS) are described, provide equal detail for Linux equivalents (e.g., Pacemaker, SBD).
- Add explicit Linux command-line examples for common tasks such as VM deployment, storage configuration, and network setup.
- Review all sections for Windows-first ordering and alternate with Linux-first or neutral ordering.
- Clarify when instructions are OS-specific, and avoid assuming Windows as the default unless justified by usage statistics.
- Expand troubleshooting and backup/restore sections to include Linux-native tools and workflows.
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 primarily focused on configuring Pacemaker on RHEL in Azure and is generally Linux-centric. However, there are signs of Windows bias: the only example for creating and attaching Azure shared disks uses PowerShell, a Windows-native tool, with no equivalent Azure CLI or Bash example provided. Additionally, references to resource deployment mention the Azure portal and CLI only as alternatives, and the PowerShell example is presented first and in detail. The services metadata includes 'virtual-machines-windows', and some links and references (such as managed identities) point to Windows VM pivots or documentation. There are no Linux-first or Linux-only deployment examples for Azure resources, and the use of PowerShell may be unfamiliar or inaccessible to Linux administrators.
Recommendations
- Provide Azure CLI and Bash examples for all resource deployment steps, especially for creating and attaching shared disks, to ensure Linux administrators can follow without needing PowerShell.
- Present Azure CLI/Bash examples before or alongside PowerShell examples, making Linux-native tooling the default for Linux-focused documentation.
- Review and update metadata and links to ensure Linux pivots are primary when the target audience is Linux administrators.
- Explicitly state when PowerShell is required and offer guidance for Linux users on installing and using PowerShell, or preferably avoid requiring it.
- Ensure all referenced tools and procedures are accessible and familiar to Linux users, minimizing reliance on Windows-centric tooling.
Sap
Azure VMs high availability for SAP NW on SLES with NFS on Azure Files| Microsoft Docs
...kloads/high-availability-guide-suse-nfs-azure-files.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
While the documentation is focused on deploying SAP NetWeaver on SUSE Linux Enterprise Server (SLES) and provides extensive Linux-specific instructions and examples, there is evidence of Windows bias in several areas. The services metadata includes 'virtual-machines-windows', and in sections describing Azure Load Balancer configuration, PowerShell is listed as a primary method alongside Azure CLI and portal, even though the scenario is Linux-centric. Additionally, references to SAP kernel versions and prerequisites mention Windows before Linux, and some linked resources and terminology (such as 'Azure Enhanced Monitoring Extension for SAP') are more commonly associated with Windows environments. The inclusion and ordering of Windows tools and patterns, even when not directly relevant to the Linux deployment, may cause confusion or suggest Windows as the default platform.
Recommendations
- Remove or de-emphasize references to Windows-specific services and tools in metadata and prerequisites when the guide is Linux-focused.
- List Linux tools and examples before Windows equivalents in all sections, especially in prerequisites and configuration steps.
- Provide Linux-centric instructions as the default, with Windows alternatives clearly marked as optional or for other scenarios.
- Ensure all example commands and scripts use Linux syntax and utilities, and avoid unnecessary inclusion of PowerShell unless explicitly needed for cross-platform management.
- Clarify any references to Windows-specific extensions or features, and provide equivalent Linux guidance where possible.
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
Windows First
Powershell Heavy
Summary
While the documentation is focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, there is evidence of Windows bias. Windows tools and terminology (e.g., 'virtual-machines-windows' in services, references to Windows maintenance docs) are present throughout. The only explicit example for creating and attaching Azure shared disks uses PowerShell, with Azure CLI and Portal mentioned only as alternatives but not shown. Windows maintenance documentation is referenced before Linux in some places. There are no Linux-native Azure CLI examples for disk creation/attachment, and Azure resource management is described primarily in terms of Windows-centric tools.
Recommendations
- Provide full Azure CLI examples for creating and attaching Azure shared disks, not just PowerShell.
- Reference Linux maintenance documentation before or alongside Windows documentation when discussing maintenance.
- Remove unnecessary references to Windows-specific services and tools unless directly relevant to the Linux workflow.
- Ensure parity in example scripts and instructions for both Linux and Windows users, especially for Azure resource management tasks.
- Clarify when PowerShell is required and offer Linux-native alternatives where possible (e.g., Bash, Azure CLI).
Sap
Azure VMs high availability for SAP NetWeaver on SLES for SAP Applications with simple mount and NFS| Microsoft Docs
...loads/high-availability-guide-suse-nfs-simple-mount.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page is focused on deploying SAP NetWeaver on SUSE Linux Enterprise Server (SLES) for SAP Applications, but there are subtle signs of Windows bias. The service metadata includes 'virtual-machines-windows', and example tabs for configuring Azure load balancer are presented in the order: Azure portal, Azure CLI, then PowerShell, with PowerShell included as a first-class option. References to SAP kernel versions and supported OSs mention Windows before Linux. Azure-specific tooling and terminology (e.g., waagent, Azure portal, Azure CLI, PowerShell) are used throughout, but Linux-native alternatives (such as cloud-init or native Linux VM provisioning tools) are not discussed. There is no explicit mention of Linux-only tools or patterns outside of SUSE and Pacemaker, and the documentation does not provide parity for Linux-native automation or scripting approaches.
Recommendations
- Remove or de-emphasize 'virtual-machines-windows' in service metadata for Linux-focused documentation.
- Present Linux-native tools and patterns (e.g., cloud-init, Ansible, shell scripts) alongside or before Azure CLI and PowerShell examples.
- If PowerShell is included, ensure Bash or Linux shell equivalents are always present and shown first.
- Reference Linux kernel and OS support before Windows in lists or tables.
- Where Azure portal or CLI steps are given, provide equivalent steps using Linux-native automation (e.g., Terraform, Ansible, cloud-init).
- Clarify that waagent is the Azure Linux agent and mention alternatives or additional Linux configuration tools if relevant.
- Expand troubleshooting and operational guidance to include Linux-native monitoring and management tools.
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 and Microsoft ecosystem bias. Integration scenarios and examples are almost exclusively focused on Microsoft products and services (e.g., Azure, Microsoft 365, Power Platform, Teams, Defender, Sentinel, Universal Print, Entra ID). Windows-specific tools and patterns are mentioned first and often exclusively, with little to no mention of Linux equivalents or cross-platform alternatives. Where security software is discussed, Windows Defender and related Microsoft tools are foregrounded, and Linux coverage is minimal or secondary. There are no explicit Linux/Powershell code examples, but the overall framing and resource selection prioritize Windows and Microsoft-centric solutions, leaving Linux parity and open-source alternatives underrepresented.
Recommendations
- Include Linux-specific integration examples and documentation links for SAP workloads, such as using Linux-native tools for authentication, security, and automation.
- Provide parity in security guidance by detailing how to configure SAP security and monitoring with open-source or Linux-native solutions (e.g., fail2ban, auditd, iptables, SELinux, Linux antivirus options).
- Add examples of SAP integration with non-Microsoft cloud services or open-source platforms to broaden applicability.
- When referencing endpoint protection, offer step-by-step guides for both Windows and Linux, and highlight differences or considerations for each.
- Ensure that developer tooling and DevOps sections include Linux-based CI/CD pipelines and automation tools (e.g., Jenkins, GitLab CI, Ansible) alongside Azure DevOps.
- Explicitly mention and link to SAP notes and best practices for Linux deployments, not just Windows.
- Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows/Microsoft-first.
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 provides general guidance for both NFS (Linux) and SMB (Windows) but demonstrates subtle 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 sections lack comparable operational examples or step-by-step instructions. Windows/SMB guidance is more explicit and actionable, whereas Linux/NFS guidance is higher-level and less practical.
Recommendations
- Add concrete Linux/NFS operational examples, such as mount commands, troubleshooting steps, and permission management.
- Provide parity in step-by-step instructions for NFS shares, similar to the detailed SMB/Windows setup and integration guidance.
- Include references to Linux tools and patterns (e.g., nfs-utils, systemd mount units, SELinux considerations) where relevant.
- Ensure troubleshooting and configuration sections for NFS/Linux are as detailed and actionable as those for SMB/Windows.
- Balance the order and depth of coverage between Windows/SMB and Linux/NFS sections to avoid implicit prioritization.
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 exhibits a moderate Windows bias. Windows-specific tools and procedures (e.g., PowerShell scripts for latency testing, Windows Server Failover Clustering) are mentioned first or exclusively in several places. While Linux is referenced (e.g., SUSE Pacemaker, Red Hat guides), Windows examples and tools are often given priority, and some automation examples (like the latency test) are only provided for PowerShell, with no equivalent Linux shell script. The 'Next steps' section lists only Windows clustering guides, omitting Linux equivalents.
Recommendations
- Provide equivalent Linux shell script examples for key automation tasks, such as network latency measurement, alongside PowerShell scripts.
- Ensure that Linux high availability solutions (e.g., Pacemaker, Corosync) are described with equal detail and prominence as Windows Server Failover Clustering.
- In 'Next steps', include links to Linux clustering guides (e.g., SUSE Pacemaker, Red Hat HA) to match the Windows resources.
- When referencing tools or procedures, present both Windows and Linux options together, or alternate which is mentioned first.
- Where possible, offer cross-platform guidance for Azure-specific features (e.g., load balancer setup, disk configuration) to avoid implicit prioritization of Windows workflows.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits several signs of Windows bias. In many sections, Windows-specific instructions, tools, and examples (such as using the Azure portal, referencing Windows file paths, and requiring Microsoft ODBC drivers) are presented either exclusively or before their Linux equivalents. Some deployment and troubleshooting steps focus on Windows environments (e.g., SQL Server, NT AUTHORITY\SYSTEM, C:\ paths) with limited or no Linux alternatives. In certain cases, Linux instructions are present but less detailed or appear after Windows instructions, and some troubleshooting steps only reference Windows-specific errors.
Recommendations
- Ensure that Linux and Windows examples are presented in parallel, with equal detail and prominence.
- Where Windows-specific tools or patterns are referenced (e.g., ODBC driver, Visual C++ Redistributable), provide Linux equivalents or clarify when they are not needed.
- Add Linux-specific troubleshooting steps and error messages where only Windows errors are currently documented.
- Avoid presenting Windows instructions first by default; alternate or group by platform.
- Expand Linux deployment examples, especially for database and application server scenarios, to match the depth of Windows coverage.
- Clearly indicate platform-specific requirements and steps, and avoid assuming Windows as the default environment.
Sap
Plan and implement an SAP deployment on Azure
...ocs/blob/main/articles/sap/workloads/planning-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page, while targeting SAP on Azure with a Linux focus (ms.tgt_pltfrm: vm-linux), exhibits several Windows biases. Windows tools and patterns (e.g., Windows Server Active Directory, RDP, SMB, Windows failover clustering, PowerShell scripts) are mentioned frequently, sometimes before or in parallel with Linux equivalents. Examples and references to Windows-specific technologies (Active Directory, RDP, SMB, Windows clustering) are given more prominence or detail than their Linux counterparts (e.g., SSH, Pacemaker, NFS). PowerShell is referenced as a migration tool, but equivalent Linux CLI or scripting examples are missing. Some sections (e.g., security, networking, high availability) provide more explicit guidance for Windows than Linux, and Linux-specific examples or best practices are less detailed or omitted.
Recommendations
- Ensure that Linux tools and patterns (e.g., SSH, Linux-based identity management, Pacemaker, NFS) are mentioned first or at least equally with Windows equivalents.
- Provide Linux CLI and scripting examples (e.g., Bash, Azure CLI) alongside or instead of PowerShell examples, especially in migration and automation sections.
- Expand guidance and examples for Linux-specific high availability frameworks (Pacemaker) and networking (NFS, Linux DNS, etc.), matching the detail given to Windows Server failover clustering and SMB.
- Where Windows-specific technologies (Active Directory, RDP, SMB) are referenced, include Linux alternatives (e.g., LDAP, SSH, NFS) and clarify their use in SAP on Azure.
- Review all referenced SAP Notes and guides to ensure Linux parity in recommendations and troubleshooting steps.
- Add explicit Linux-focused architecture diagrams and step-by-step deployment examples to match any Windows-centric content.
Sap
Configuration options to minimize network latency with SAP applications | Microsoft Docs
...rticles/sap/workloads/proximity-placement-scenarios.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for VM and proximity placement group deployment, with no equivalent Azure CLI (Linux-friendly) commands. Windows/PowerShell tooling is presented first and exclusively in code samples, while Linux/CLI options are only mentioned in passing or as links. This may hinder Linux users or those preferring cross-platform command-line tools.
Recommendations
- Add equivalent Azure CLI examples alongside every Azure PowerShell command shown, especially for VM and proximity placement group deployment.
- Where deployment steps are described, explicitly mention both PowerShell (Windows) and CLI (Linux/macOS) workflows, giving them equal prominence.
- Ensure that references to external documentation (e.g., deploying VMs to proximity placement groups) are balanced, with both Linux and Windows links presented together.
- Consider including Bash script snippets or guidance for Linux administrators to improve parity.
- Review and update any terminology or instructions that assume a Windows-first environment, making them platform-neutral where possible.
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 (e.g., Storage Spaces) are mentioned before or more prominently than Linux equivalents (e.g., LVM). References to high availability and clustering scenarios often list Windows before Linux, and some examples or links are Windows-centric. There is a lack of explicit Linux command-line or configuration examples, and Windows terminology (e.g., SMB shares) is frequently foregrounded, sometimes without equivalent detail for Linux/NFS. While Linux support is acknowledged, parity in examples and tool descriptions is lacking.
Recommendations
- Provide explicit Linux examples (e.g., LVM commands, NFS configuration) alongside or before Windows examples.
- Ensure that Linux tools (such as LVM) are described in equal detail and prominence as Windows Storage Spaces.
- When listing supported scenarios, alternate the order between Windows and Linux, or group them together to avoid implicit prioritization.
- Include links to Linux-specific high availability and clustering documentation, not just Windows guides.
- Add sample configuration snippets for both Linux and Windows environments where relevant.
- Clarify SMB/NFS support by providing equivalent details and recommendations for both protocols and OSes.
- Review terminology to ensure Linux and open-source technologies are not treated as secondary or afterthoughts.
Sap
SAP on Azure: Supported Scenarios with Azure VMs
...les/sap/workloads/planning-supported-configurations.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: Windows-specific tools and configurations (e.g., Active Directory, Windows Failover Cluster, SQL Server Always On) are frequently mentioned first or in greater detail, with Linux equivalents (such as Pacemaker) often listed after or with less emphasis. Some examples and recommendations are Windows-centric, and certain features (like multi-SID clustering) are described in more depth for Windows than for Linux. There are also cases where Linux examples or tool references are missing or less detailed, especially for high availability and storage scenarios.
Recommendations
- Ensure Linux-based examples (e.g., Pacemaker, DRBD, GlusterFS) are presented with equal prominence and detail as Windows solutions.
- Where Windows tools or patterns are mentioned (e.g., Active Directory, Failover Cluster), provide direct Linux equivalents (e.g., LDAP, Pacemaker) and link to their documentation.
- Avoid listing Windows solutions first by default; alternate or group by OS to avoid implicit prioritization.
- Expand documentation for Linux multi-SID clustering, high availability, and disaster recovery scenarios to match the depth provided for Windows.
- Include explicit Linux command-line or configuration examples (not just references) where Windows/PowerShell examples are given.
- Clarify any limitations or gaps for Linux and provide guidance or workarounds where possible.
Sap
Network connectivity options in Azure with SAP RISE| Microsoft Docs
...ain/articles/sap/workloads/rise-integration-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While the content is generally platform-neutral and focuses on Azure networking concepts, there are subtle indications of Windows preference: Active Directory Domain Services (AD DS) is mentioned as a DNS solution before BIND, and Windows terminology appears first in some places. There are no explicit Linux command-line or configuration examples, nor any references to Linux-specific tools or patterns. The documentation does not provide parity in examples or guidance for Linux administrators, despite mentioning 'virtual-machines-linux' as a service.
Recommendations
- When listing DNS solutions, mention BIND and other Linux-based DNS servers before or alongside AD DS to avoid Windows-first ordering.
- Provide Linux-specific examples or references for network configuration, such as using Linux-based NVAs, iptables, or routing appliances.
- Include sample configurations or command-line snippets for both Windows (PowerShell, AD DS) and Linux (Bash, BIND, systemd-resolved) environments.
- Reference Linux documentation or community resources for common networking tasks in Azure.
- Ensure diagrams and architecture descriptions explicitly mention Linux VM scenarios and tools where relevant.
Sap
SAP ASCS/SCS multi-SID HA with WSFC and Azure shared disk | Microsoft Docs
...kloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation is heavily focused on Windows Server Failover Clustering (WSFC) and provides only Windows-specific instructions, examples, and tooling (PowerShell, Windows DNS Manager, Failover Cluster Manager). There are no references to Linux-based high availability solutions (such as Pacemaker/Corosync), nor are there any Linux CLI or configuration examples. Windows terminology and tools are used exclusively and are presented as the default or only option throughout the guide.
Recommendations
- Add equivalent instructions and examples for SAP ASCS/SCS multi-SID HA using Linux clustering solutions (e.g., Pacemaker/Corosync) and Azure shared disks.
- Include Linux CLI commands (such as az CLI, shell scripts, and cluster management commands) alongside PowerShell examples.
- Reference Linux-supported OS versions and provide guidance for Linux VM preparation and configuration.
- Describe how to configure DNS and load balancer settings using Linux-native tools and procedures.
- Clarify in the introduction that the guide is Windows-specific, or provide links to Linux-focused documentation for SAP HA on Azure.
- Ensure parity in troubleshooting, failover testing, and operational procedures for both Windows and Linux environments.
Sap
Integrating Azure with SAP RISE| Microsoft Docs
...s/blob/main/articles/sap/workloads/rise-integration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Microsoft-centric tools and services (such as Power Apps, Power BI, Microsoft Entra ID, and Sentinel) without providing equivalent examples or explicit parity for Linux or open-source alternatives. While the page is generally high-level and does not provide command-line examples, the 'First steps' section lists Windows-oriented tools and services before any Linux-specific guidance, and there is no mention of Linux-native integration patterns or tools. The absence of Linux-specific examples or references, especially given the context of SAP workloads that often run on Linux, further highlights the bias.
Recommendations
- Include Linux-native integration examples or references, such as using Linux-based automation tools (e.g., Bash scripts, Ansible) for network peering or SAP interface consumption.
- Provide parity for Microsoft tools by mentioning open-source or cross-platform alternatives (e.g., suggest how Linux clients can connect to SAP interfaces, or how to use open-source BI tools alongside Power BI).
- Balance the order of examples so that Linux and Windows scenarios are presented equally, or explicitly state cross-platform compatibility where relevant.
- Add a section or callout specifically addressing Linux administrators, outlining best practices and tools for integrating SAP RISE with Azure from a Linux perspective.
Sap
SAP ASCS/SCS multi-SID HA with WSFC&shared disk on Azure | Microsoft Docs
...ap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, specifically Windows Server Failover Clustering (WSFC) and related tooling. All examples, scripts, and procedures use Windows-centric technologies such as PowerShell, Windows Firewall, DNS Manager, and SIOS DataKeeper for shared disk replication. There is no mention of Linux equivalents, nor any guidance for implementing similar SAP multi-SID HA setups on Linux or with Linux-based clustering solutions. The page title, introduction, and all technical steps assume a Windows-only context.
Recommendations
- Add equivalent guidance and examples for SAP multi-SID HA on Linux, using Linux clustering solutions such as Pacemaker/Corosync.
- Provide scripts and automation examples using Bash, Azure CLI, or Ansible for Linux environments.
- Mention and compare Linux-based shared disk replication solutions (e.g., DRBD) alongside SIOS DataKeeper.
- Include firewall configuration steps for Linux (e.g., using firewalld or iptables).
- Clarify in the introduction whether Linux is supported or not, and if not, link to Linux-specific documentation if available.
- Ensure parity in diagrams and architecture explanations by showing Linux-based alternatives.