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 576-600 of 639 flagged pages
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/start-stop-sap-systems.md
...les/sap/center-sap-solutions/start-stop-sap-systems.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows and Linux support, but there is a subtle Windows bias: Windows is consistently listed before Linux in supported OS mentions, and Windows clustering (WSFC) is referenced alongside Linux clustering tools. The only command-line interfaces referenced are Azure PowerShell and Azure CLI, which are cross-platform but often associated with Windows environments. There are no explicit Linux shell or native OS-level examples, and the documentation does not provide parity in examples or troubleshooting for Linux-specific scenarios.
Recommendations
- Alternate the order of OS mentions (e.g., sometimes list Linux before Windows) to avoid the perception of Windows primacy.
- Include explicit Linux shell (bash) command examples where relevant, especially for prerequisites or troubleshooting (e.g., checking sapstartsrv status, managing services).
- Reference Linux-native tools and commands (such as systemctl, journalctl, or Pacemaker commands) in troubleshooting or advanced sections.
- Provide screenshots or walkthroughs from both Windows and Linux perspectives when discussing prerequisites or cluster configurations.
- Clarify that Azure CLI and PowerShell are cross-platform, and provide usage examples on both Windows and Linux terminals.
Create Pull Request
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/hana-example-installation.md
...icles/sap/large-instances/hana-example-installation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a detailed example of downloading SAP HANA installation packages using a Windows jump box, with screenshots and instructions specific to Windows. There are no equivalent instructions or examples for Linux-based jump boxes, despite the article being targeted at Linux (as indicated by metadata and context). This creates a Windows-first bias and omits guidance for users operating in a Linux environment.
Recommendations
- Add parallel instructions and screenshots for downloading and extracting SAP HANA installation packages using a Linux jump box (e.g., using wget, curl, tar, or unzip).
- Explicitly mention that the jump box can be either Windows or Linux, and provide guidance for both scenarios.
- Ensure that all steps involving file extraction, copying, and permissions include Linux command-line examples where appropriate.
- Review the documentation for any other Windows-specific assumptions and clarify or generalize them to cover Linux workflows.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/dbms-guide-ibm.md
...ocs/blob/main/articles/sap/workloads/dbms-guide-ibm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains good Linux parity, but there are subtle signs of Windows bias. In several sections, Windows tools and patterns (such as Windows Storage Pools and PowerShell cmdlets) are mentioned before their Linux equivalents (LVM, mdadm), and Windows-specific configuration steps are sometimes described in more detail. Some features (e.g., Accelerated Networking) are recommended for Windows first, even though they apply to both platforms. However, Linux-specific guidance and examples are present, and Linux is well-represented in storage, HA, and deployment sections.
Recommendations
- When mentioning platform-specific tools or patterns (e.g., Windows Storage Pools, PowerShell), always present Linux equivalents (e.g., LVM, mdadm) first or in parallel, with equal detail.
- Ensure that configuration steps for Linux (such as LVM/mdadm setup) are as detailed as those for Windows, including example commands where appropriate.
- In recommendations (e.g., Accelerated Networking), avoid phrasing that suggests Windows is the primary or default platform; instead, state applicability to both platforms up front.
- Where Windows-specific PowerShell cmdlets are referenced, provide equivalent Linux shell commands or links to relevant documentation.
- Continue to expand Linux-specific sections, especially for advanced topics (e.g., backup/restore, performance tuning), to ensure full parity.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/expose-sap-odata-to-power-query.md
...icles/sap/workloads/expose-sap-odata-to-power-query.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing examples and guidance for Microsoft-centric tools and environments (Excel Desktop, Power BI, Power Query, Power Automate), with no mention of Linux clients, alternative open-source tools, or cross-platform usage. All illustrated workflows and screenshots are from Windows-based applications, and there is no guidance for users on Linux or non-Windows platforms.
Recommendations
- Include explicit guidance and examples for accessing SAP OData feeds using Power Query on non-Windows platforms, such as Excel for the web, Power BI web, or any available Linux-compatible clients.
- Mention and, where possible, provide examples for open-source or cross-platform OData clients (e.g., using Python with pandas or requests, curl, or other tools available on Linux) to demonstrate how similar integrations can be achieved outside the Microsoft ecosystem.
- Clarify any platform limitations (e.g., if Power Query is only available on Windows) and suggest alternative approaches for Linux users.
- Add a section or callout addressing Linux/macOS users, outlining what is and is not supported, and linking to relevant resources or community solutions.
- Ensure that any code snippets, screenshots, or step-by-step instructions are either platform-neutral or are supplemented with Linux/macOS equivalents where possible.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/rise-integration-services.md
...in/articles/sap/workloads/rise-integration-services.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing the SAP .NET connector and the Microsoft on-premises data gateway, both of which are primarily Windows-based technologies. There are no explicit examples, instructions, or mentions of Linux-native integration runtimes, connectors, or gateway alternatives, despite the page being tagged for Linux virtual machines.
Recommendations
- Include examples and references for Linux-based integration runtimes, such as running the self-hosted integration runtime on Linux (if supported), or provide guidance for Linux-based alternatives.
- Mention and provide instructions for using SAP connectors that are cross-platform or Linux-native, such as the SAP Java Connector (JCo) or ODBC/JDBC drivers on Linux.
- Clarify whether the on-premises data gateway can be deployed on Linux, and if not, suggest alternative architectures for Linux environments.
- Ensure that code snippets, deployment instructions, and architectural diagrams include both Windows and Linux scenarios where applicable.
- Explicitly state OS requirements and provide parity in documentation for both Windows and Linux users.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-edge-integration-cell-with-azure.md
.../sap/workloads/sap-edge-integration-cell-with-azure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Azure and its managed Kubernetes services (AKS, Azure ARC), which are primarily used in Windows-centric environments. There is no mention of deploying SAP Edge Integration Cell on non-Azure Kubernetes distributions (such as vanilla Kubernetes on Linux, OpenShift, or other cloud providers) or using Linux-native tools. All examples and recommendations are focused on Azure services, with no guidance for Linux users or those operating outside the Microsoft ecosystem.
Recommendations
- Include examples and guidance for deploying SAP Edge Integration Cell on generic (non-Azure) Kubernetes clusters, such as those running on Linux VMs or other cloud providers.
- Mention and provide links to Linux-native tools and best practices for Kubernetes management (e.g., kubectl, Helm, kustomize) alongside Azure-specific tools.
- Add a section comparing Azure-specific services with their open-source or Linux-native counterparts (e.g., Azure Database for PostgreSQL vs. self-hosted PostgreSQL on Linux).
- Provide sample deployment manifests or scripts that are platform-agnostic, not tied to Azure-specific resources.
- Clarify which steps are Azure-specific and which are applicable to any Kubernetes environment, to help Linux users adapt the instructions.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-availability-overview.md
...ticles/sap/workloads/sap-hana-availability-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a 'windows_first' bias by specifically recommending the reader to review the 'Manage the availability of Windows virtual machines in Azure' article before defining their availability architecture, without providing an equivalent Linux resource. Additionally, while PowerShell and the Azure portal are mentioned for VM deployment, there is only a brief mention of the Azure CLI, and no explicit Linux-based examples or tools are provided. There are no Linux-specific instructions or references to Linux VM management, which is relevant since SAP HANA is commonly deployed on Linux.
Recommendations
- Include references to both Windows and Linux VM availability documentation, such as 'Manage the availability of Linux virtual machines in Azure'.
- Provide explicit examples or links for deploying and managing VMs using Linux-native tools (e.g., Bash, SSH, Linux command-line utilities) alongside PowerShell and the Azure portal.
- Ensure that any prerequisite or recommended reading covers both Windows and Linux scenarios equally.
- Where possible, add Linux-specific considerations or best practices for SAP HANA on Azure VMs.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-suse-pacemaker.md
...ap/workloads/high-availability-guide-suse-pacemaker.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is highly focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, with all configuration and operational examples using Linux commands and tools. However, there is a notable Windows bias in the following ways: (1) The only example for creating and attaching Azure shared disks is given in PowerShell, a Windows-centric tool, rather than Azure CLI or ARM templates, which are more cross-platform and native to Linux users. (2) In the 'Overview' and some cross-references, Windows is mentioned before Linux (e.g., 'virtual-machines-windows,virtual-network,storage' in metadata, and [virtual-machines-windows-maintenance] is referenced before [virtual-machines-linux-maintenance]). There are no missing Linux examples for the core SLES/Pacemaker content, but the disk provisioning step assumes PowerShell, which may be unfamiliar or unavailable to Linux users.
Recommendations
- Provide Azure CLI examples for creating and attaching Azure shared disks, as Azure CLI is cross-platform and more familiar to Linux users.
- Reorder references and metadata to mention Linux before Windows where appropriate, especially since the guide is Linux-specific.
- Explicitly state that PowerShell examples are for illustration only and provide equivalent steps for Linux environments.
- Where possible, include ARM/Bicep template snippets for infrastructure provisioning to ensure parity for users who prefer declarative approaches.
- Audit other cross-references and links to ensure Linux documentation is not deprioritized or omitted in favor of Windows.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap-troubleshooting.md
.../sap/workloads/vm-extension-for-sap-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows troubleshooting steps and directory paths before Linux equivalents, and refers to Windows-specific tools and log file locations first. While Linux sections are present and reasonably complete, the ordering and initial focus on Windows may suggest a subtle Windows bias.
Recommendations
- Alternate the order of Windows and Linux sections, or present them in parallel tables or tabs to give equal prominence.
- When referencing log files or directories, mention both Windows and Linux paths together where possible.
- Ensure that tool names and troubleshooting steps are given equal detail and visibility for both platforms.
- Consider adding more explicit Linux command-line examples or references, if applicable, to match any Windows/Powershell examples.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-start.md
...les/sap/workloads/sap-high-availability-guide-start.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation consistently lists Windows/WSFC scenarios and guides before Linux equivalents, and uses Windows-specific terminology (e.g., 'Windows Server Failover Cluster', 'shared disk', 'file share') as primary patterns. Linux options are present but appear after Windows, and the structure and imagery reinforce a Windows-first perspective.
Recommendations
- Alternate the order of Windows and Linux sections/examples to avoid always presenting Windows first.
- Use neutral, cross-platform terminology in summaries and section headings where possible (e.g., 'cluster framework' instead of 'failover cluster').
- Ensure that Linux-specific tools and patterns (e.g., Pacemaker, Corosync, DRBD, NFS, GlusterFS) are described with equal detail and prominence as Windows tools.
- Add explicit cross-references between Windows and Linux sections to help users find their platform quickly.
- Consider a summary table or matrix at the top that lists all supported OSes and high-availability options equally.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/virtual-machine-scale-set-sap-deployment-guide.md
...oads/virtual-machine-scale-set-sap-deployment-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Virtual Machine Scale Sets for SAP workloads, but the PowerShell section is given equal prominence to the CLI, and there is no explicit mention or example of Linux-specific command-line tools or workflows (such as Bash scripts or Linux-native automation). The CLI examples use variable syntax compatible with both Bash and PowerShell, but the PowerShell section is presented as a distinct, full-featured alternative, which may suggest a Windows-centric approach. Additionally, the documentation does not reference Linux-specific tools or patterns, and the quick start guide link at the end points to a Linux VM creation guide, but this is not integrated into the main workflow examples.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and provide Bash-specific variable syntax/examples to reinforce Linux compatibility.
- Add a section or examples showing how to automate or script these deployments using Bash on Linux, including environment setup and best practices for Linux users.
- Where PowerShell is presented, clarify that it is available cross-platform, but also provide guidance for Linux users who may prefer Bash or other shells.
- Reference Linux-native tools or patterns where relevant (e.g., cloud-init, Ansible, or other automation tools commonly used in Linux environments).
- Ensure that Linux and Windows are given equal prominence in both narrative and example sections, and avoid implying that PowerShell is the primary or preferred method.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-high-availability.md
...n/articles/sap/workloads/sap-hana-high-availability.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is overwhelmingly focused on SUSE Linux Enterprise Server (SLES) and Linux-native tools and workflows, with all configuration, installation, and operational examples provided for Linux. However, there is minor evidence of Windows bias in the ordering and referencing of SAP Notes, where Windows is sometimes mentioned before Linux, and in the mention of Windows-specific SAP kernel versions. There are also references to Azure CLI, Azure Portal, and PowerShell for load balancer configuration, but all Linux equivalents are present and equally detailed. No PowerShell-heavy or Windows-only examples are present, and Linux parity is strong throughout.
Recommendations
- When referencing SAP Notes or supported OS/kernel versions, list Linux before or alongside Windows to reflect the Linux focus of the guide.
- If mentioning Windows-specific details, ensure Linux details are equally or more prominently presented, especially in introductory or summary sections.
- Continue to provide Linux-first examples and ensure that any cross-platform tooling (such as Azure CLI, Portal, PowerShell) is always presented with Linux parity.
- Consider removing or de-emphasizing Windows references in the context of a Linux-specific guide unless strictly necessary for context.
Sap
Get started with manual deployment of automation framework
...blob/main/articles/sap/automation/manual-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform, using Bash and Azure CLI examples suitable for Linux/macOS and Azure Cloud Shell. However, there is minor Windows bias in the SSH client instructions, where PuTTY (a Windows tool) is mentioned as the example SSH client and the need to convert keys to .ppk format is described before any mention of Linux/macOS SSH clients. There are no PowerShell examples, and most commands are Bash/Azure CLI, but the SSH client guidance could be more inclusive.
Recommendations
- When describing SSH client usage, mention both Windows (PuTTY) and Linux/macOS (native ssh) clients equally, or provide instructions for both.
- Include a note that Linux/macOS users can use the built-in ssh command with the provided key files, and do not need to convert to .ppk format.
- If providing conversion instructions, offer both PuTTYgen (Windows) and ssh-keygen (Linux/macOS) methods.
- Consider listing cross-platform SSH client options before mentioning Windows-specific tools.
Sap
Configure the automation framework for new and existing deployments
...s/blob/main/articles/sap/automation/new-vs-existing.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all major deployment steps, ensuring functional parity. However, PowerShell examples are consistently shown after Bash, and some PowerShell-specific modules (e.g., SAPDeploymentUtilities.psd1) are referenced without noting Linux/macOS equivalents or alternatives. There is a slight Windows-first bias in the naming conventions (e.g., backslashes in PowerShell paths) and in the mention of SQL Server on Windows in one scenario, but overall, Linux users can follow the instructions without major friction.
Recommendations
- Explicitly state that both Bash and PowerShell workflows are supported on their respective platforms.
- Clarify any platform-specific requirements for PowerShell modules (e.g., SAPDeploymentUtilities.psd1) and provide guidance for Linux/macOS users if available.
- Where possible, provide notes on cross-platform compatibility for scripts and modules.
- Ensure that any references to Windows-specific technologies (e.g., SQL Server on Windows) are contextual and do not imply that the entire workflow is Windows-only.
Sap
Tutorial: Deploy SAP Deployment Automation Framework
...ure-docs/blob/main/articles/sap/automation/tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides some instructions and examples that prioritize Windows tooling and patterns, such as saving SSH keys in Windows file paths (e.g., C:\Users\<your-username>\.ssh), mentioning Notepad++ and Visual Studio Code as editors, and referencing PuTTY and PuTTYGen for SSH key conversion. These Windows-centric instructions are presented before or instead of Linux/macOS equivalents, despite the overall workflow being cross-platform and primarily Bash/Ansible/Terraform-based.
Recommendations
- Add explicit instructions and file paths for Linux and macOS users when saving SSH keys (e.g., ~/.ssh).
- Mention Linux/macOS editors (such as nano, vi, or gedit) alongside Notepad++ and Visual Studio Code.
- Provide guidance for SSH key conversion on Linux/macOS (e.g., using ssh-keygen or OpenSSH tools) in addition to PuTTY/PuTTYGen.
- Ensure that examples and troubleshooting steps do not assume a Windows environment unless necessary.
- Where tools are referenced (e.g., Visual Studio Code), clarify that they are available cross-platform, or suggest alternatives.
Sap
Soft stop individual SAP instances and HANA database
...enter-sap-solutions/soft-stop-sap-and-hana-database.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure PowerShell, CLI, and REST API interfaces to soft stop SAP systems and HANA databases. PowerShell examples are consistently presented first, which may suggest a Windows-centric workflow. However, Azure CLI and REST API examples are also provided, which are cross-platform and usable on Linux/macOS. No Linux-specific tools or shell examples are given, and there is no explicit mention of Linux/macOS usage patterns.
Recommendations
- Alternate the order of examples, sometimes showing CLI first to avoid implicit prioritization of Windows/PowerShell.
- Explicitly state that Azure CLI and REST API are fully supported on Linux/macOS, and provide links or notes for installing and using these tools on non-Windows platforms.
- Consider adding a short section or note for Linux/macOS users, confirming parity and pointing to platform-specific installation guides for Azure CLI.
- If relevant, mention any SAP/Linux-specific commands or integration points for advanced users.
Sap
SAP Business One on Azure Virtual Machines | Microsoft Docs
...blob/main/articles/sap/workloads/business-one-azure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally aims to support both Windows and Linux deployments for SAP Business One on Azure VMs, referencing both platforms in prerequisites and infrastructure sections. However, there is a mild Windows bias: Windows/PowerShell examples and links are often listed before Linux/CLI equivalents, and some sections (e.g., client VM sizing) reference Windows VM sizes without mentioning Linux VM sizes. There are no explicit Linux configuration examples or references to Linux-specific VM sizing, and the guidance for client/server components is Windows-centric.
Recommendations
- Ensure that examples and links for Linux (Azure CLI, Linux VM sizes) are presented alongside or before Windows/PowerShell equivalents.
- Add explicit references to Linux VM sizing documentation (e.g., link to 'Sizes for Linux virtual machines in Azure').
- Include Linux-specific deployment/configuration examples where relevant, especially for SAP HANA scenarios.
- Clarify when guidance applies equally to both Windows and Linux, or note any differences.
Sap
Considerations for Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
...blob/main/articles/sap/workloads/dbms-guide-general.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, providing recommendations and examples for both platforms. However, in some sections, Windows tools (e.g., Storage Spaces) are mentioned before their Linux equivalents (MDADM, LVM), and Windows examples are presented first in side-by-side comparisons. This ordering may subtly prioritize Windows, but Linux guidance is present and clear.
Recommendations
- Alternate the order of Windows and Linux examples in side-by-side sections, or present both simultaneously without implied priority.
- Explicitly state that both Windows and Linux are equally supported and provide links to Linux documentation with the same prominence as Windows links.
- Where Windows-specific tools are mentioned, ensure Linux equivalents are described with equal detail and clarity.
- Consider adding introductory statements in relevant sections to reinforce platform neutrality.
Sap
IBM Db2 Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
...ocs/blob/main/articles/sap/workloads/dbms-guide-ibm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation covers IBM Db2 deployment for SAP workloads on Azure VMs, supporting both Linux and Windows. While Linux is well-represented (with specific sections, examples, and recommendations), there are a few instances of Windows bias: Windows tools (Storage Pools) are described before Linux equivalents (LVM/mdadm), and the Windows command-line tool (New-StoragePool) is referenced with no Linux command-line example. In some sections, Windows-specific recommendations (e.g., Accelerated Networking) are mentioned before Linux, though both are covered. Overall, Linux parity is strong, but minor ordering and tooling bias exists.
Recommendations
- When mentioning Windows tools (e.g., Storage Pools), immediately follow with Linux equivalents (LVM, mdadm), and provide example Linux commands for parity.
- Where possible, alternate the order of Windows and Linux instructions/examples so Linux is not always second.
- Add explicit Linux command-line examples for disk setup (e.g., creating LVM or mdadm arrays) to match the detail given for Windows Storage Pools.
- Ensure recommendations for features like Accelerated Networking are presented for both OSes in parallel, not Windows-first.
Sap
SAP ASE Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
.../blob/main/articles/sap/workloads/dbms-guide-sapase.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Minor Windows Firewall Note
Summary
The documentation provides parity for both Windows and Linux deployments of SAP ASE on Azure, with configuration tables and recommendations for each OS. Both Windows and Linux tools (Storage Spaces, LVM2, NTFS, XFS) are mentioned side-by-side. However, in some sections, Windows tools (Storage Spaces, NTFS) are listed before their Linux equivalents, and there are a few notes specific to Windows Firewall configuration without equivalent Linux firewall guidance. The page does not show exclusive bias; Linux is well represented throughout.
Recommendations
- When mentioning disk aggregation and file systems, alternate the order between Windows and Linux tools to avoid implicit prioritization.
- Add a brief note about Linux firewall configuration (e.g., using firewalld or iptables) when discussing network security group rules, for parity with the Windows Firewall mention.
- Ensure that any OS-specific instructions (such as 'Lock Pages in Memory' for Windows) are matched with Linux equivalents or an explicit note if not applicable.
- Continue to provide configuration tables for both OSes, as done here.
Sap
Azure Virtual Machines deployment for SAP NetWeaver | Microsoft Docs
...s/blob/main/articles/sap/workloads/deployment-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is generally balanced and covers both Windows and Linux deployment scenarios for SAP NetWeaver on Azure VMs. However, there is a mild Windows bias: Windows/PowerShell tools are mentioned first in several places, and some instructions (such as local computer prerequisites) prioritize Windows environments. PowerShell is referenced as a primary automation tool, with Azure CLI for Linux mentioned as an alternative. Windows-specific tools and patterns (such as sysprep and Group Policy) are described in detail before their Linux equivalents. Linux instructions are present and technically complete, but are sometimes secondary in order or detail.
Recommendations
- In the prerequisites section, clarify that Linux users can use Azure CLI and the Azure portal from Linux or macOS, and update the local computer requirements to reflect cross-platform support.
- When listing tools or automation options, present Azure CLI and PowerShell together, or mention Azure CLI first when describing Linux scenarios.
- Ensure Linux examples and instructions are given equal prominence and detail as Windows examples, especially in sections describing deployment, proxy configuration, and VM agent installation.
- Where possible, provide explicit Linux/macOS command-line examples for tasks currently described only for Windows/PowerShell.
- Review the order of presentation in mixed OS sections to alternate or balance Windows and Linux instructions.
Sap
Implement SAP BW NLS with SAP IQ on Azure | Microsoft Docs
...s/blob/main/articles/sap/workloads/dbms-guide-sapiq.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides parity between Windows and Linux for SAP IQ NLS deployment on Azure, with dedicated sections for each OS. However, there is a mild Windows bias: Windows deployment instructions and examples are presented before Linux equivalents, and Windows-specific clustering tools (WSFC) are described in detail before mentioning Linux alternatives (Pacemaker). Storage options are clearly split by OS, but Windows tools and terminology (e.g., UNC paths, WSFC) are introduced first and with more detail.
Recommendations
- Alternate the order of Windows and Linux sections or present them side-by-side to avoid implicit prioritization.
- Ensure Linux-specific tools (e.g., Pacemaker) are described with equal detail and clarity as Windows tools (WSFC).
- Provide explicit Linux examples for file paths, backup commands, and automation scripts where Windows-specific examples (e.g., UNC path) are given.
- Where possible, use neutral language and parallel structure for both OSes to reinforce parity.
Sap
Disaster Recovery recommendation for SAP workload
.../articles/sap/workloads/disaster-recovery-sap-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides guidance for both Linux and Windows SAP workloads, with parallel sections for each OS. However, there is a mild Windows bias: Windows examples and terminology (such as WSFC, SMB, Robocopy) are presented with equal or slightly more detail, and Windows terminology (WSFC, cloud witness, Robocopy) is used without always providing Linux equivalents first or in parallel. In the backup section, Windows-centric tools (Robocopy) are mentioned for SMB replication before Linux alternatives (rsync for NFS) are referenced. The order of presentation sometimes puts Windows before Linux, and Windows tools are referenced by name, while Linux equivalents are described more generically.
Recommendations
- Ensure Linux and Windows examples/tools are presented in parallel, with equal detail and clarity.
- When referencing Windows tools (e.g., Robocopy), provide Linux equivalents (e.g., rsync) in the same context, not just in separate tables.
- Avoid presenting Windows terminology or examples before Linux unless there is a technical reason.
- Add explicit Linux command-line examples (e.g., rsync invocation for NFS replication) where Windows commands (Robocopy) are shown.
- Clarify cross-platform applicability in each section, especially for backup and storage replication.
Sap
Exchange Online Integration for Email-Outbound from SAP NetWeaver | Microsoft Docs
...oads/exchange-online-integration-sap-email-outbound.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by exclusively referencing Microsoft 365 Admin Center, Exchange Admin Center, and PowerShell for configuration steps, without mentioning or providing Linux/macOS alternatives for managing Exchange Online settings. All screenshots and step-by-step instructions are tailored to the Microsoft 365 web portals and PowerShell, which are most commonly used on Windows. There is no mention of Linux-based tools or CLI alternatives for managing Exchange Online, nor guidance for SAP administrators who may be operating on Linux-based SAP servers.
Recommendations
- Add notes or links for Linux/macOS users on how to access Exchange Online management tools, such as using Exchange Online PowerShell from non-Windows platforms (e.g., via PowerShell Core or Azure Cloud Shell).
- Clarify that the SAP application server can be Linux-based and provide any relevant caveats or steps for Linux environments (e.g., telnet/ping commands, SMTP configuration specifics).
- Where possible, include cross-platform instructions for administrative tasks (such as enabling SMTP AUTH) that can be performed via browser-based portals or PowerShell Core on Linux/macOS.
- Explicitly state that the SAP Connect (SCOT) configuration steps are OS-agnostic, and highlight any OS-specific considerations for SAP administrators.
Sap
Plan and implement an SAP deployment on Azure
...ocs/blob/main/articles/sap/workloads/planning-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains good cross-platform coverage, with a clear focus on both Linux and Windows SAP deployments. However, there are a few areas where Windows tools (such as PowerShell) are referenced first or exclusively, and some examples or links for finding VM images use PowerShell before CLI. In addition, some migration tooling and scripting references point to PowerShell samples, which may create friction for Linux users. Overall, Linux is well-represented, but minor Windows-first patterns exist.
Recommendations
- Where PowerShell is referenced for Azure tasks (e.g., finding VM images, migration scripts), provide equivalent Azure CLI or Bash examples alongside.
- When linking to sample scripts or migration utilities, ensure Linux/Bash/CLI alternatives are highlighted or included if available.
- In sections listing both Linux and Windows options, alternate the order or explicitly state parity to avoid subtle Windows-first impressions.
- Review referenced blog posts and open-source projects to ensure Linux users are not left without guidance or equivalents.