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 351-375 of 639 flagged pages
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/high-availability-guide-rhel-pacemaker.md
...ap/workloads/high-availability-guide-rhel-pacemaker.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
While the documentation is focused on setting up Pacemaker on RHEL in Azure and is generally Linux-centric, there are notable instances of Windows bias. The only example for creating and attaching Azure shared disks is provided using PowerShell, with Azure CLI and portal options relegated to a brief mention. The documentation references PowerShell and Windows-centric tools before Linux-native equivalents, and some links for managed identity configuration point to Windows VM instructions. This may create friction for Linux administrators who expect parity in CLI or portal-based examples.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples for creating and attaching Azure shared disks, as CLI is more commonly used in Linux environments.
- Include explicit step-by-step instructions for performing key Azure resource management tasks (e.g., disk creation, managed identity assignment) using the Azure CLI and Azure portal, not just PowerShell.
- Ensure that all referenced links for identity and resource configuration include Linux VM-specific instructions or clarify when steps are OS-agnostic.
- Review all sections for ordering bias, ensuring that Linux-native tools and workflows are presented first or at least equally with Windows/PowerShell alternatives.
- Where possible, avoid referencing Windows-specific documentation or tools unless strictly necessary, and always provide the Linux equivalent.
Create Pull Request
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/bom-get-files.md
...ocs/blob/main/articles/sap/automation/bom-get-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-style file extensions (e.g., .EXE), using Windows-centric tools (such as SAP Download Manager and Postman) without mentioning Linux alternatives or command-line equivalents, and omitting Linux-specific instructions or examples for downloading and uploading files. While there are some references to Linux (e.g., 'LINUX ON X86_64 64BIT'), practical steps and examples are presented in a way that assumes a Windows environment.
Recommendations
- Provide explicit Linux command-line examples for downloading and uploading SAP media, such as using wget, curl, or azcopy/azure-cli for uploads.
- Mention and give examples for running SAP Download Manager and Postman on Linux, or suggest alternative CLI tools where possible.
- When referencing file extensions (e.g., SAPCAR*.EXE), also mention the Linux equivalents (e.g., SAPCAR for Linux, without .EXE).
- Include screenshots or terminal commands for Linux environments alongside any GUI-based instructions.
- Clarify any OS-specific steps, such as directory paths (use both Windows and Linux path formats in examples).
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-sap-parameters.md
...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 provides some Windows-specific parameters and references (such as Windows domain, cluster, and SQL Server), and these are grouped under dedicated sections. However, there is no equivalent section or explicit mention of Linux-specific parameters, tools, or patterns, despite the fact that most SAP deployments on Azure are Linux-based. The only example YAML and command-line overrides shown are generic and do not demonstrate Linux-specific patterns or tools. Windows-specific terms (e.g., 'Windows cluster service', 'domain_name', 'win_cluster_share_type') are present, but there are no Linux equivalents (e.g., for Linux clustering, authentication, or file system patterns).
Recommendations
- Add a dedicated section for Linux-specific parameters, such as those related to Linux authentication (e.g., sssd, LDAP), clustering (e.g., Pacemaker, Corosync), or file system mounting patterns.
- Provide Linux-specific examples for overriding parameters, such as sample Ansible playbook commands run from a Linux shell, or examples of Linux-specific YAML configurations.
- Balance the documentation by ensuring that for every Windows-specific parameter or example, a Linux equivalent is provided where applicable.
- Mention Linux tools and patterns explicitly, such as LVM, NFS mount options, or Linux user/group management, especially in sections where Windows tools (like domain or cluster) are discussed.
- Clarify in the introductory sections which parameters or sections are relevant for Linux, Windows, or both, to help users quickly find platform-specific guidance.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-workload-zone.md
...ain/articles/sap/automation/configure-workload-zone.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Utility VM parameters' section, where the default image for the utility virtual machine is 'Windows Server 2019' and the suggested use case is to host SAPGui (a Windows-only tool). While there is a code example for defining a Linux VM image, it is not presented as the default or recommended option. There are no explicit Linux/Unix command-line examples or references to Linux-native tools, and the documentation does not provide parity in usage scenarios or defaults for Linux environments.
Recommendations
- Present both Windows and Linux options equally in the 'Utility VM parameters' section, including default examples for both.
- Explicitly mention Linux use cases for the utility VM, such as hosting SAP CLI tools or other Linux-based SAP utilities.
- Provide example configurations for common Linux distributions (e.g., Ubuntu, RHEL, SUSE) alongside the Windows Server example.
- Clarify that SAPGui is a Windows-only tool and suggest Linux alternatives or remote access methods if available.
- Wherever defaults are specified (such as default OS image), offer Linux as an alternative default or at least document how to select it.
- Add Linux-specific configuration or deployment examples where relevant, ensuring Linux users are equally supported.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/configure-devops.md
.../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 demonstrates a significant Windows bias. The primary automation scripts are provided exclusively in PowerShell, with instructions to use PowerShell ISE and .ps1 scripts. While there are some Linux-specific instructions (notably for the web app setup and a few bash snippets), the main setup and automation flows are PowerShell-centric, and Linux equivalents are either missing or only provided later. The documentation assumes the use of Windows tools and patterns (e.g., PowerShell ISE, .ps1 scripts, Windows file paths) and only provides Linux/bash examples in isolated sections, often after the Windows instructions.
Recommendations
- Provide full-featured bash shell scripts for all automation steps currently only available as PowerShell scripts, ensuring parity for Linux users.
- Avoid instructions that assume the use of PowerShell ISE or other Windows-specific tools; instead, offer cross-platform alternatives (e.g., VS Code, plain text editors, or shell terminals).
- When presenting code examples, use tabbed sections for both Windows (PowerShell) and Linux (bash) equally, and ensure both are complete and tested.
- Mention Linux and macOS support explicitly at the start, and clarify any prerequisites or differences in setup.
- Where possible, use platform-agnostic tools and commands (e.g., Azure CLI, Python scripts) instead of platform-specific scripting languages.
- Review all steps for references to Windows-only file paths or environment variables, and provide Linux equivalents.
- Ensure that all automation scripts referenced from GitHub have both .ps1 (PowerShell) and .sh (bash) versions, or provide clear guidance for Linux users.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/get-started.md
...-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 demonstrates a Windows bias by providing detailed PowerShell scripts for key setup steps (such as application registration and Azure DevOps environment creation) without equivalent Bash/Linux shell examples. PowerShell is used as the default scripting language, and instructions often reference Windows tools (e.g., PowerShell ISE) or use Windows-centric patterns first, with only minimal or conditional Unix/Linux handling. Some critical automation steps are only shown in PowerShell, leaving Linux users to adapt or reverse-engineer the process.
Recommendations
- Provide equivalent Bash or shell script examples for all major automation steps, especially for application registration and Azure DevOps environment setup.
- Avoid referencing Windows-specific tools (like PowerShell ISE) as the default; instead, offer cross-platform alternatives or clarify when a step is platform-specific.
- When showing scripts, present both Windows (PowerShell) and Linux (Bash) versions side by side or clearly indicate how to perform each step on both platforms.
- Explicitly document any differences or prerequisites for Linux environments, ensuring parity in instructions and automation.
- Test all provided scripts on both Windows and Linux to ensure they work as documented.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/integration-sap-cloud-application-library.md
...utomation/integration-sap-cloud-application-library.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows/Azure-centric bias by focusing exclusively on Azure DevOps, Microsoft Entra, and Azure Key Vault tools and workflows. While there is a brief mention of 'shell scripts' and a link with a '?tabs=linux' parameter, there are no explicit Linux or cross-platform command-line examples. All step-by-step instructions and screenshots are based on Azure portal, Azure CLI, or Azure PowerShell, with no equivalent Linux-native or non-Microsoft tool guidance provided.
Recommendations
- Provide explicit Linux command-line examples for key steps, such as certificate creation and authentication setup, using standard Linux tools (e.g., OpenSSL, curl) in addition to Azure CLI/PowerShell.
- Include alternative instructions for users who prefer to use non-Azure DevOps CI/CD systems (e.g., GitLab CI, Jenkins) or shell scripts, with sample YAML or bash scripts.
- Balance the documentation by presenting Linux-native workflows and tools alongside Azure-specific ones, ensuring that Linux users are not required to use Windows-centric tools or interfaces.
- Add screenshots or terminal output examples from Linux environments where appropriate.
- Clarify in each section whether the instructions are cross-platform, and provide links to Linux/macOS-specific guidance if available.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/deploy-control-plane.md
...b/main/articles/sap/automation/deploy-control-plane.md
High Priority
View Details →
Detected Bias Types
Missing Windows Example
Linux First
Linux Only
Windows Tools
Summary
The documentation demonstrates a bias toward Linux environments. All core deployment instructions and scripts are provided exclusively for Linux, with explicit statements that Windows cannot be used for control plane deployment. Windows-specific instructions are only present for optional or peripheral tasks (such as preparing the web app), and even then, the main deployment workflow is not supported on Windows. Linux examples are always presented first and in detail, while Windows is either omitted or explicitly unsupported.
Recommendations
- Provide equivalent PowerShell or Windows Command Prompt scripts for all deployment steps where possible.
- If Windows is not supported for certain operations, explain the technical reasons and suggest workarounds (e.g., using WSL, Docker, or Azure Cloud Shell).
- Ensure that any scripts or automation tools are cross-platform or document their platform requirements clearly at the beginning.
- For tasks that can be performed on both platforms (such as preparing the web app), ensure parity in the depth and clarity of examples.
- Consider providing guidance for using WSL on Windows as an alternative for users who prefer or are required to use Windows environments.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/plan-deployment.md
...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 exhibits a moderate Windows bias. While it acknowledges Linux as a deployment platform and references Linux VMs and shell scripts, several sections provide Windows-specific details, tools, and examples without equivalent Linux coverage. Notably, the only explicit script example for connectivity testing is in PowerShell, and Windows tools (PowerShell Gallery, Visual Studio components) are listed with detailed firewall requirements, while Linux equivalents are not. The 'Windows-based deployments' section is detailed, but there is no parallel section for Linux-based deployments. This may leave Linux users without clear guidance for equivalent tasks.
Recommendations
- Provide Linux/bash script examples alongside PowerShell scripts, especially for connectivity testing and automation tasks.
- Include a section on Linux-based deployments with details similar to the 'Windows-based deployments' section (e.g., credential management, DNS integration, required accounts).
- List Linux-specific tools and their firewall/network requirements (e.g., apt/yum repositories, SSH, relevant package sources) in the firewall configuration table.
- Ensure that when both Windows and Linux are supported, examples and instructions for both platforms are presented with equal prominence and detail.
- Where possible, use cross-platform tools (e.g., Azure CLI, bash scripts) in examples, or provide both Windows and Linux alternatives.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/tools-configuration.md
...ob/main/articles/sap/automation/tools-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing file path examples in Windows format (e.g., C:\Users\...), referencing Windows-specific directory conventions, and omitting equivalent Linux/macOS instructions for saving SSH keys. The workflow assumes a Windows user environment, with no guidance for Linux or macOS users on where to store SSH keys or how to adapt the process. Visual Studio Code instructions are otherwise cross-platform, but the lack of Linux/macOS parity in file handling is significant.
Recommendations
- Provide parallel instructions and examples for Linux and macOS users, including file paths (e.g., ~/.ssh/weeu_deployer.ssh) and commands.
- When referencing file paths, show both Windows and Unix-style examples side by side.
- Explicitly mention that the instructions apply to all platforms, and note any platform-specific differences.
- Include screenshots or command snippets for Linux/macOS environments where relevant.
- Review the documentation for other implicit Windows assumptions and address them for cross-platform parity.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/automation/tutorial.md
...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 generally assumes a Linux/Bash environment for automation and scripting, which is appropriate for SAP automation on Azure. However, there are several instances of Windows bias: (1) File path examples and instructions for saving SSH keys use Windows paths (e.g., C:\Users\<your-username>\.ssh) and Windows-centric editors (Notepad++), (2) Visual Studio Code is recommended as the primary editor, and (3) PuTTY/PuTTYGen are mentioned for SSH key conversion, which are Windows tools, without mentioning Linux-native alternatives. There are no PowerShell or Windows CMD script examples, but the documentation does not provide explicit Linux-native alternatives for file management or SSH key handling, and the order of tool recommendations often puts Windows tools first.
Recommendations
- When giving file path examples for SSH keys, provide both Windows (C:\Users\<username>\.ssh) and Linux (~/.ssh) examples, or default to Linux paths since the automation is Bash/Ansible-based.
- When recommending editors, mention Linux-native editors (e.g., nano, vim, gedit) alongside Visual Studio Code and Notepad++.
- When discussing SSH key conversion, mention Linux-native tools (e.g., ssh-keygen, OpenSSH utilities) in addition to PuTTY/PuTTYGen.
- If referencing Visual Studio Code, clarify that it is cross-platform and provide instructions for both Windows and Linux users.
- Where possible, avoid assuming the user is on Windows, especially in sections about connecting to VMs, managing files, or editing configuration files.
- Add explicit notes or examples for Linux users where Windows-specific instructions are given.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/about-azure-monitor-sap-solutions.md
...icles/sap/monitor/about-azure-monitor-sap-solutions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing Azure PowerShell as the only command-line deployment method, without mentioning Azure CLI or Linux-native alternatives. The 'How can you create Azure Monitor for SAP solutions resources?' section lists the Azure portal and Azure PowerShell, omitting Azure CLI, which is commonly used on Linux. No Linux-specific deployment or configuration examples are provided, and the only command-line automation path is Windows-centric. While the monitored systems include Linux (e.g., Pacemaker clusters, Linux OS), the documentation does not provide parity in tooling or examples for Linux users.
Recommendations
- Add Azure CLI instructions and examples alongside Azure PowerShell for deployment and configuration tasks.
- Explicitly mention support for Linux environments in deployment and operational sections.
- Provide sample scripts or walkthroughs using Bash or shell scripting for common Linux scenarios.
- Ensure that any references to command-line tools are cross-platform, or provide equivalent steps for both Windows and Linux users.
- Review and update quickstart and how-to guides to include Linux-first or Linux-equal workflows.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/provider-sql-server.md
.../blob/main/articles/sap/monitor/provider-sql-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns, such as SQL Server Management Studio and Windows authentication modes. It instructs users to open 'Windows ports' and references configuring firewalls only in the context of Windows. There are no Linux or cross-platform examples or instructions, and Linux-based SQL Server deployments are not mentioned.
Recommendations
- Include instructions for configuring SQL Server on Linux, such as using 'mssql-conf' or editing configuration files directly.
- Provide examples for opening ports on Linux firewalls (e.g., using 'firewalld', 'ufw', or 'iptables').
- Mention cross-platform tools (e.g., Azure Data Studio) alongside SQL Server Management Studio.
- Clarify that the steps apply to both Windows and Linux SQL Server deployments, or specify when steps are Windows-only.
- Add links to official Microsoft documentation for configuring SQL Server authentication and encryption on Linux.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/compliance-cedr.md
...n/articles/sap/center-sap-solutions/compliance-cedr.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for re-registering SAP systems, mentioning PowerShell before CLI in mitigation steps, and omitting any explicit Linux/Unix shell or Azure CLI (bash) examples. There is no mention of Linux-specific tools or workflows, which may disadvantage users operating from Linux environments.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell, preferably in bash syntax, to support Linux and cross-platform users.
- When referring to command-line tools, mention Azure CLI before or alongside PowerShell to avoid implying a Windows-first workflow.
- Explicitly state that both Windows and Linux environments are supported, and link to relevant cross-platform documentation.
- Include notes or examples for Linux administrators, such as using bash or shell scripts for automation.
- Review terminology and instructions to ensure they are not tailored exclusively to Windows users.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/compliance-bcdr-reliabilty.md
...sap/center-sap-solutions/compliance-bcdr-reliabilty.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation references PowerShell and CLI as deployment interfaces but consistently lists PowerShell first, suggesting a Windows-first approach. There are no explicit Linux shell or Bash examples, nor are Linux-specific tools or workflows mentioned. The documentation does not provide parity in examples or instructions for Linux users.
Recommendations
- Explicitly provide both PowerShell and Bash/Azure CLI examples for all command-line instructions.
- When mentioning deployment interfaces, alternate the order (e.g., 'CLI and PowerShell') or clarify that both Windows and Linux users are supported equally.
- Include screenshots or walkthroughs from both Windows and Linux environments where applicable.
- Reference Linux-specific tools or workflows (e.g., Bash scripts, SSH) alongside Windows tools.
- Add a section or note clarifying that all features and procedures are supported on both Windows and Linux platforms.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/deploy-s4hana.md
...ain/articles/sap/center-sap-solutions/deploy-s4hana.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell-only example for listing Azure Marketplace images, with no equivalent Azure CLI (bash/Linux) example. This may disadvantage Linux users, as PowerShell is primarily associated with Windows environments. No Linux-native tooling or command-line patterns are shown, and the only scripting example is in PowerShell.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all scripting tasks, especially for listing VM images.
- Explicitly mention that both PowerShell and Azure CLI can be used, and link to Azure CLI documentation.
- Where possible, show both Windows and Linux command-line workflows for common tasks.
- Avoid assuming PowerShell as the default scripting environment; offer parity for Linux-native tools.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/soft-stop-sap-and-hana-database.md
...enter-sap-solutions/soft-stop-sap-and-hana-database.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) as the first and primary example for all operations, followed by Azure CLI and REST API. There are no examples or guidance for native Linux shell commands or scripts, nor any mention of Linux-specific tools or workflows. This may give the impression that Windows environments are prioritized or required, even though SAP and HANA are commonly deployed on Linux.
Recommendations
- Provide explicit Linux shell (bash) examples for using the Azure CLI, including sample commands and expected output.
- Clarify that Azure CLI is fully cross-platform and can be used natively on Linux, macOS, and Windows.
- If relevant, include native SAP/Linux commands (e.g., using sapcontrol or HDB stop commands) for users who may need to perform soft stops outside of Azure tooling.
- Balance the order of examples: alternate between starting with CLI and PowerShell, or group them together to avoid implying a Windows-first workflow.
- Add a section or note highlighting Linux support and any Linux-specific considerations for SAP and HANA operations in Azure.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-register-system-cli.md
...center-sap-solutions/quickstart-register-system-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates some Windows bias by referencing Windows tools and file paths before or more prominently than Linux equivalents, and by providing a Windows-only example for checking the status of the SAP host control agent. Some Linux commands are mentioned, but not always with parity or equal detail.
Recommendations
- Ensure that for every Windows-specific command or file path, the Linux equivalent is also provided, and vice versa.
- Present Linux and Windows instructions/examples side-by-side or in parallel sections, rather than listing Windows first or exclusively.
- Where commands differ between platforms (e.g., checking sapstartsrv status), provide both Linux and Windows examples.
- Review the order of presentation so that neither platform is consistently prioritized over the other.
- Consider adding a table or clear callouts for platform-specific steps to improve clarity and parity.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/hana-additional-network-requirements.md
...arge-instances/hana-additional-network-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing explicit PowerShell examples and links, while omitting equivalent Linux/Unix command-line (Azure CLI or Bash) examples. PowerShell is mentioned before Azure CLI, and no Linux-specific guidance or parity is offered, despite the article being targeted at Linux-based SAP HANA deployments.
Recommendations
- Provide Azure CLI (cross-platform) examples and links alongside or before PowerShell examples, especially since the target audience is likely to use Linux.
- When referencing how to perform tasks (such as creating or deleting subnets or virtual networks), include both PowerShell and Azure CLI/Bash instructions or links.
- Avoid listing PowerShell before Azure CLI in instructions or links, or alternate the order to avoid implicit prioritization.
- Explicitly mention that all operations can be performed from Linux environments using Azure CLI, and provide sample commands.
- Review and update all referenced documentation links to ensure Linux users are equally supported.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-install-high-availability-namecustom-cli.md
...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 demonstrates a Windows bias by referencing PowerShell as a primary tool for creating the required JSON configuration file, without providing equivalent Linux shell or cross-platform examples. The mention of PowerShell precedes Azure CLI in the prerequisites, and there are no explicit Linux shell or bash examples for steps such as generating the JSON file or managing SSH keys, which are common tasks in Linux environments. While the main deployment example uses Azure CLI (which is cross-platform), the supporting instructions and context favor Windows tools and workflows.
Recommendations
- Provide explicit Linux shell/bash examples for generating the JSON configuration file, managing SSH keys, and other preparatory steps.
- Mention cross-platform or Linux-native tools (such as nano, vi, or jq) alongside or before PowerShell when discussing file creation or manipulation.
- Rephrase prerequisites to avoid listing PowerShell before Azure CLI, or clarify that both Windows and Linux users can use Azure CLI for all steps.
- Include notes or links to Linux-specific guidance for common tasks (e.g., creating service principals, editing JSON files, handling SSH keys).
- Audit all referenced tools and commands to ensure Linux parity and avoid implicit preference for Windows environments.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/register-existing-system.md
...s/sap/center-sap-solutions/register-existing-system.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (e.g., PowerShell, Windows file paths, and VM agent troubleshooting) are mentioned explicitly and often before or in more detail than their Linux equivalents. Some instructions and troubleshooting steps are more detailed for Windows, and in some cases, Linux examples or commands are missing or less emphasized. The documentation references PowerShell and Windows tools prominently, sometimes without providing equivalent Linux/CLI alternatives or giving them equal prominence.
Recommendations
- Ensure that all examples and instructions are provided for both Windows and Linux platforms, with equal detail and visibility.
- When referencing tools or interfaces (e.g., PowerShell), always mention and provide examples for Azure CLI and Bash/shell scripts for Linux users.
- List Linux and Windows options in parallel, rather than mentioning Windows first or in more detail.
- For file paths, always provide both Windows and Linux paths together.
- In troubleshooting sections, ensure that Linux and Windows solutions are equally detailed, and that links to Linux-specific troubleshooting guides are as prominent as those for Windows.
- Avoid language that implies Windows is the default or primary platform; treat both platforms as first-class citizens.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-create-distributed-non-high-availability.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/center-sap-solutions/quickstart-create-distributed-non-high-availability.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, and there is no mention or example of equivalent commands using Bash, Azure CLI, or Linux-native tools. The instructions assume familiarity with PowerShell and Windows-centric workflows, with no guidance for Linux users or those preferring cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operations, as Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the preferred shell.
- Include Linux/Bash-specific instructions for tasks such as editing JSON files, running commands, and managing files.
- Avoid assuming the user is running commands from a Windows environment; clarify that steps work on all platforms or provide platform-specific notes where necessary.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Where possible, use neutral language (e.g., 'command-line interface' instead of 'PowerShell') unless the step is truly PowerShell-specific.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/monitor/enable-sap-insights.md
.../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 demonstrates a Windows bias by providing only PowerShell-based scripting examples for enabling access, referencing PowerShell and the Azure Cloud Shell's PowerShell environment explicitly, and omitting any Bash or Linux-native command-line alternatives. The quickstart links also mention PowerShell before the Azure portal, and there are no Linux-specific instructions or parity in tooling guidance.
Recommendations
- Provide equivalent Bash or Azure CLI script examples for Linux users alongside PowerShell examples.
- Include instructions for using the Azure Cloud Shell in Bash mode, not just PowerShell.
- Ensure that quickstart and how-to links reference both PowerShell and Bash/Azure CLI guides equally, or mention the portal first as a neutral option.
- Explicitly state that the onboarding script or process can be performed from Linux environments, and provide any necessary modifications or prerequisites.
- Add screenshots or walkthroughs that show the process from a Linux terminal or Bash Cloud Shell, not just PowerShell.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/exchange-online-integration-sap-email-outbound.md
...oads/exchange-online-integration-sap-email-outbound.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft 365 Admin Center, Exchange Admin Center, and PowerShell for configuration steps, with no mention of Linux-based tools or command-line alternatives. All screenshots and step-by-step instructions assume a Windows/Microsoft ecosystem, and there are no examples or guidance for performing equivalent tasks from Linux environments or using cross-platform tools.
Recommendations
- Provide Linux-based examples for key steps, such as using curl, openssl, or Linux mail clients to test SMTP connectivity instead of only referencing ping/telnet.
- Include instructions for configuring SMTP relay and authentication using Linux-based mail transfer agents (e.g., Postfix, Exim, or Sendmail) as the intermediary relay server.
- Offer PowerShell alternatives only alongside equivalent Bash or shell script examples for tasks like enabling SMTP AUTH or retrieving public IP addresses.
- Reference cross-platform tools (e.g., Azure CLI, REST APIs) for administrative tasks instead of only the Microsoft 365 Admin Center or Exchange Admin Center GUIs.
- Add a section or callouts specifically addressing Linux-based SAP deployments and their integration with Exchange Online.
Sap
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/large-instances/hana-connect-vnet-express-route.md
...sap/large-instances/hana-connect-vnet-express-route.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell instructions. The text refers to PowerShell as the primary scripting environment for automation, and there are no Linux-native tools or workflows mentioned. Although the service is for 'virtual-machines-linux', the documentation assumes the user is operating from a Windows or PowerShell environment. The Azure portal is mentioned, but when it comes to scripting, only PowerShell is covered.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Explicitly mention that all steps can be performed from Linux or macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where possible, include Bash shell script examples or guidance for Linux users.
- Reorder instructions or provide parallel sections so that Linux-native (CLI/Bash) instructions are not always secondary to Windows/PowerShell.
- Clarify in the prerequisites or introduction that the instructions are not limited to Windows environments, and highlight cross-platform options.