This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

Bias Analysis

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.
GitHub Create pull request

Scan History

Date Scan ID Status Bias Status
2025-09-11 00:00 #108 completed ✅ Clean
2025-08-11 00:00 #77 completed ✅ Clean
2025-08-10 00:00 #76 completed ✅ Clean
2025-08-09 00:00 #75 completed ✅ Clean
2025-08-08 00:00 #74 completed ✅ Clean
2025-08-07 00:00 #73 completed ✅ Clean
2025-08-06 00:00 #72 completed ✅ Clean
2025-08-05 00:00 #71 completed ✅ Clean
2025-08-03 00:00 #69 completed ✅ Clean
2025-08-01 00:00 #67 completed ✅ Clean
2025-07-31 00:00 #66 completed ✅ Clean
2025-07-30 00:00 #65 completed ✅ Clean
2025-07-29 00:01 #64 completed ✅ Clean
2025-07-28 00:00 #63 completed ✅ Clean
2025-07-27 00:00 #62 completed ✅ Clean
2025-07-26 00:01 #61 completed ✅ Clean
2025-07-25 00:00 #60 completed ✅ Clean
2025-07-24 00:00 #59 completed ✅ Clean
2025-07-23 00:00 #58 completed ✅ Clean
2025-07-22 00:01 #57 completed ✅ Clean
2025-07-13 21:37 #48 completed ❌ Biased
2025-07-12 23:44 #41 in_progress ❌ Biased

Flagged Code Snippets

(Get-Module Az.Compute).Version
$env = Get-AzEnvironment -Name <name of the environment> Connect-AzAccount -Environment $env Set-AzContext -SubscriptionName <subscription name> Set-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name> -InstallNewExtension
**Expected result**: Returns an XML document that contains the monitoring information of the virtual machine, its disks and network interfaces. If the preceding check was not successful, run these additional checks: 1. Make sure that the waagent is installed and enabled. a. Run `sudo ls -al /var/lib/waagent/` **Expected result**: Lists the content of the waagent directory. b. Run `ps -ax | grep waagent` **Expected result**: Displays one entry similar to: `python /usr/sbin/waagent -daemon` 1. Make sure that the Azure Extension for SAP is installed and running. a. Run `sudo sh -c 'ls -al /var/lib/waagent/Microsoft.AzureCAT.AzureEnhancedMonitoring.MonitorX64Linux-*/'` **Expected result**: Lists the content of the Azure Extension for SAP directory. b. Run `ps -ax | grep AzureEnhanced` **Expected result**: Displays one entry similar to: `/var/lib/waagent/Microsoft.AzureCAT.AzureEnhancedMonitoring.MonitorX64Linux-1.0.0.82/AzureEnhancedMonitoring -monitor` 1. Install SAP Host Agent as described in SAP Note [1031096], and check the output of `saposcol`. a. Run `/usr/sap/hostctrl/exe/saposcol -d` b. Run `dump ccm` c. Check whether the **Virtualization_Configuration\Enhanced Monitoring Access** metric is **true**. If you already have an SAP NetWeaver ABAP application server installed, open transaction ST06 and check whether monitoring is enabled. If any of these checks fail, and for detailed information about how to redeploy the extension, see [Troubleshooting][troubleshooting] ## <a name="e2d592ff-b4ea-4a53-a91a-e5521edb6cd1"></a>Health checks If some of the infrastructure data isn't delivered correctly as indicated by the tests described in [Readiness check][readiness-check], run the health checks described in this chapter to check whether the Azure infrastructure and the Azure Extension for SAP are configured correctly. ### [Azure PowerShell](#tab/powershell5) 1. Make sure that you have installed the latest version of the Azure PowerShell cmdlet (at least 4.3.0). 1. Run the following PowerShell cmdlet. For a list of available environments, run the cmdlet `Get-AzEnvironment`. To use global Azure, select the **AzureCloud** environment. For Microsoft Azure operated by 21Vianet, select **AzureChinaCloud**.
--- ## <a name="versions"></a> Versions of the VM Extension for SAP If you want to disable automatic updates for the VM extension or want to deploy a specific version of the extension, you can retrieve the available versions with Azure CLI or Azure PowerShell. ### [Azure PowerShell](#tab/powershell4)
--- ## <a name="readiness-check"></a>Readiness check This check makes sure that all performance metrics that appear inside your SAP application are provided by the underlying Azure Extension for SAP. ### Run the readiness check on a Windows VM 1. Sign in to the Azure virtual machine (using an admin account isn't necessary). 1. Open a web browser and navigate to `http://127.0.0.1:11812/azure4sap/metrics`. 1. The browser should display or download an XML file that contains the monitoring data of your virtual machine. If that isn't the case, make sure that the Azure Extension for SAP is installed. 1. Check the content of the XML file. The XML file that you can access at `http://127.0.0.1:11812/azure4sap/metrics` contains all populated Azure performance counters for SAP. It also contains a summary and health indicator of the status of Azure Extension for SAP. 1. Check the value of the **Provider Health Description** element. If the value is not **OK**, follow the instructions in chapter [Health checks][health-check]. ### Run the readiness check on a Linux VM 1. Connect to the Azure Virtual Machine by using SSH. 1. Check the output of the following command