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 401-425 of 639 flagged pages
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-shared-disk.md
...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 focused on Windows environments, specifically Windows Server Failover Clustering (WSFC) and related tooling. All examples, scripts, and procedures are Windows-centric, with exclusive use of PowerShell and Windows-specific clustering and storage solutions (e.g., SIOS DataKeeper, DNS Manager, Windows Firewall). There are no Linux equivalents, nor any mention of Linux-based clustering solutions or commands.
Recommendations
- Add a parallel section or separate article for SAP ASCS/SCS multi-SID HA on Linux, using Pacemaker/Corosync and native Linux tools.
- Provide equivalent Linux command-line examples (e.g., using Azure CLI, shell scripts) for infrastructure preparation, load balancer configuration, and cluster setup.
- Reference Linux-based SAP HA guides and link to SAP documentation for Linux clustering.
- Clarify early in the article that the procedure is Windows-only, and direct Linux users to appropriate resources.
- Include a comparison table of Windows and Linux HA approaches for SAP on Azure to help users choose the right path.
Create Pull Request
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-hana-availability-one-region.md
...cles/sap/workloads/sap-hana-availability-one-region.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. References to Windows-specific documentation (e.g., availability sets) are given before or instead of Linux equivalents, and links often point to Windows tutorials. There is a lack of explicit Linux command-line or configuration examples, despite the content being relevant for Linux-based SAP HANA deployments. While Linux is mentioned, especially in the context of high availability clusters, practical Linux setup steps or scripts are missing, and Windows patterns/tools are referenced more prominently.
Recommendations
- Provide direct links to Linux-specific documentation for Azure features (e.g., availability sets, VM sizes) alongside or before Windows links.
- Include Linux command-line examples (e.g., bash, systemctl, sysctl) for relevant configuration steps, such as enabling kernel panic auto-reboot.
- Balance references to Windows and Linux tools/patterns, ensuring that Linux equivalents are always mentioned and linked where appropriate.
- Add step-by-step Linux setup guides or code snippets for common tasks (e.g., configuring HANA auto-restart, setting up Pacemaker clusters).
- Review and update all references to ensure Linux parity, especially in introductory sections and diagrams.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-file-share.md
...sap/workloads/sap-ascs-ha-multi-sid-wsfc-file-share.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows, specifically Windows Server Failover Clustering (WSFC) and Scale-Out File Server (SOFS) on Azure. All examples, scripts, and screenshots are for Windows environments, with extensive use of PowerShell and Windows-native tools. There are no Linux equivalents, alternative approaches, or even references to Linux-based high availability solutions for SAP ASCS/SCS multi-SID scenarios. The documentation assumes a Windows-only context throughout.
Recommendations
- Add a section or parallel documentation for configuring SAP ASCS/SCS multi-SID high availability on Linux, using Pacemaker/Corosync or other supported Linux clustering solutions.
- Provide Linux shell script examples for file share and permission setup, analogous to the PowerShell scripts shown for Windows.
- Include diagrams and screenshots for Linux-based clusters, not just Windows Failover Cluster Manager.
- Reference Linux-specific Azure resources (e.g., NFS on Azure Files, Linux VM clustering guides) where appropriate.
- Clarify in the introduction that the guide is Windows-specific, and link to Linux-focused documentation if available.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-wsfc-file-share.md
...rkloads/sap-high-availability-guide-wsfc-file-share.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows Server Failover Clustering (WSFC) and related Windows technologies (e.g., SMB file shares, Storage Spaces Direct, SOFS, ReFS, Windows-specific clustering patterns). There are no Linux or cross-platform examples, tools, or alternative approaches mentioned. All architectural diagrams, terminology, and prerequisites are Windows-centric, and there is no discussion of Linux-based clustering solutions for SAP ASCS/SCS in Azure.
Recommendations
- Add a section or references for clustering SAP ASCS/SCS on Linux in Azure, such as using SUSE High Availability Extension (HAE) or Red Hat Pacemaker clusters.
- Provide comparative architecture diagrams and workflows for Linux-based SAP high availability setups in Azure.
- Include Linux-specific prerequisites, supported file sharing technologies (e.g., NFS, OCFS2, GFS2), and configuration steps.
- Reference or link to Linux-focused SAP high availability documentation in Azure, if available.
- Clearly indicate in the introduction that this guide is Windows-specific and provide links to equivalent Linux documentation for parity.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap.md
...ob/main/articles/sap/workloads/vm-extension-for-sap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets and Azure PowerShell before Azure CLI, mentioning Windows-specific SAP Host Agent requirements before Linux, and not providing explicit Linux command-line examples or Linux-native tooling. While both Linux and Windows are mentioned in prerequisites and supported OS lists, actionable examples and tool references are Windows-centric.
Recommendations
- Provide explicit Linux shell (bash) command examples alongside or before PowerShell examples.
- Reference Azure CLI as the primary cross-platform tool, with PowerShell as an alternative, to reflect Linux parity.
- Mention Linux prerequisites and SAP Host Agent requirements before or alongside Windows equivalents, not after.
- Include Linux-native troubleshooting steps or commands where relevant.
- Ensure all instructions and examples are validated for both Windows and Linux environments, and clarify any OS-specific differences.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-architecture-scenarios.md
...kloads/sap-high-availability-architecture-scenarios.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 and clustering solutions (such as WSFC) are often mentioned first or in more detail, and the overall structure and terminology sometimes prioritize Windows patterns. There are sections where only Windows examples are given before Linux equivalents, and some advanced features (like multi-SID clustering) are described in more detail for Windows. The document also references Windows-specific technologies (e.g., SMB, WSFC) and sometimes omits equivalent Linux command-line or tool examples.
Recommendations
- Ensure Linux and Windows solutions are presented in parallel, with equal detail and prominence.
- When discussing high-availability clustering, introduce Linux (Pacemaker, NFS, etc.) and Windows (WSFC, SMB, etc.) options together, rather than leading with Windows.
- Provide Linux-specific examples and command-line snippets (e.g., Pacemaker configuration, systemctl commands) where Windows/PowerShell examples are given.
- Expand Linux multi-SID clustering documentation to match the depth and clarity of the Windows section.
- Avoid using Windows-centric terminology as the default (e.g., 'file share' without clarifying SMB vs NFS).
- Review all tables and lists to ensure Linux options are not omitted or relegated to secondary status.
- Add links to Linux-specific guides and best practices wherever Windows links are provided.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-file-share.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-file-share.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All examples, scripts, and procedures are specific to Windows Server Failover Clustering, Scale-Out File Server, and PowerShell. There are no Linux equivalents, nor is there any mention of Linux-based clustering or file sharing solutions. Windows tools and patterns are referenced exclusively, with no cross-platform guidance.
Recommendations
- Provide equivalent instructions for Linux-based SAP high availability setups, such as using Pacemaker/Corosync clusters and NFS file shares.
- Include Linux shell script examples alongside PowerShell scripts for all relevant steps.
- Reference Linux-native tools (e.g., crm, pcs, systemd, NFS) where appropriate.
- Add a section or links to documentation for SAP NetWeaver high availability on Linux clusters in Azure.
- Clarify in the introduction that this guide is Windows-specific, and direct Linux users to appropriate resources.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-guide-wsfc-shared-disk.md
...kloads/sap-high-availability-guide-wsfc-shared-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is exclusively focused on Windows Server Failover Clustering (WSFC) for clustering SAP ASCS/SCS instances in Azure, with no mention of Linux-based clustering solutions, tools, or examples. All technical details, diagrams, and recommendations are specific to Windows, and Windows-specific tools (such as WSFC, SIOS DataKeeper, Windows Scale-Out File Server, and Windows Server versions) are referenced throughout. There are no Linux equivalents, nor is there any guidance for users running SAP on Linux in Azure.
Recommendations
- Add a parallel section or a separate documentation page covering SAP ASCS/SCS high availability clustering on Linux in Azure, using solutions such as Pacemaker/Corosync.
- Include Linux-specific prerequisites, supported distributions, and Azure-specific configuration steps for Linux clusters.
- Provide Linux command-line examples (e.g., using shell scripts or systemd) alongside or after Windows/Powershell examples.
- Reference Linux-native tools and patterns (such as NFS for shared storage, or Linux-based fencing mechanisms) where appropriate.
- Clearly indicate in the introduction that the page is Windows-specific, and link to Linux-focused documentation for parity.
- Ensure diagrams and architecture discussions include Linux-based scenarios where possible.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-file-share.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows-based high availability for SAP on Azure, specifically using Windows Server Failover Clustering (WSFC) and Microsoft Scale-Out File Server. All examples, instructions, and code samples are for Windows environments, with exclusive use of PowerShell and Windows-specific tools. There is no mention of Linux-based high availability solutions, nor are any Linux commands, tools, or deployment patterns provided.
Recommendations
- Add equivalent guidance for deploying SAP high availability on Linux, such as using Pacemaker/Corosync clusters and NFS for file sharing.
- Provide Linux-based command-line examples (e.g., Bash scripts, systemctl commands) alongside PowerShell examples.
- Reference Azure Resource Manager templates or automation scripts for Linux-based SAP HA deployments.
- Include a section comparing Windows and Linux HA approaches for SAP on Azure, with links to relevant documentation for both platforms.
- Clarify in the introduction that this guide is Windows-specific, and provide links to Linux-focused documentation for SAP HA on Azure.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically Windows Server Failover Clustering (WSFC) for SAP ASCS/SCS high availability on Azure. All examples, instructions, and tooling references are for Windows (e.g., PowerShell, Windows registry, Windows Failover Cluster Manager, SIOS DataKeeper for Windows). There are no Linux equivalents, nor is there any mention of how to achieve similar SAP HA setups on Linux-based systems. The documentation assumes a Windows-only context throughout.
Recommendations
- Add a section or parallel documentation for configuring SAP ASCS/SCS high availability on Azure using Linux-based clusters (e.g., Pacemaker, Corosync, or SUSE HAE).
- Provide Linux command-line examples (e.g., using Azure CLI, shell scripts) for VM provisioning, disk attachment, and cluster setup.
- Discuss Linux-supported shared disk solutions (e.g., Azure Shared Disks with Linux, NFS, or other supported storage options for Linux clusters).
- Reference Linux-specific SAP HA guides and best practices, ensuring Linux administrators have a clear migration or deployment path.
- Clearly indicate in the introduction that the guide is Windows-specific, and link to Linux documentation if available.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-higher-availability-architecture-scenarios.md
...oads/sap-higher-availability-architecture-scenarios.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific tools and patterns, such as Windows Server Failover Clustering (WSFC), are mentioned before their Linux equivalents (Pacemaker), and the overall structure and references (including linked guides and images) are heavily focused on Windows environments. There is a lack of concrete Linux-specific examples or detailed parity in instructions, and the documentation references Windows services and clustering tools extensively, with only brief mentions of Linux support and limitations.
Recommendations
- Provide Linux-specific examples and step-by-step instructions equivalent to those given for Windows, especially for high availability configurations.
- Mention Linux tools (e.g., Pacemaker) alongside Windows tools, and give them equal prominence in both text and diagrams.
- Include Linux screenshots, diagrams, and references in parallel with Windows-focused ones.
- Clarify which features and recommendations apply to Linux, and specify supported distributions and versions.
- Link to Linux-specific SAP and Azure documentation where available, and ensure Linux users have clear guidance for all major scenarios.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-shared-disk.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/sap-high-availability-installation-wsfc-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, specifically Windows Server Failover Clustering, and provides only Windows-specific instructions and examples. All operational steps, scripts, and tooling references (such as PowerShell, Windows DNS Manager, Windows Firewall, and Failover Cluster Manager) are exclusive to Windows. There are no Linux equivalents, examples, or even mentions of how to achieve similar SAP NetWeaver HA setups on Linux platforms. The only Linux reference is a link in the references section, but the main content is entirely Windows-centric.
Recommendations
- Add a section or parallel guide for installing SAP NetWeaver HA on Linux clusters (e.g., using SUSE or Red Hat with Pacemaker/Corosync).
- Provide Linux-specific examples for DNS configuration, firewall rules (e.g., using firewalld or iptables), and cluster management (e.g., crmsh or pcs commands).
- Include sample scripts or command lines for Linux environments where PowerShell is used for Windows.
- Reference and link to Linux HA documentation more prominently, not just in the references but in the main flow.
- Clearly state in the introduction that this guide is Windows-specific, and direct Linux users to the appropriate documentation.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/supported-product-on-azure.md
...n/articles/sap/workloads/supported-product-on-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows is consistently listed first when enumerating supported operating systems, and certain features (such as non-Unicode SAP systems) are described as only supported on Windows, with little explanation or parity for Linux. In the Oracle DBMS section, Windows is emphasized as a primary guest OS, and the documentation references SQL Server (a Windows-centric DBMS) before mentioning Linux-based alternatives. There are no command-line or configuration examples, but the narrative and ordering suggest a Windows-first perspective. Linux is supported, but not given equal prominence or detailed guidance.
Recommendations
- Alternate the order of operating system mentions (e.g., sometimes list Linux first) to avoid reinforcing a Windows-first mindset.
- Provide explicit Linux-focused guidance and examples where Windows-specific features or limitations are discussed.
- Where features are Windows-only (e.g., non-Unicode SAP systems), clearly explain the technical reasons and offer migration or workaround advice for Linux users.
- Include references to Linux-native tools and patterns (e.g., systemd, Linux file paths) where relevant.
- Ensure that all sections discussing supported platforms or configurations give equal detail and prominence to both Windows and Linux options.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/universal-print-sap-frontend.md
...articles/sap/workloads/universal-print-sap-frontend.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by only referencing Windows client OS and showing Windows-specific UI (e.g., Windows 11 settings dialog) when describing how to add and use Universal Print printers. There are no examples or instructions for Linux clients, despite the service being listed as relevant for both Linux and Windows virtual machines. The prerequisites and workflow assume a Windows environment, and there is no mention of Linux printing tools or how Universal Print could be accessed from Linux desktops.
Recommendations
- Include explicit instructions and screenshots for adding and using Universal Print printers on Linux client systems (e.g., using CUPS or other Linux printing subsystems).
- Mention and provide examples for Linux printing workflows, such as how to configure SAP GUI or browser-based SAP access on Linux to use Universal Print.
- Clarify whether Universal Print is supported on Linux clients, and if there are limitations or alternative approaches, document them.
- Ensure that all UI examples (such as printer selection dialogs) are shown for both Windows and Linux environments, or at least describe the Linux equivalent.
- List Linux alongside Windows in all prerequisite and setup steps, not just in the service metadata.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/virtual-machine-scale-set-sap-faq.md
...les/sap/workloads/virtual-machine-scale-set-sap-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell as the method for configuring Azure Site Recovery for VMs in scale sets, and by highlighting PowerShell-based open-source migration scripts. No Linux CLI (az CLI, Bash) or cross-platform tooling examples are provided, and Linux-native workflows are not mentioned.
Recommendations
- Provide equivalent Azure CLI (az CLI) or Bash script examples alongside PowerShell instructions, especially for critical tasks such as configuring Azure Site Recovery and migration.
- Reference or develop open-source migration scripts that support Linux environments, not just PowerShell.
- Explicitly mention cross-platform or Linux-compatible tools and workflows where possible.
- Add notes or links to documentation for Linux users, ensuring parity in guidance and tooling.
- Where only PowerShell is currently supported, clarify this limitation and provide a roadmap or alternatives for Linux users.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap-new.md
...ain/articles/sap/workloads/vm-extension-for-sap-new.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/PowerShell examples and references are often presented first or exclusively, especially in sections about configuring managed identities. Many links and instructions default to Windows VM scenarios, and PowerShell is emphasized throughout. Linux is supported and included in most code examples, but parity is not always maintained in linked resources or step-by-step instructions.
Recommendations
- Ensure that all linked guides (e.g., for configuring managed identities) include Linux VM versions and are referenced alongside or before Windows equivalents.
- When listing multiple examples (e.g., PowerShell, CLI, Terraform), alternate the order or present Linux and Windows examples together to avoid always leading with Windows.
- Expand step-by-step instructions and troubleshooting sections to provide Linux-specific guidance where only Windows is currently detailed.
- Review all referenced articles and ensure Linux parity in external links, not just in code blocks.
- Where PowerShell is mentioned, clarify if/when Bash or other Linux-native tools can be used, and provide those alternatives.
- In the 'Next steps' and reference sections, include links to Linux-specific command references and guides, not just PowerShell/Windows.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/vm-extension-for-sap-standard.md
...rticles/sap/workloads/vm-extension-for-sap-standard.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows/PowerShell examples and tools are consistently presented before Linux/Azure CLI equivalents, and certain troubleshooting and configuration workflows are described in more detail for Windows. PowerShell cmdlets and Windows-specific tools (such as azperflib.exe and Windows services) are emphasized, sometimes with more context or screenshots than their Linux counterparts. While Linux/Azure CLI instructions are present and reasonably complete, the ordering and depth of Windows content suggest a Windows-first approach.
Recommendations
- Present Linux and Windows instructions in parallel or in a consistent order (e.g., always Linux first if targeting Linux VMs, or interleave both).
- Ensure that Linux/Azure CLI examples are as detailed as Windows/PowerShell examples, including equivalent screenshots, output samples, and troubleshooting steps.
- Where Windows-specific tools (e.g., azperflib.exe) are mentioned, provide clear Linux equivalents or explicitly state if there is no direct counterpart.
- Avoid referring to PowerShell cmdlets as the default or primary method; instead, phrase instructions to treat PowerShell and Azure CLI as equal alternatives.
- Review troubleshooting and error resolution sections to ensure Linux guidance is as comprehensive as Windows guidance.
- If a section is only relevant to one OS, clearly label it as such and provide a corresponding section for the other OS where possible.
Sap
Exchange Online Integration for Email-Outbound from SAP ABAP Platform | Microsoft Docs
...oads/exchange-online-integration-sap-email-outbound.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only automation example provided for configuring Entra ID and Exchange Online, and Exchange Admin Center/Cloud Shell instructions are Windows-centric. Linux alternatives for scripting or CLI-based configuration are not mentioned, and PowerShell is referenced as a prerequisite for automation. Additionally, Windows/PowerShell tools are mentioned before any generic or cross-platform alternatives, and Linux-specific guidance is missing for key steps.
Recommendations
- Provide equivalent automation examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or Bash scripts for Linux/macOS users.
- Clarify whether PowerShell 7.x is required or if the steps can be performed using Azure CLI or REST API calls, which are available on Linux/macOS.
- Include notes or links to Linux/macOS-compatible methods for accessing Exchange Online and Entra ID (e.g., using browser-based portals, Azure CLI, or Graph API).
- Explicitly state which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
- Add a brief section or callout for Linux/macOS users, outlining any differences or additional steps needed.
Sap
Configure Azure DevOps Services for SAP Deployment Automation Framework
.../blob/main/articles/sap/automation/configure-devops.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias in its automation setup instructions. The primary configuration scripts for Azure DevOps Services and SAP Deployment Automation Framework are provided exclusively in PowerShell, with explicit instructions to use PowerShell ISE, and no equivalent Bash or Linux shell examples are given for these critical steps. Linux/macOS users are only accommodated in a few sections (e.g., app registration and web app URL update), and these appear after the Windows instructions. The lack of Linux/macOS parity in the initial and main automation steps creates friction for non-Windows users.
Recommendations
- Provide equivalent Bash or shell scripts for the main Azure DevOps and SAP Deployment Automation Framework setup steps, or clarify if the SDAFUtilities module and related scripts are cross-platform (PowerShell Core).
- Explicitly document any prerequisites or limitations for running the provided PowerShell scripts on Linux/macOS (e.g., PowerShell Core compatibility, required modules).
- Where possible, use cross-platform tools (e.g., Azure CLI, Bash) for automation examples, or offer both PowerShell and Bash alternatives.
- Ensure Linux/macOS instructions are presented alongside Windows instructions, not only in isolated sections.
- Add notes or links for Linux/macOS users on how to adapt or run the scripts in their environment.
Sap
Configure SAP parameters files for Ansible
...in/articles/sap/automation/configure-sap-parameters.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides both cross-platform and Windows-specific SAP parameter configuration details for Ansible. However, Windows parameters and support are given dedicated sections and examples (e.g., SQL Server, Windows domain, cluster types) while Linux-specific configuration (such as user/group IDs, NFS, disk layout) is present but not explicitly labeled as 'Linux support'. Windows-specific options (domain, cluster, SQL Server) are described in detail, but equivalent Linux clustering or domain integration options are not discussed. No PowerShell examples are present, but Windows parameters are called out separately and sometimes appear before Linux equivalents.
Recommendations
- Add a dedicated 'Linux support' section to parallel the 'Windows support' section, describing Linux-specific configuration options (e.g., clustering, domain integration, NFS specifics).
- Explicitly label tables and examples that pertain to Linux/UNIX platforms, not just Windows.
- Provide examples for Linux-specific scenarios, such as configuring Linux clusters, joining Linux systems to a domain (if supported), or using Linux-native tools.
- Ensure that Linux and Windows configuration options are presented with equal prominence and detail.
- Where possible, present Linux examples before or alongside Windows examples, rather than after.
Sap
Get started with SAP Deployment Automation Framework
...-docs/blob/main/articles/sap/automation/get-started.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page for SAP Deployment Automation Framework shows a notable Windows bias. Many critical automation steps, especially those involving Azure DevOps setup and application registration, are provided only as PowerShell scripts, with instructions to use PowerShell ISE. There are no equivalent bash or Linux shell examples for these sections, and Windows/PowerShell patterns are presented first or exclusively. Linux/macOS users are left to infer how to adapt these steps, creating friction and potential confusion.
Recommendations
- Provide bash or shell script equivalents for all PowerShell-only instructions, especially for application registration and Azure DevOps setup.
- Include explicit instructions and examples for Linux/macOS environments, not just Windows.
- Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the default; suggest cross-platform alternatives (e.g., VS Code, terminal).
- Clearly indicate which scripts are cross-platform and which require adaptation, and provide guidance for Linux/macOS users.
- Where PowerShell scripts are used, note how to run them on Linux/macOS (e.g., via PowerShell Core) or provide alternative approaches.
Sap
Plan your SAP deployment with the automation framework on Azure
...s/blob/main/articles/sap/automation/plan-deployment.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides a generally cross-platform overview of SAP deployment automation on Azure, with a clear emphasis on Linux-based deployments for the control plane and workload zones. However, there are notable sections where Windows-specific tools and patterns are presented first or exclusively, such as the PowerShell script for testing connectivity (even on Linux VMs), and detailed credential management for Windows-based deployments (Active Directory integration, Windows service accounts). The firewall configuration table lists Windows components and PowerShell Gallery endpoints, but does not provide equivalent Linux/macOS tooling guidance. The PowerShell script example is given for both Unix and Windows platforms, but only as a PowerShell script, not as a Bash or native Linux shell alternative.
Recommendations
- Provide equivalent Bash or shell script examples for connectivity testing on Linux VMs, rather than only PowerShell.
- When listing firewall requirements, include Linux/macOS package sources and installation endpoints (e.g., apt, yum, Homebrew) alongside Windows/PowerShell Gallery endpoints.
- In sections about credential management and deployment, clarify which steps are Windows-specific and provide parallel guidance for Linux-based deployments where applicable.
- Ensure that Linux tools and patterns (e.g., SSH, Bash scripting) are mentioned with equal prominence and, where possible, before Windows equivalents in cross-platform sections.
Sap
Customer enabled disaster recovery in Azure Center for SAP Solutions
...n/articles/sap/center-sap-solutions/compliance-cedr.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for critical disaster recovery operations, with no equivalent Azure CLI or Linux/macOS shell examples. References to 'PowerShell or CLI' are made, but only PowerShell commands are shown, and no explicit Linux-friendly instructions are provided. This creates friction for Linux/macOS administrators managing SAP workloads on Azure.
Recommendations
- Add Azure CLI examples alongside PowerShell for all registration and failover steps.
- Explicitly mention platform-agnostic tools and clarify which commands work on Linux/macOS.
- Provide guidance or links for running Azure CLI on Linux/macOS, especially for SAP administrators likely to use those platforms.
- Ensure that any referenced scripts or tools are available and documented for both Windows and Linux environments.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell-only example for listing Azure VM images, without equivalent Azure CLI or Bash examples. The only code sample is in PowerShell, which is a Windows-centric tool. While the rest of the documentation is platform-neutral and focused on Linux OS images for SAP, the example may create friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
- Add equivalent Azure CLI and/or Bash examples alongside the PowerShell command for listing VM images.
- Wherever code samples are provided, ensure both Windows (PowerShell) and Linux/macOS (CLI/Bash) options are shown.
- Explicitly mention that users can use Azure CLI on Linux/macOS for all deployment steps, and link to relevant CLI documentation.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides examples and instructions for both Windows and Linux SAP systems, but there is a noticeable Windows bias. Windows-specific requirements (such as outbound connectivity to www.microsoft.com for PowerShell script signature validation) are described in detail, and PowerShell is mentioned as a primary automation interface. Some commands and troubleshooting steps are given only for Windows (e.g., checking sapstartsrv status), while Linux equivalents are less emphasized or missing. Windows file paths and tools are often listed before Linux ones, and some troubleshooting links are Windows-centric.
Recommendations
- Ensure all command-line examples are provided for both Windows and Linux, with clear separation and parity.
- When mentioning PowerShell, also highlight Bash/CLI alternatives for Linux users.
- List Linux and Windows file paths and commands side-by-side, or in parallel sections, to avoid Windows-first ordering.
- Provide troubleshooting steps and links for Linux issues with equal detail as Windows.
- Clarify when instructions are OS-specific and avoid implying Windows as the default.