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 26-50 of 639 flagged pages
Sap
Configure SAP system parameters for automation
.../blob/main/articles/sap/automation/configure-system.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in several areas. Windows-specific technologies (such as Windows failover clustering) are mentioned alongside Linux equivalents (Pacemaker), but Windows is often listed first or equally, despite SAP on Azure being predominantly Linux-based. There are references to Windows licensing and clustering, but no PowerShell or Windows command examples are provided. The only command-line examples are Azure CLI, which is cross-platform. However, there is a lack of explicit Linux command examples (e.g., Pacemaker configuration), and Linux high-availability patterns are not described in detail. The documentation does not provide Linux-first guidance or parity in example depth for Linux-specific operations.
Recommendations
- Provide explicit Linux configuration examples, especially for Pacemaker clusters and fencing agent setup.
- List Linux high-availability solutions (Pacemaker) before Windows equivalents (Windows failover clustering) to reflect common SAP deployment patterns.
- Include references or links to Linux-specific documentation for SAP on Azure, such as SUSE or Red Hat guides.
- Expand on Linux licensing options and patterns, matching the detail given for Windows.
- Add sample commands or configuration snippets for Linux-based deployments (e.g., Pacemaker resource configuration, systemd unit files).
Create Pull Request
Sap
Configure Azure DevOps Services for SAP Deployment Automation Framework
.../blob/main/articles/sap/automation/configure-devops.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by providing PowerShell-only scripts for core setup tasks, instructing users to use PowerShell ISE, and referencing Windows-specific tools and patterns before or instead of Linux equivalents. Linux instructions are only present for a few isolated steps (app registration, web app URL update), while the main automation setup and artifact deployment scripts lack Bash or cross-platform alternatives. The documentation also assumes use of Visual Studio Code and other Windows-centric workflows.
Recommendations
- Provide equivalent Bash scripts for all PowerShell automation steps, especially for initial setup and artifact deployment.
- Clearly indicate cross-platform compatibility for all scripts and modules, or provide platform-specific instructions side-by-side.
- Avoid referencing Windows-only tools (e.g., PowerShell ISE) as the default; suggest VS Code or other cross-platform editors.
- Ensure all manual steps (such as repository cloning, agent setup, and variable group creation) have Linux/macOS instructions, not just Windows.
- Review screenshots and UI instructions to ensure they are not Windows-centric, or provide Linux/macOS alternatives where applicable.
Sap
Configure SAP parameters files for Ansible
...in/articles/sap/automation/configure-sap-parameters.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing a dedicated section for Windows parameters and support, listing Windows-specific parameters (such as domain names, cluster types, and SQL Server), and referencing Windows cluster services and load balancer IPs before or in addition to Linux equivalents. There are no explicit Linux-specific configuration examples or sections, and Linux tools or patterns (such as systemd, Linux clustering, or Linux-specific user/group management) are not mentioned. The only example YAML for disks uses Linux-like hostnames, but no Linux configuration instructions or parity for Windows-specific features are provided.
Recommendations
- Add a dedicated section for Linux support, including parameters relevant to Linux deployments (e.g., systemd service configuration, Linux cluster types such as Pacemaker/Corosync, Linux domain integration).
- Provide Linux-specific examples for parameters and override methods, such as using Linux shell commands or configuration files.
- Ensure that Linux tools and patterns are mentioned alongside Windows equivalents, and avoid listing Windows options first unless contextually necessary.
- Clarify which parameters are platform-specific and provide guidance for both Windows and Linux users.
- Include references to Linux documentation and best practices for SAP deployments.
Sap
Workload zone configuration in the automation framework
...ain/articles/sap/automation/configure-workload-zone.md
High Priority
View Details →
Detected Bias Types
Windows First
Default Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows Server is the default image for utility VMs, and SAPGui is suggested to be hosted on these Windows VMs. There is no equivalent example or recommendation for Linux-based utility VMs or SAPGui alternatives. While the VM image structure does show a Linux example (SUSE), it is not presented as the default for utility VMs, and the overall tone and defaults favor Windows tools and patterns.
Recommendations
- Provide explicit Linux-based utility VM examples and defaults alongside Windows Server, including SAPGui alternatives for Linux (e.g., SAPGui for Java).
- Clarify that both Windows and Linux can be used for utility VMs, and offer guidance for Linux-based SAP administration and tooling.
- Wherever defaults are specified (e.g., VM image, SAPGui hosting), present both Windows and Linux options equally, or make the default OS configurable.
- Add documentation sections or notes highlighting cross-platform support and considerations for Linux users.
Sap
Get started with SAP Deployment Automation Framework
...-docs/blob/main/articles/sap/automation/get-started.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by providing multiple PowerShell-based examples and scripts, often without equivalent Bash/Linux alternatives. Windows/PowerShell tooling is referenced first or exclusively in several key automation steps, such as application registration and Azure DevOps setup. Linux instructions are present but less detailed and appear later in the document, with some steps (e.g., Azure DevOps automation) lacking Linux-specific guidance.
Recommendations
- Provide Bash/Linux shell script equivalents for all PowerShell examples, especially for Azure DevOps setup and application registration.
- Ensure that Linux instructions are presented alongside Windows instructions, not only as afterthoughts or in separate sections.
- Explicitly mention cross-platform compatibility for all scripts and tools, and clarify any platform-specific requirements.
- Include troubleshooting notes for common Linux-specific issues (e.g., file permissions, environment variables).
- Where PowerShell is used, offer guidance on using PowerShell Core on Linux, or recommend native Bash alternatives.
Sap
Tutorial: Deploy SAP Deployment Automation Framework
...ure-docs/blob/main/articles/sap/automation/tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. While most deployment and configuration steps use Bash scripts and Azure CLI (which are cross-platform), instructions for connecting to the deployer VM and handling SSH keys are written with Windows-centric file paths (e.g., C:\Users\<your-username>\.ssh) and mention Windows tools (Visual Studio Code, Notepad++, PuTTY) before or instead of Linux-native alternatives. There are no explicit Linux examples for SSH key placement or connection, and the documentation does not mention Linux editors or SSH clients (such as nano, vim, or OpenSSH) in these contexts.
Recommendations
- Add explicit Linux examples for SSH key placement (e.g., ~/.ssh directory) and connection (e.g., using ssh command in terminal).
- Mention Linux-native editors (nano, vim) and SSH clients alongside Windows tools.
- Provide instructions for both Windows and Linux users when referencing file paths and tools.
- Clarify that Visual Studio Code is available on both platforms, but also suggest alternatives for Linux-only environments.
- Include troubleshooting steps relevant to Linux environments (e.g., file permissions, line endings).
Sap
Deploy the control plane for SAP Deployment Automation Framework
...b/main/articles/sap/automation/deploy-control-plane.md
High Priority
View Details →
Detected Bias Types
Missing Windows Example
Linux Only
Windows Excluded
Windows Tools
Summary
The documentation demonstrates a bias against Windows by providing detailed Linux/bash instructions for deploying the control plane, while explicitly stating that deployment cannot be performed from Windows. There are no Windows or PowerShell examples for the main deployment workflow, and Windows users are directed to use SSH clients to connect to Linux VMs rather than providing native Windows deployment options. The only Windows-specific content is for auxiliary tasks (e.g., preparing the web app), not for the core deployment process.
Recommendations
- Investigate and document whether the control plane deployment can be performed natively on Windows (e.g., via WSL, PowerShell, or Azure CLI for Windows).
- If Windows deployment is possible, provide PowerShell examples and instructions alongside bash/Linux examples.
- If Windows deployment is not supported, clarify the technical reasons and suggest alternatives (such as using WSL or Azure Cloud Shell from Windows).
- Ensure parity in tooling recommendations, mentioning Windows equivalents (e.g., PowerShell, Windows SSH clients) where appropriate.
- Consider providing a Docker-based deployment option that is cross-platform, with instructions for both Windows and Linux users.
Sap
Integrate SAP Cloud Appliance Library with SAP Deployment Automation Framework
...utomation/integration-sap-cloud-application-library.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 by consistently referencing Azure-specific tools and workflows, such as Azure DevOps, Azure portal, Azure Key Vault, and Azure PowerShell, without providing equivalent Linux or cross-platform alternatives. Examples and instructions are focused on Microsoft Entra, Azure CLI, and PowerShell, and there is no mention of Linux command-line tools or shell script examples, despite a brief reference to 'provided shell scripts.' The documentation assumes the use of Azure-centric infrastructure and omits guidance for Linux users or those using non-Windows environments.
Recommendations
- Include explicit Linux shell script examples for key steps, such as certificate creation and authentication.
- Provide instructions using cross-platform tools (e.g., Azure CLI) before or alongside PowerShell and portal-based steps.
- Add guidance for integrating with SAP CAL using Linux-based automation frameworks or CI/CD tools (e.g., Jenkins, GitLab CI).
- Clarify which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
- Reference Linux-specific documentation or best practices for SAP deployments on Azure.
Sap
Plan your SAP deployment with the automation framework on Azure
...s/blob/main/articles/sap/automation/plan-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific deployment scenarios, credential patterns, and tools (Active Directory, PowerShell Gallery, Visual Studio components) are described in detail, while Linux equivalents are either briefly mentioned or omitted. The only provided script example for connectivity testing is in PowerShell, with no Bash or Linux-native alternative. Windows tools and patterns (Active Directory, domain join, PowerShell scripts) are presented before or instead of Linux options, and Linux-specific instructions are less prominent.
Recommendations
- Provide equivalent Linux/Bash script examples for connectivity testing and other automation tasks, not just PowerShell.
- Include explicit Linux credential management patterns (e.g., integration with LDAP, Linux user accounts) alongside Windows/Active Directory examples.
- Mention Linux tools (such as OpenSSH, Bash, Linux package managers) in firewall and deployment requirements, with equal detail as Windows tools.
- Add examples and instructions for Linux-based deployments, such as joining SAP systems to Linux-based identity solutions, and clarify differences in credential storage.
- Ensure that both Windows and Linux deployment scenarios are described with parity in detail and order of presentation.
- Where PowerShell is referenced, also provide Bash or Python alternatives for Linux users.
Sap
Configure the automation framework for new and existing deployments
...s/blob/main/articles/sap/automation/new-vs-existing.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for deployment tasks, but PowerShell commands and modules (e.g., SAPDeploymentUtilities.psd1, New-SAPAutomationRegion) are featured prominently and sometimes before Bash equivalents. Windows-specific tooling and patterns (such as referencing Windows paths and modules) are present, and there is a notable mention of a Microsoft SQL Server back-end running Windows Server 2016 in the example scenario, with no Linux database alternative shown. The documentation lacks explicit Linux-specific guidance or parity for some advanced scenarios and tools.
Recommendations
- Ensure Bash and Linux-native examples are presented before or alongside PowerShell/Windows examples.
- Include Linux database alternatives (e.g., HANA on SUSE/Red Hat) in example scenarios, especially where Windows SQL Server is mentioned.
- Avoid Windows path notation (e.g., '\Azure_SAP_Automated_Deployment\...') in generic instructions; use platform-agnostic or dual notation.
- Document any differences in prerequisites, environment setup, or tooling for Linux users (e.g., required shell, permissions, package dependencies).
- Highlight cross-platform compatibility and limitations for all scripts and modules, and provide troubleshooting tips for Linux environments.
- Where PowerShell modules are referenced, clarify if Bash equivalents exist or provide alternative approaches for Linux users.
Sap
Run Ansible to configure the SAP system
...-docs/blob/main/articles/sap/automation/run-ansible.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides parity between Linux and Windows by using tabbed sections for each platform, but there is evidence of Windows bias. Windows-specific tools (such as DSC modules, Windows Defender, ServerManager, SecurityPolicyDsc, and Windows Failover Clustering) are mentioned explicitly, while Linux equivalents (such as systemd, firewalld, or SELinux) are not named. In the operating system configuration section, Windows tasks are listed first and in greater detail, with specific modules and components called out. The use of PowerShell Desired State Configuration (DSC) modules is highlighted for Windows, but no similar configuration management tools (like Ansible roles for Linux hardening) are referenced for Linux. The scripts and playbook commands are Bash-based for both platforms, but Windows-specific environment variables and Azure Key Vault usage are more prominent.
Recommendations
- Explicitly mention Linux equivalents for Windows tools and configuration modules (e.g., systemd, firewalld, SELinux, Linux security hardening roles).
- Provide equal detail for Linux configuration steps, listing specific packages, services, and security modules involved.
- Reference Linux-native configuration management approaches (such as Ansible roles for OS hardening, package management, and security) alongside Windows DSC modules.
- Ensure that both Linux and Windows sections are equally detailed and that neither platform is listed first by default.
- Where PowerShell/DSC is mentioned for Windows, mention Ansible modules or roles for Linux that achieve similar outcomes.
Sap
Quickstart - Install software for a Distributed HA SAP system with Azure Center for SAP solutions with custom resource names using Azure CLI
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-install-high-availability-namecustom-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as a tool for creating the JSON configuration file, without mentioning Linux alternatives. There are no explicit Linux shell (bash) examples or instructions, and the prerequisites and workflow implicitly assume familiarity with Windows tooling and patterns. The Azure CLI is cross-platform, but the supporting instructions and examples do not address Linux users or provide parity in guidance.
Recommendations
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
- Provide Linux/bash examples for creating and editing the JSON configuration file, such as using nano, vim, or other Linux editors.
- Reference Linux tools and workflows alongside PowerShell, e.g., show how to generate or manipulate the payload file using bash commands.
- Clarify that prerequisites and steps apply equally to Linux environments, and note any OS-specific differences.
- Include links to installing and using Azure CLI on Linux and macOS.
- Avoid mentioning PowerShell or Windows tools exclusively; always provide cross-platform alternatives.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias in several ways: Windows-specific tools (PowerShell, Windows VM Agent) and file paths are mentioned before or more prominently than their Linux equivalents. PowerShell is referenced as a primary automation interface, with Linux CLI only mentioned as an alternative. Some troubleshooting and prerequisite instructions are more detailed for Windows, and Linux commands/examples are sometimes missing or less emphasized.
Recommendations
- Provide Linux CLI and shell script examples alongside PowerShell, with equal prominence.
- List Linux and Windows file paths and commands together, or alternate their order to avoid Windows-first presentation.
- Expand troubleshooting sections to include detailed Linux steps where Windows instructions are given.
- Reference Linux tools (e.g., Bash, systemctl) as primary options where appropriate, not only as alternatives.
- Ensure parity in error handling and agent management instructions for both Windows and Linux environments.
- Include screenshots or walkthroughs for Linux registration flows in the Azure portal, not just Windows.
- Review all sections for implicit prioritization of Windows and revise to present both platforms equally.
Sap
Other network requirements for SAP HANA on Azure (Large Instances) | Microsoft Docs
...hived-hli-docs/hana-additional-network-requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation repeatedly lists 'PowerShell' as a primary tool for network management tasks, often before or alongside the Azure portal and Azure CLI. There are no explicit Linux-specific command examples or references to Linux-native tools (such as Bash or shell scripts), despite the article targeting Linux-based SAP HANA deployments. This creates a subtle Windows bias by prioritizing Windows-centric tools and omitting Linux-focused guidance.
Recommendations
- Provide explicit Linux command-line examples using Azure CLI (az) in Bash, especially for common tasks like adding/removing subnets and virtual networks.
- Mention Bash/shell scripting as a valid automation method for Linux administrators, and link to relevant Azure CLI documentation for Linux.
- When listing management tools, list Azure CLI first (since it is cross-platform and often preferred on Linux), followed by portal and PowerShell.
- Add a note clarifying that PowerShell is available on Linux, but most Linux administrators use Azure CLI or Bash.
- Include sample scripts or command snippets for both Linux and Windows environments to ensure parity.
Sap
Start and stop SAP systems, instances and HANA database
...les/sap/center-sap-solutions/start-stop-sap-systems.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows and PowerShell interfaces before Linux alternatives, referencing Windows-specific clustering (WSFC) alongside Linux options, and mentioning Azure PowerShell as a primary automation tool. There are no explicit Linux shell or command-line examples, and the documentation does not provide parity in CLI or Linux-native instructions, despite claiming support for RHEL and SUSE. Windows terminology and tools are referenced first or exclusively in several sections.
Recommendations
- Add explicit Linux shell (bash) examples for starting and stopping SAP systems using Azure CLI, especially for RHEL and SUSE environments.
- Present Linux and Windows instructions in parallel, or alternate which is listed first, to avoid Windows-first ordering.
- Include references to Linux-native tools and patterns (e.g., systemctl, Pacemaker commands) where relevant, not just Windows Server Failover Clustering (WSFC) and PowerShell.
- Clarify any differences in workflow or troubleshooting steps for Linux environments.
- Ensure screenshots and UI references are not exclusively Windows-centric, and include Linux-relevant visuals where possible.
Sap
Data reference for Azure Monitor for SAP solutions
...-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 demonstrates a Windows bias primarily through the extensive focus on Microsoft SQL Server (MSSQL) tables and references, which are inherently Windows-centric. Many referenced system views and functions (e.g., sys.dm_os_windows_info, SQL Server DMVs) are specific to Windows environments, with no equivalent coverage for Linux-based database systems (such as SAP HANA on Linux or PostgreSQL). While Prometheus exporters (node_exporter, ha_cluster_exporter) are mentioned, these are the only Linux-native tools referenced, and they appear after the Windows/MSSQL sections. There are no examples or references to Linux command-line tools, log locations, or monitoring patterns outside of Prometheus.
Recommendations
- Add equivalent examples and references for Linux-based SAP deployments, such as log file locations, system views, and monitoring commands relevant to Linux environments.
- Include documentation for monitoring SAP HANA on Linux, such as using Linux-native tools (e.g., journalctl, systemd, top, vmstat) for troubleshooting and performance analysis.
- Provide parity in examples by listing Linux/Prometheus exporters and tools before or alongside Windows/MSSQL tools, rather than after.
- Expand coverage to include other common Linux database platforms (e.g., PostgreSQL, MySQL) if supported, or clarify platform limitations.
- Explicitly state platform requirements and differences for each log table, helping users understand which apply to Windows, Linux, or both.
Sap
Enable Insights to troubleshoot SAP workload issues
.../blob/main/articles/sap/monitor/enable-sap-insights.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways. The only command-line example for enabling access uses PowerShell, with explicit instructions to switch from Bash to PowerShell in Azure Cloud Shell. There are no equivalent Bash or Linux shell script examples provided, nor is there mention of Linux-native tooling or patterns. The quickstart links and onboarding script are PowerShell-centric, and the workflow assumes familiarity with Windows/PowerShell environments. This may disadvantage users who primarily use Linux or Bash in their SAP on Azure deployments.
Recommendations
- Provide equivalent Bash shell script examples for onboarding and role assignment, alongside PowerShell scripts.
- Include instructions for using Azure CLI (az) commands to perform role assignments, which are cross-platform and work natively in Linux environments.
- Mention both Bash and PowerShell options in Cloud Shell instructions, rather than instructing users to switch to PowerShell.
- Add screenshots and walkthroughs for Linux/Bash workflows where applicable.
- Review all referenced quickstarts and guides to ensure Linux parity and visibility.
Sap
Configure SAP NetWeaver for Azure Monitor for SAP solutions
...s/blob/main/articles/sap/monitor/provider-netweaver.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and workflows (such as SAP MMC, PowerShell scripts, and Windows Defender Firewall) are mentioned before or in more detail than their Linux equivalents. PowerShell is used for validation and scripting examples, while Linux alternatives are less prominent or missing. Some instructions and links are specifically for Windows environments, and troubleshooting steps often lead with Windows solutions.
Recommendations
- Provide Linux/Bash script equivalents for all PowerShell examples, especially for validation and automation steps.
- Present Linux and Windows instructions in parallel, giving equal prominence to both platforms in step-by-step guides and troubleshooting.
- Include links to Linux-specific resources and scripts where Windows-only links are currently provided.
- Expand on Linux tools and workflows (e.g., systemd/service management, firewall configuration) to match the detail given for Windows tools.
- Ensure screenshots and UI walkthroughs are available for both SAP MMC (Windows) and relevant Linux management consoles or CLI tools.
- Review all prerequisite and troubleshooting sections to confirm Linux parity in examples, commands, and guidance.
Sap
Configure SQL Server provider for Azure Monitor for SAP solutions
.../blob/main/articles/sap/monitor/provider-sql-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-specific tools (SQL Server Management Studio), Windows authentication modes, and Windows firewall configuration. There are no Linux equivalents or examples provided for configuring SQL Server on Linux, opening ports on Linux firewalls, or using Linux-native tools. The prerequisites and configuration steps assume a Windows environment, omitting guidance for users running SQL Server on Linux.
Recommendations
- Add instructions and examples for configuring SQL Server on Linux, including authentication modes and user creation.
- Include guidance for opening ports in Linux firewalls (e.g., using ufw or firewalld).
- Mention and provide examples using Linux-native SQL Server tools (such as sqlcmd or Azure Data Studio) alongside SQL Server Management Studio.
- Clarify that the steps apply to both Windows and Linux deployments, or specify any differences.
- Provide links to official Microsoft documentation for SQL Server on Linux where appropriate.
Sap
Set up a network for Azure Monitor for SAP solutions
...-docs/blob/main/articles/sap/monitor/set-up-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell in the 'Next steps' section and providing a quickstart specifically for PowerShell, without mentioning or linking to Linux CLI equivalents. The instructions and examples focus on Azure portal and PowerShell workflows, with no explicit mention of Bash, Azure CLI, or Linux-native tools. There are no examples or guidance tailored for Linux users, such as using Azure CLI commands in Bash or shell scripting for network configuration.
Recommendations
- Add equivalent quickstart guides for Linux users, such as 'Set up Azure Monitor for SAP solutions with Azure CLI' or Bash scripting.
- Include example commands using Azure CLI (az) for all major steps, alongside PowerShell examples.
- Explicitly mention Linux compatibility and provide guidance for Linux administrators, including references to Linux tools and workflows.
- Ensure that instructions for network configuration, NSG rules, and subnet management include both portal, PowerShell, and CLI/Bash approaches.
- Review screenshots and UI references to ensure they are not exclusively Windows-centric.
Sap
SAP Business One on Azure Virtual Machines | Microsoft Docs
...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 page exhibits a Windows bias by frequently mentioning Windows and Windows Server before Linux, referencing Windows-specific tools and tutorials (such as PowerShell), and providing more detailed guidance for Windows environments. Linux equivalents are mentioned but often after Windows, and there are fewer Linux-specific operational details or examples. There is a lack of parity in example scripts, operational recommendations, and VM sizing guidance for Linux-based deployments.
Recommendations
- Ensure Linux and Windows are mentioned with equal prominence and order throughout the documentation.
- Provide Linux-specific examples and operational guidance, such as Bash/CLI commands alongside PowerShell.
- Include links to both Windows and Linux VM sizing documentation and best practices.
- Reference Linux tools and management patterns (e.g., SSH, cloud-init) as alternatives to Windows tools like PowerShell and RDS.
- Add explicit Linux deployment scenarios and troubleshooting tips where only Windows is currently covered.
- Balance recommendations for OS versions, giving equal detail to recent Linux releases as is given to Windows Server.
Sap
SAP BusinessObjects BI Platform Deployment on Azure | Microsoft Docs
...cles/sap/workloads/businessobjects-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows and Azure SQL Database are frequently mentioned first or exclusively, especially in examples and recommendations. There is a lack of parity in detailed Linux-specific guidance, with Linux options often mentioned as secondary or in passing. Windows tools and services (e.g., Azure SQL Database for Windows) are described in greater detail, while Linux equivalents (e.g., Azure Database for MySQL) receive less coverage and fewer practical examples.
Recommendations
- Provide Linux-first and Linux-specific examples, especially for deployment steps, configuration, and troubleshooting.
- Ensure that Linux tools and patterns (e.g., NFS setup, Linux VM configuration, Linux-specific high availability) are described with the same level of detail as Windows equivalents.
- Include explicit, step-by-step Linux deployment walkthroughs alongside Windows walkthroughs.
- Balance recommendations so that both Windows and Linux approaches are presented equally, rather than defaulting to Windows-first.
- Highlight Linux compatibility and best practices in architecture diagrams and storage/networking sections.
- Add more references and links to Linux-focused SAP BusinessObjects BI Platform resources.
Sap
Microsoft Azure certifications for SAP | Microsoft Docs
...ocs/blob/main/articles/sap/workloads/certifications.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation lists both Windows and Linux as supported platforms for SAP workloads on Azure, but there is a noticeable Windows bias. Windows is frequently listed first in tables and examples, and several products (e.g., SAP BusinessObjects BI, SAP Business One on SQL Server, SAP Hybris Commerce Platform) are documented as Windows-only or Windows-first, with Linux equivalents mentioned later or not at all. There are references to Windows-specific tools (SQL Server, Oracle on Windows), and some products lack Linux-specific configuration or example details.
Recommendations
- Ensure Linux platforms are listed first or equally in tables and examples, especially since the page is tagged as Linux-focused.
- Provide Linux-specific examples and configuration details where only Windows is currently described.
- Highlight Linux-compatible database options and tools alongside Windows ones.
- Clarify parity between Windows and Linux support for each SAP product, including any limitations or differences.
- Add explicit Linux usage scenarios and best practices to match the depth of Windows coverage.
Sap
Considerations for Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
...blob/main/articles/sap/workloads/dbms-guide-general.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits mild Windows bias in several areas. Windows-specific tools (e.g., Storage Spaces) are mentioned before Linux equivalents (MDADM/LVM), and Windows examples or terminology (e.g., drive D, Windows Server versions) are often presented first or in more detail. Conversion instructions for managed disks list Windows before Linux. Some references and links are Windows-centric (e.g., SQL Server Always On, Windows failover cluster guides), and there is a heavier emphasis on Windows terminology and patterns. Linux examples are present but sometimes less detailed or appear after Windows ones.
Recommendations
- Present Linux and Windows examples in parallel, ensuring equal detail and prominence.
- List Linux tools and procedures before or alongside Windows equivalents, not after.
- Expand Linux-specific guidance and terminology (e.g., more details on MDADM/LVM usage, Linux network configuration).
- Ensure links and references for Linux are as comprehensive and visible as those for Windows.
- Avoid Windows-centric language (e.g., 'drive D') without immediately providing the Linux equivalent ('/mnt/resource').
- Where possible, provide cross-platform scripts or commands (e.g., Bash and PowerShell) for common tasks.
Sap
IBM Db2 Azure Virtual Machines DBMS deployment for SAP workload | Microsoft Docs
...ocs/blob/main/articles/sap/workloads/dbms-guide-ibm.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific tools and patterns (e.g., Storage Pools, PowerShell cmdlets) are mentioned and explained in detail, sometimes before or instead of Linux equivalents. For example, Windows Storage Pools are described with explicit command-line instructions, while Linux alternatives (LVM, mdadm) are referenced but not shown with example commands. In some sections, Windows features and limitations (such as VSS backup support) are discussed, but Linux-specific backup/restore strategies are not elaborated. There are also areas where Windows configuration details are more thoroughly documented than Linux, and Linux examples are missing or less detailed.
Recommendations
- Provide Linux command-line examples for storage configuration (e.g., LVM, mdadm) similar to the PowerShell examples for Windows Storage Pools.
- Ensure Linux tools and patterns are described with equal detail and prominence as Windows equivalents.
- Include Linux-specific backup/restore strategies and considerations, not just Windows limitations.
- Where Windows features are discussed first or exclusively, add parallel Linux sections or examples.
- Review the order of presentation to avoid consistently listing Windows options before Linux, unless justified by user base or technical requirements.