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 376-400 of 639 flagged pages
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/data-reference.md
...-docs/blob/main/articles/sap/monitor/data-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias primarily through the extensive referencing of Microsoft SQL Server (MSSQL) system views and functions, many of which are Windows-centric or only available on Windows-based SQL Server deployments. There are no equivalent examples or references for Linux-based database systems (such as SAP HANA on Linux, PostgreSQL, or MySQL), nor are there examples of Linux-native monitoring tools or commands. The documentation also lists Windows-specific system views (e.g., sys.dm_os_windows_info) without Linux alternatives, and the MSSQL sections are significantly more detailed than those for Linux-based systems.
Recommendations
- Include equivalent Linux-based database monitoring examples, such as for SAP HANA on Linux, PostgreSQL, or MySQL, where relevant.
- For each MSSQL/Windows-specific log table or reference, provide a Linux equivalent or explicitly state if none exists.
- Reference Linux-native monitoring tools (e.g., sar, top, vmstat, iostat) and how their data might be integrated or mapped to Azure Monitor tables.
- Balance the level of detail between Windows/MSSQL and Linux/SAP HANA/Prometheus sections, ensuring Linux users have parity in guidance and reference material.
- If certain features or tables are only available for Windows/MSSQL, clearly indicate this and provide guidance for Linux users on alternative monitoring strategies.
Create Pull Request
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-hana.md
...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 references PowerShell as a primary alternative to the Azure portal for resource creation, without mentioning or providing examples for Linux-native tools (such as Azure CLI or Bash scripts). The quickstart links prioritize the Azure portal and PowerShell, which are more commonly used on Windows, and there are no Linux-specific instructions or examples.
Recommendations
- Include Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- When referencing quickstarts, provide links for both PowerShell and Azure CLI (or Bash) to ensure parity.
- Explicitly mention that the instructions are applicable regardless of the underlying OS, and provide any OS-specific notes if needed.
- If scripts or command-line tools are referenced, ensure both Windows (PowerShell) and Linux (Bash/Azure CLI) examples are present.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-netweaver.md
...s/blob/main/articles/sap/monitor/provider-netweaver.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. In several sections, Windows tools (such as Microsoft Management Console) and PowerShell scripts are mentioned before or instead of Linux equivalents. Some instructions and links are provided only for Windows (e.g., the PowerShell script to unprotect web methods), while Linux steps are less detailed or referenced after Windows. There are also troubleshooting steps that provide more detailed instructions for Windows firewall configuration than for Linux, and some automation examples are only given for Windows.
Recommendations
- Ensure that all automation scripts (such as those for unprotecting web methods) are provided for both Windows and Linux, or at least reference equivalent Linux scripts if available.
- When describing steps that differ between Windows and Linux (such as restarting SAPStartSRV), present Linux instructions first or at least in parallel with Windows instructions.
- Provide equal detail for both Windows and Linux in troubleshooting sections, including explicit Linux command-line examples where Windows GUI steps are described.
- Where Windows-specific tools (like MMC) are referenced, include the equivalent Linux commands or tools (e.g., systemctl, sapcontrol) and screenshots if possible.
- Avoid referencing PowerShell scripts or Windows-only automation without also providing Bash or shell script equivalents for Linux environments.
- Review all linked resources (such as GitHub scripts) to ensure Linux users are equally supported, and add Linux-specific links or instructions where missing.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/business-one-azure.md
...blob/main/articles/sap/workloads/business-one-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by frequently mentioning Windows and Windows-specific tools (such as PowerShell) before Linux equivalents, providing more detailed or explicit references to Windows resources, and omitting Linux-specific examples or tools in several sections. While Linux is mentioned, it is often secondary, and practical guidance or examples for Linux users are less prominent or missing.
Recommendations
- Ensure Linux and Windows are given equal prominence in all sections, mentioning both platforms together and in parallel.
- Provide explicit Linux examples and references (e.g., using Bash/CLI, Linux-specific VM sizes, and storage configuration steps) alongside Windows/PowerShell ones.
- When referencing Azure management tools, always include both PowerShell (for Windows) and Azure CLI/Bash (for Linux) options, and avoid listing PowerShell or Windows tools first.
- Include links to both Windows and Linux documentation for all Azure features and tasks.
- Add practical Linux deployment and configuration examples, especially for SAP HANA scenarios, to match the detail given for Windows/SQL Server.
- Review and update language to avoid implying Windows is the default or primary platform.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/cal-ides-erp6-erp7-sp3-sql.md
...n/articles/sap/workloads/cal-ides-erp6-erp7-sp3-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes deploying an SAP IDES solution on Windows and SQL Server, with no mention of Linux-based deployments or examples. All references, solution names, and screenshots are Windows-centric, and there is no guidance for Linux users or alternative database platforms. The documentation assumes and reinforces a Windows-only deployment pattern.
Recommendations
- Add parallel instructions and examples for deploying SAP IDES on Linux (e.g., SUSE or Red Hat) and alternative supported databases (e.g., SAP HANA, MaxDB, or ASE).
- Include screenshots and walkthroughs for Linux-based deployments in SAP CAL, ensuring parity with the Windows examples.
- Explicitly mention the availability (or lack thereof) of Linux-based SAP IDES solutions in SAP CAL, and provide guidance or links for users interested in Linux deployments.
- If SAP CAL does not support Linux for this solution, clarify this limitation early in the documentation and suggest alternative SAP solutions or deployment methods for Linux users.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/set-up-network.md
...-docs/blob/main/articles/sap/monitor/set-up-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Azure portal (a GUI often associated with Windows environments) as the primary method for configuration, and by listing the PowerShell quickstart before any Linux/CLI alternatives. There are no explicit Linux command-line (e.g., Azure CLI, Bash) examples or instructions, and the only alternative setup method mentioned is PowerShell, which is more commonly used in Windows environments. No Linux-native tools or patterns are referenced, and there are no Bash or shell script examples for network configuration.
Recommendations
- Add Azure CLI (az) command examples alongside or before PowerShell examples for all major configuration steps.
- Include Bash/shell script snippets for common tasks, such as subnet creation, NSG rule configuration, and DNS settings.
- Reference Linux-native tools and workflows (e.g., using SSH, editing /etc/resolv.conf for DNS) where appropriate.
- Ensure that quickstart and next steps sections provide parity between PowerShell and Azure CLI/Bash options, and consider listing CLI/Bash options before PowerShell to avoid implicit Windows-first bias.
- Explicitly mention that all steps can be performed from Linux/macOS as well as Windows, and provide links to relevant cross-platform documentation.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/businessobjects-deployment-guide.md
...cles/sap/workloads/businessobjects-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias throughout. Windows and Azure SQL Database are consistently mentioned before Linux and MySQL equivalents, and detailed examples or guidance for Linux deployments are limited or deferred to external links. Windows-specific tools and services (e.g., Azure SQL Database, Premium SSDs for Windows, and explicit mention of 'SAP BOBI Platform on Windows with Azure SQL Database') are highlighted, while Linux alternatives are less emphasized or lack equivalent detail. There are no Linux/POSIX command-line or configuration examples, and Linux deployment guidance is relegated to a separate page rather than being integrated.
Recommendations
- Present Windows and Linux options in parallel throughout the documentation, rather than listing Windows first or in more detail.
- Include explicit Linux deployment examples and configuration steps within this main guide, not just as a link to a separate Linux-specific page.
- Provide parity in discussion of database options (e.g., equal detail for Azure Database for MySQL and Azure SQL Database, including limitations and best practices for both platforms).
- Mention Linux-native tools and patterns (e.g., NFS setup, Linux file permissions, systemd service management) alongside Windows equivalents.
- Ensure that all architectural diagrams and storage/networking sections include Linux-specific considerations and not just Windows defaults.
- Add command-line examples for both Windows (PowerShell, CMD) and Linux (Bash, shell scripts) where relevant.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-general.md
...blob/main/articles/sap/workloads/dbms-guide-general.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally strives for parity between Windows and Linux, but there are several instances of Windows bias. Windows tools and patterns (e.g., Storage Spaces, drive D:) are often mentioned before or in more detail than their Linux equivalents. Some examples and links are Windows-specific, and Windows terminology is sometimes used as the default. Linux alternatives are present but sometimes less detailed or referenced after Windows. There are also references to Windows-specific guides and tools without equivalent Linux guidance in some sections.
Recommendations
- Ensure that Linux examples and tools (e.g., LVM, MDADM) are presented with equal prominence and detail as Windows tools (e.g., Storage Spaces).
- When providing step-by-step guides or links (such as for converting unmanaged to managed disks), ensure Linux and Windows links are presented together and with equal context.
- Avoid using Windows terminology (e.g., 'drive D:') as the default; always provide the Linux equivalent (e.g., '/mnt/resource') in parallel.
- Where Windows-specific tools or procedures are described (such as Storage Spaces), provide equally detailed Linux procedures and best practices.
- Review all sections for implicit Windows-first ordering and alternate with Linux-first or neutral ordering.
- Include Linux-specific troubleshooting and operational guidance where Windows-specific guidance is given.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-maxdb.md
...s/blob/main/articles/sap/workloads/dbms-guide-maxdb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively covers deployment, configuration, and operational guidance for SAP MaxDB, liveCache, and Content Server on Windows in Azure VMs. There is no mention of Linux support, Linux-specific instructions, or parity in tooling or examples. Windows tools and patterns (such as Windows Storage Pools/Spaces, VSS integration, Microsoft IIS) are referenced without Linux equivalents, and all recommendations and best practices are framed around Windows environments.
Recommendations
- Add a section or parallel guidance for deploying SAP MaxDB, liveCache, and Content Server on Linux-based Azure VMs, including supported Linux distributions and versions.
- Provide Linux-specific storage configuration examples (e.g., using LVM, mdadm, or other Linux-native storage management tools) alongside or before Windows examples.
- Include backup and restore guidance for Linux, referencing Linux-compatible backup tools and methods (e.g., native MaxDB tools, cron jobs, or third-party Linux backup solutions).
- Mention and illustrate how to achieve similar high availability and performance configurations on Linux (e.g., using Linux RAID, LVM striping, or Azure Disk features).
- Reference Linux equivalents for any Windows-specific technologies (e.g., suggest Apache or Nginx as alternatives to IIS for Content Server, or describe how to integrate with Linux-native VSS alternatives if needed).
- Clearly indicate in the introduction whether Linux is supported or not, and if not, provide a rationale or roadmap for Linux support.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-sapase.md
.../blob/main/articles/sap/workloads/dbms-guide-sapase.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux in most configuration tables and recommendations. However, there are several areas where a Windows bias is evident: Windows-specific tools and settings (e.g., Storage Spaces, NTFS, Windows Firewall) are mentioned first or exclusively, and some operational details (such as firewall configuration) are given only for Windows. The 'Specifics to SAP ASE on Windows' section is more detailed than its Linux counterpart, and some Linux-specific operational examples (e.g., firewall rules) are missing. In some cases, Windows terminology and tools are referenced before Linux equivalents, and certain recommendations (like 'Lock Pages in Memory') are only described for Windows.
Recommendations
- Ensure that operational instructions (such as firewall configuration) are provided for both Linux (e.g., iptables, firewalld, ufw) and Windows, not just Windows.
- When describing disk aggregation and file systems, present Linux and Windows options in parallel, or alternate which OS is mentioned first.
- Provide Linux-specific tuning and troubleshooting examples with the same level of detail as Windows (e.g., explain how to set up 'Lock Pages in Memory' or its Linux equivalent, if applicable).
- Include Linux command-line examples for tasks where only Windows or PowerShell instructions are given.
- Balance the depth of 'Specifics' sections for both OSes, ensuring Linux operational nuances are equally covered.
- Review all tables and recommendations to ensure Linux is not consistently listed after Windows, and consider alternating or grouping by scenario rather than OS.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-sqlserver.md
...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 heavily biased towards Windows, explicitly stating that the scope is the Windows version of SQL Server and that SAP does not support SQL Server on Linux for SAP workloads. All examples, configuration steps, and recommendations are for Windows Server environments, with exclusive references to Windows tools, filesystems (NTFS), and Windows-specific VM disk patterns. There are no Linux equivalents or even mentions of Linux-based deployment, tools, or best practices. Even general SQL Server features are described only in the context of Windows Server.
Recommendations
- Clearly state early in the document that SAP does not support SQL Server on Linux for SAP workloads, but also provide a brief rationale and a link to any SAP or Microsoft roadmap or support statement for Linux.
- If possible, provide a short section or callout for customers interested in Linux, summarizing the current support status and alternatives (e.g., HANA on Linux, or SQL Server for non-SAP workloads).
- Where general SQL Server or Azure VM best practices are discussed, clarify which recommendations are Windows-specific and which could apply to Linux if/when support is available.
- Avoid using Windows-specific terminology (e.g., NTFS, D:\ drive, Windows command prompt) without noting that these are not applicable to Linux.
- If Linux support is added in the future, ensure all examples, configuration tables, and best practices are provided for both Windows and Linux, or clearly indicate differences.
- Add a note in the 'Next steps' or summary section to direct Linux users to appropriate documentation or support channels.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-sapiq.md
...s/blob/main/articles/sap/workloads/dbms-guide-sapiq.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. In several sections, Windows-specific tools and patterns (such as Windows Server Failover Cluster and SMB/UNC path backup examples) are discussed in more detail or presented first. The Windows high-availability solution is described with explicit references to Azure shared disks and WSFC, while the Linux equivalent (Pacemaker with Azure NetApp Files) is mentioned but with less detail and no command-line or configuration examples. The backup section provides a concrete UNC path example for Windows but omits a corresponding Linux/NFS example. The overall structure often presents Windows options before Linux, and some advanced features (like Azure shared disks) are available only for Windows, but this is a platform limitation rather than a documentation bias.
Recommendations
- Provide equivalent Linux/NFS backup path examples (e.g., show a sample BACKUP DATABASE command using an NFS mount path).
- Balance the level of detail between Windows and Linux high-availability solutions, possibly by including more information or links for Pacemaker configuration.
- Where possible, present Windows and Linux options in parallel or in a neutral order, rather than consistently listing Windows first.
- Explicitly mention any platform limitations (e.g., Azure shared disks not available for Linux) as Azure constraints, not as documentation omissions.
- Include Linux-specific automation or scripting examples where Windows PowerShell or WSFC are discussed.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/disaster-recovery-overview-guide.md
...cles/sap/workloads/disaster-recovery-overview-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates several forms of Windows bias. PowerShell is mentioned as the only method for configuring Azure Site Recovery for certain VM deployments, with no equivalent Linux/CLI example. Windows-specific tools (e.g., RoboCopy) are referenced for storage replication, while Linux alternatives (e.g., rsync) are mentioned but less emphasized or explained. There is a specific callout for SAP systems running on Windows with Azure Shared Disk, but no parallel guidance for Linux-based SAP systems. Overall, examples and tooling references tend to prioritize or exclusively mention Windows approaches, with Linux alternatives either missing or less detailed.
Recommendations
- Provide equivalent Azure CLI or Bash script examples wherever PowerShell is referenced, especially for configuring Azure Site Recovery for scale sets.
- When referencing tools like RoboCopy for SMB file replication, also provide equal detail and guidance for Linux tools such as rsync or scp.
- Include explicit guidance and examples for SAP systems running on Linux, particularly in sections that currently only mention Windows (e.g., Azure Shared Disk scenarios).
- Ensure that all platform-specific recommendations (Windows or Linux) are presented in parallel, with equal prominence and explanation.
- Review all sections for implicit assumptions of Windows environments and add Linux-specific considerations where relevant (e.g., Active Directory integration, storage configuration).
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/disaster-recovery-sap-guide.md
.../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 are signs of Windows bias. Windows-specific tools and patterns (e.g., Robocopy, Windows Server Failover Cluster) are mentioned explicitly, sometimes before or more prominently than their Linux equivalents. The Linux sections are present and detailed, but some examples and tool recommendations (such as for file replication) are more explicit for Windows (e.g., Robocopy for SMB) than for Linux (where only 'custom (like rsync)' is mentioned). In backup support tables, Windows/SMB scenarios are called out with supported tools, while Linux/NFS scenarios are marked as 'Not Supported' with less guidance. There is also a tendency to mention Windows patterns (e.g., WSFC, cloud witness) in more detail or with more direct links than Linux clustering solutions.
Recommendations
- Provide equally detailed, step-by-step examples for Linux as for Windows, especially for storage replication and cluster reconfiguration.
- Explicitly mention and link to Linux-native tools (e.g., rsync, lsyncd, DRBD) for file replication, similar to how Robocopy is highlighted for Windows.
- Where Windows-specific tools or patterns are mentioned, ensure the Linux equivalents are introduced with equal prominence and detail.
- In tables and process descriptions, avoid listing Windows/SMB solutions first by default; alternate or group by OS to avoid implicit prioritization.
- For backup and restore, clarify Linux/NFS alternatives or workarounds if Azure Backup is not supported, and provide links to community or third-party solutions.
- Where possible, provide parity in diagrams and architecture visuals for both Linux and Windows scenarios.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/hana-vm-operations.md
...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 demonstrates a moderate Windows bias. While it is focused on SAP HANA (which is Linux-centric), Windows tools and patterns are often mentioned first or exclusively (e.g., Azure PowerShell cmdlets are listed before Azure CLI, and Windows Server SOFS and failover clustering are referenced in high-availability scenarios). There is a lack of explicit Linux command-line or scripting examples, and some operational instructions (such as VM deployment) mention PowerShell before CLI, which is more commonly used in Linux environments. Although Linux is referenced (especially for SUSE and Red Hat), practical Linux-centric operational examples are sparse.
Recommendations
- When listing deployment methods, mention Azure CLI before or alongside Azure PowerShell, as CLI is cross-platform and preferred by many Linux users.
- Provide explicit Linux shell command examples (e.g., using az CLI, bash scripts, or relevant Linux tools) for common operations such as VM deployment, storage configuration, and network setup.
- For high-availability and clustering, ensure Linux-first examples and guidance are given, especially since SAP HANA is most often deployed on Linux.
- When referencing Windows-specific tools or patterns (e.g., Windows Server SOFS, Windows failover cluster), always provide equivalent Linux solutions (e.g., Pacemaker, NFS, or Linux clustering) and ensure they are given equal prominence.
- Add more Linux-focused troubleshooting and operational guidance, such as systemd service management, log file locations, and common Linux networking commands.
- Review the ordering of instructions and examples to avoid implicit prioritization of Windows tools or workflows.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/deployment-guide.md
...s/blob/main/articles/sap/workloads/deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as PowerShell, sysprep, and Active Directory domain join) are often mentioned first or exclusively, and Windows-specific instructions are more detailed. While Linux is supported and included, Linux instructions are sometimes less prominent, and some advanced deployment steps (e.g., domain join) are only documented for Windows. PowerShell is referenced as a primary automation tool, with Azure CLI for Linux mentioned as an alternative rather than an equal. Some sections (such as joining a domain) are marked 'Windows only' with no Linux equivalent or guidance.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and detail, especially in step-by-step sections.
- Where a feature is Windows-only (e.g., domain join), explicitly state the Linux alternative or clarify the lack of equivalent functionality.
- Provide Linux-first or side-by-side examples for automation (e.g., Azure CLI, shell scripts) alongside PowerShell.
- Expand Linux-specific troubleshooting and configuration guidance to match the depth of Windows sections.
- Avoid defaulting to Windows tools or patterns in general guidance; instead, present both Linux and Windows options in parallel.
- Review and update the prerequisites section to clarify that a Linux workstation can be used for all Linux VM management tasks, not just as an alternative.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel-pacemaker.md
...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 focused on setting up Pacemaker on RHEL in Azure and is generally Linux-centric, with extensive Bash and Linux-native tooling examples. However, there is a notable bias in the section on configuring Azure shared disks, where only PowerShell examples are provided for disk creation and attachment, with no Azure CLI or portal equivalents shown first or in detail. Additionally, references to Azure role assignment and identity management link to Windows VM documentation or PowerShell-based guides before mentioning Linux/CLI alternatives. This can create friction for Linux users who may not use PowerShell or Windows tools.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell for all Azure resource provisioning steps, especially for disk creation and attachment.
- Include instructions for performing key Azure operations (e.g., managed identity assignment, custom role creation) using the Azure portal and Azure CLI, not just PowerShell or Windows-centric documentation.
- Where links are provided for identity or role assignment, ensure Linux/CLI/portal documentation is referenced first or equally, not just Windows VM or PowerShell guides.
- Explicitly state that all Azure resource management steps can be performed from Linux environments, and provide parity in example commands.
- Consider adding a table or section comparing PowerShell, Azure CLI, and portal methods for common tasks to help Linux users choose their preferred workflow.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-zones.md
...main/articles/sap/workloads/high-availability-zones.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as Windows Server Failover Clustering and PowerShell scripts) are mentioned first or exclusively in several places. Automated network latency measurement is only described with a PowerShell script, with no equivalent Linux automation provided. The 'Next steps' section exclusively links to Windows failover cluster guides, omitting Linux cluster equivalents. While Linux is referenced (e.g., Pacemaker, SUSE, RHEL), the documentation tends to provide more detailed or prioritized guidance for Windows scenarios.
Recommendations
- Provide Linux automation examples for tasks such as network latency measurement (e.g., bash scripts using niping or other SAP-supported tools).
- In sections discussing failover clustering, mention Linux Pacemaker and Windows Failover Clustering equally, and provide parallel guidance or links for both.
- Balance 'Next steps' links to include Linux high availability guides (e.g., clustering SAP ASCS/SCS with Pacemaker on SUSE or RHEL).
- When referencing scripts or tools (such as the PowerShell latency test), offer or link to equivalent Linux scripts if available, or note how Linux users can accomplish the same task.
- Ensure that examples, recommendations, and tool references are presented in a platform-neutral order or with equal prominence for both Windows and Linux.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/integration-get-started.md
...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 is heavily focused on Microsoft and Azure integration scenarios for SAP, with a strong emphasis on Microsoft tools, platforms, and services (e.g., Power Platform, Microsoft Entra ID, Microsoft Defender, Microsoft Sentinel, Microsoft Teams, Office, etc.). While there are some mentions of Linux (e.g., Defender for Endpoint on Linux), the majority of examples, resources, and integration patterns are centered around Windows-based or Microsoft-native solutions. There is a lack of parity in Linux-specific guidance, examples, or tooling, and Linux is rarely mentioned first or in equal detail compared to Windows/Microsoft solutions.
Recommendations
- Include Linux-specific integration examples and guidance for SAP workloads, such as using open-source tools, Linux-native authentication/authorization mechanisms, and Linux-based automation/orchestration.
- When discussing security (e.g., Defender for Endpoint), provide balanced, parallel examples for both Windows and Linux, including configuration steps and best practices.
- Highlight cross-platform compatibility and limitations for each Microsoft tool or service, and explicitly mention any Linux support or alternatives.
- Add sections or callouts for Linux administrators, such as integration with Linux-based identity providers, Linux printing solutions, or Linux-native monitoring/logging tools.
- Ensure that when listing supported platforms or scenarios, Linux is mentioned alongside Windows, and not as an afterthought.
- Provide links to SAP documentation or community resources that focus on Linux deployments and integration patterns.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-guide-storage.md
.../main/articles/sap/workloads/planning-guide-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology, tools, and patterns (such as SMB, Windows Storage Spaces, and references to Windows-specific high availability guides) are often mentioned before or more prominently than their Linux/NFS or LVM equivalents. In some cases, Windows-specific features are described in detail, while Linux alternatives are only briefly mentioned or referenced. There is a lack of explicit Linux command-line examples or detailed guidance for Linux-specific storage management (e.g., LVM striping), and some high-availability scenarios are illustrated with Windows first or exclusively.
Recommendations
- Ensure Linux/NFS examples and tools (e.g., LVM, mdadm) are given equal prominence and detail as Windows/SMB/Storage Spaces, including explicit command-line examples where appropriate.
- When referencing high availability or clustering guides, list Linux and Windows options together, or alternate the order to avoid always listing Windows first.
- Include Linux-specific best practices for storage striping, mounting, and performance tuning, not just generic statements or references.
- Where Windows tools or patterns are mentioned (e.g., Storage Spaces), provide the Linux equivalent (e.g., LVM striping) with similar depth.
- Add explicit Linux command-line or configuration examples for common scenarios (e.g., mounting NFS shares, configuring LVM striping for SAP data/log volumes).
- Review tables and capability matrices to ensure Linux and Windows are equally represented, and clarify where features or recommendations differ by OS.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md
...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 environments, specifically Windows Server Failover Clustering (WSFC). All operational examples, scripts, and tooling references are for Windows and PowerShell. There is no mention of Linux-based clustering (e.g., Pacemaker), nor are there any Linux command-line examples or guidance for equivalent SAP HA setups on Linux. Windows-specific tools (Failover Cluster Manager, Windows DNS Manager) are referenced exclusively, and the supported OS section only lists Windows Server versions.
Recommendations
- Add a section or a separate guide for SAP ASCS/SCS multi-SID HA on Linux, using Pacemaker or other supported Linux clustering solutions.
- Provide equivalent Linux shell (bash) commands and Azure CLI examples for disk creation, attachment, and formatting.
- Include Linux-specific guidance for DNS configuration (e.g., using BIND or /etc/hosts), cluster resource management, and failover testing.
- Mention supported Linux distributions and versions in the 'Supported OS versions' section.
- Where possible, present both Windows and Linux instructions side-by-side or clearly indicate which steps are OS-specific.
- Reference SAP Notes or guides for Linux HA configuration, and link to Azure documentation for Linux-based SAP high availability.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-guide.md
...ocs/blob/main/articles/sap/workloads/planning-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation, while targeting both Linux and Windows SAP deployments on Azure, exhibits subtle Windows bias. Windows terminology and tools (e.g., RDP, Windows Server Active Directory, Windows failover clustering, PowerShell) are often mentioned before or more prominently than their Linux equivalents. Some examples and references (such as migration scripts and clustering) are Windows-centric or use Windows-first language. There are also instances where only Windows-specific tools or patterns are mentioned, or where Linux alternatives are not given equal detail or visibility.
Recommendations
- Ensure that Linux tools and patterns (e.g., SSH, Linux-based clustering, Linux-native management commands) are mentioned alongside or before Windows equivalents, especially since the target platform is vm-linux.
- Provide Linux/Unix command-line examples (e.g., Azure CLI, Bash scripts) in parallel with PowerShell or Windows examples.
- When referencing migration scripts or utilities, include Linux-compatible versions or alternatives, not just PowerShell-based solutions.
- In sections discussing Active Directory, clustering, or file shares, give equal prominence and detail to Linux-native solutions (e.g., Microsoft Entra ID, Pacemaker, NFS) as to Windows (e.g., Windows Server AD, Windows failover clustering, SMB).
- Review and update references to ensure that Linux scenarios are not treated as exceptions or afterthoughts, but as first-class, fully supported options.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/proximity-placement-scenarios.md
...rticles/sap/workloads/proximity-placement-scenarios.md
High Priority
View Details →
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 deployment commands, referencing Windows-centric tools and patterns first, and omitting equivalent Azure CLI (Linux-friendly) command examples in the main instructional sections. While Linux/CLI documentation is linked in the 'Next steps' and 'Change proximity placement group configurations' sections, the core walkthroughs and code samples are exclusively PowerShell-based, which may disadvantage Linux users or those preferring cross-platform tooling.
Recommendations
- For every Azure PowerShell example, provide an equivalent Azure CLI example side-by-side or immediately following, especially in the main instructional sections.
- When referencing deployment methods, mention Azure CLI and PowerShell together, or list CLI first to avoid Windows-first bias.
- In code blocks, clearly label which platform/tool each example is for (e.g., 'Azure CLI', 'Azure PowerShell').
- Ensure that Linux users can follow all steps without needing to switch to Windows or PowerShell.
- Consider including a short section or table summarizing both PowerShell and CLI commands for common tasks.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-supported-configurations.md
...les/sap/workloads/planning-supported-configurations.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several ways: Windows terminology, tools, and configurations are consistently mentioned before Linux equivalents, with more detail and coverage for Windows scenarios. Windows-specific technologies (e.g., Windows Failover Cluster, Scale-Out File Server, SIOS Datakeeper) are described in depth, while Linux solutions (e.g., Pacemaker) are often grouped together or mentioned after Windows. Some examples and recommendations are Windows-only or lack Linux command-line or configuration examples. In certain sections, Linux alternatives are only briefly referenced or require the reader to consult external documentation, and Oracle Linux is explicitly called out as unsupported for some features, with third-party solutions required.
Recommendations
- Ensure that Linux-based solutions (e.g., Pacemaker, DRBD, GlusterFS) are described with the same level of detail and prominence as Windows solutions, including step-by-step configuration or links to such guides.
- Present Linux and Windows options in parallel, rather than listing Windows first or in more detail.
- Include Linux command-line examples (e.g., for resource limiting, cluster setup) where Windows-specific tools or PowerShell commands are mentioned.
- Where third-party solutions are required for Linux (e.g., Oracle Linux HA), provide clear guidance, supported options, and links to official documentation, not just a mention.
- Review all tables and lists to ensure Linux distributions and tools are included wherever Windows is referenced.
- Add explicit Linux examples for monitoring, memory/cpu capping, and storage configuration, not just generic statements.
- Highlight any feature parity gaps and, if possible, provide workarounds or roadmaps for Linux support.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration.md
...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 Windows bias by referencing Microsoft-centric tools and services (e.g., Power App, Power BI, Microsoft Entra ID, Sentinel) as primary integration examples, without providing equivalent Linux or open-source alternatives. Despite the page being tagged for both Linux and Windows, there are no explicit Linux-specific examples, tools, or command-line instructions. The focus on Microsoft ecosystem tools and the absence of Linux-native integration patterns or examples may make the documentation less accessible or actionable for Linux-centric users.
Recommendations
- Include Linux-native integration examples, such as using open-source tools (e.g., curl, wget, Linux-based monitoring/identity solutions) for connecting to SAP RISE.
- Provide parallel examples for Linux environments where Microsoft tools are mentioned (e.g., alternatives to Power App/Power BI, such as Grafana or open-source BI tools).
- Explicitly mention and demonstrate how Linux VMs or Linux-based services can be integrated with SAP RISE, including relevant command-line instructions.
- Balance the order of examples so that Linux and Windows tools are presented equally, or alternate which platform is presented first.
- Reference cross-platform or open standards-based solutions where possible, to ensure inclusivity for non-Windows environments.