Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Standard version of Azure VM extension for SAP solutions description: Learn how to deploy the Azure Standard VM extension for SAP. services: virtual-machines-linux,virtual-machines-windows ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-content ms.assetid: 1c4f1951-3613-4a5a-a0af-36b85750c84e ms.service: sap-on-azure ms.subservice: sap-vm-workloads ms.topic: article ms.tgt_pltfrm: vm-linux manager: juergent author: OliverDoMS ms.author: oldoll ms.date: 03/12/2026 # Customer intent: "As an IT administrator managing SAP solutions, I want to configure the Azure VM extension for SAP using PowerShell or Azure CLI, so that I can effectively monitor and collect performance metrics for my SAP applications running on Azure VMs." --- # Standard version of Azure VM extension for SAP solutions There are two versions of the Azure virtual machine (VM) extension. This article covers the **Standard** version of the Azure VM extension for SAP. For guidance on how to install the new version, see [New Version of Azure VM extension for SAP solutions][new-extension]. ## Prerequisites Make sure to uninstall the VM extension before switching between the standard and the new version of the Azure extension for SAP. The Azure PowerShell module or Azure CLI must be installed. See the following instructions: # [Azure PowerShell](#tab/azure-powershell) Follow the steps described in [Install the Azure PowerShell module](/powershell/azure/install-azure-powershell). Check frequently for updates to the Azure PowerShell cmdlets. Unless stated otherwise in SAP Note [1928533] or SAP Note [2015553], we recommend that you work with the latest version of Azure PowerShell cmdlets. To check the version of the Azure PowerShell cmdlets that are installed on your computer, run the following command: ```azurepowershell (Get-Module Az.Compute).Version ``` ### [Azure CLI](#tab/azure-cli) Follow the steps described in [Install the Azure CLI](/cli/azure/install-azure-cli). Check frequently for updates to the Azure CLI. To check the version of Azure CLI that is installed on your computer, run the following command: ```console az --version ``` --- > [!NOTE] > **General support statement:** > > Support for the Azure extension for SAP is provided through SAP support channels. If you need assistance with the Azure VM extension for SAP solutions, open a support case with SAP Support. ## Configure the Azure VM extension for SAP solutions # [Azure PowerShell](#tab/azure-powershell) 1. Make sure that you installed the latest version of the Azure PowerShell cmdlet. For more information, see [Deploying Azure PowerShell cmdlets][deployment-guide-4.1] 1. Run the following cmdlet. For a list of available environments, run `Get-AzEnvironment`. If you want to use global Azure, your environment is **AzureCloud**. For Microsoft Azure operated by 21Vianet, select **AzureChinaCloud**. ```azurepowershell $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> ``` After you enter your account data, the script deploys the required extensions and enables the required features. The script can take several minutes. For more information, see [Set-AzVMAEMExtension][msdn-set-Azvmaemextension]. ![A screenshot of an Azure PowerShell script successfully installing the Standard VM extension.][deployment-guide-figure-900] The `Set-AzVMAEMExtension` configuration does all the steps to configure host data collection for SAP. The script output includes the following information: * Confirmation that data collection for the OS disk and all other data disks are configured. * The next two messages confirm the configuration of Storage Metrics for a specific storage account. * One line of output gives the status of the actual update of the VM extension for SAP configuration. * Another line of output confirms that the configuration is deployed or updated. * The last line of output is informational. It shows your options for testing the VM extension for SAP configuration. * Verify that the Azure VM extension for SAP configuration is complete and the Azure infrastructure is delivering the required data by running the [Readiness check][readiness-check]. * Wait 15-30 minutes for Azure Diagnostics to collect the relevant data. # [Azure CLI](#tab/azure-cli) 1. Make sure that you installed the latest version of the Azure CLI. For more information, see [Deploy Azure CLI][deploy-cli] 1. Sign in with your Azure account: ```azurecli az login ``` 1. Install the Azure CLI Azure Event Management (AEM) extension. Ensure that you use version 0.2.2 or later. ```azurecli az extension add --name aem ``` 1. Enable the extension ```azurecli az vm aem set -g <resource-group-name> -n <vm name> ``` 1. Verify that the Azure extension for SAP is active on the Azure Linux VM. Check whether the file `/var/lib/AzureEnhancedMonitor/PerfCounters` exists. If it exists, at a command prompt, run this command to display information collected by the Azure extension for SAP: ```console cat /var/lib/AzureEnhancedMonitor/PerfCounters ``` The output looks like this: ```output ... 2;cpu;Current Hw Frequency;;0;2194.659;MHz;60;1444036656;saplnxmon; 2;cpu;Max Hw Frequency;;0;2194.659;MHz;0;1444036656;saplnxmon; ... ``` --- ## Update the configuration of Azure extension for SAP Update the configuration of Azure extension for SAP in any of the following scenarios: * The joint Microsoft/SAP team extends the capabilities of the VM extension and requests more or fewer counters. * Microsoft introduces a new version of the underlying Azure infrastructure that delivers the data, and the Azure extension for SAP needs to be adapted to those changes. * You mount extra data disks to your Azure VM or you remove a data disk. In this scenario, update the collection of storage-related data. Changing your configuration by adding or deleting endpoints or by assigning IP addresses to a VM doesn't affect the extension configuration. * You change the size of your Azure VM, for example, from size A5 to any other VM size. * You add new network interfaces to your Azure VM. To update settings, update configuration of Azure extension for SAP by following the steps in [Configure the Azure VM extension for SAP solutions with Azure CLI][configure-linux] or [Configure the Azure VM extension for SAP solutions with PowerShell][configure-windows]. ## Checks and troubleshooting After you deploy your Azure VM and set up the relevant Azure extension for SAP, check whether all the components of the extension are working as expected. Run the readiness check for the Azure extension for SAP as described in [Readiness check][readiness-check]. If all readiness check results are positive and all relevant performance counters appear OK, the Azure extension for SAP is set up successfully. You can proceed with the installation of SAP Host Agent as described in the SAP Notes in [SAP resources][deployment-guide-2.2]. If the readiness check indicates that counters are missing, run the health check for the Azure extension for SAP, as described in [Health check for the Azure extension for SAP configuration][healthcheck]. For more troubleshooting options, see [Troubleshooting for Windows][troubleshoot-windows] or [Troubleshooting for Linux][troubleshoot-linux]. ### 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. # [Windows VM](#tab/windows-vm) 1. Sign in to the Azure VM (using an admin account isn't necessary). 1. Open a Command Prompt window. 1. At the command prompt, change the directory to the installation folder of the Azure extension for SAP: ``` cd "C:\Packages\Plugins\Microsoft.AzureCAT.AzureEnhancedMonitoring.MonitorX64Windows\<version>\drop" ``` The `<version>` in the path to the extension might vary. If you see folders for multiple versions of the extension in the installation folder, check the configuration of the AzureEnhancedMonitoring Windows service, and then switch to the folder indicated as *Path to executable*. ![A screenshot of the properties dialog window of the Azure Enhanced Monitor service running the Azure VM extension for SAP.][deployment-guide-figure-1000] 1. At the command prompt, run `azperflib.exe` without any parameters. > [!NOTE] > `Azperflib.exe` runs in a loop and updates the collected counters every 60 seconds. To end the loop, close the command prompt window. Azperflib.exe is a component that can't be used for own purposes. It's a component that delivers Azure infrastructure data related to the VM for the SAP Host Agent exclusively. If the Azure extension for SAP isn't installed, or the AzureEnhancedMonitoring service isn't running, the extension wasn't configured correctly. For detailed information about how to troubleshoot the extension, see [Troubleshooting for Windows][troubleshoot-windows] or [Troubleshooting for Linux][troubleshoot-linux]. #### Check the output of azperflib.exe The `azperflib.exe` output shows all populated Azure performance counters for SAP. At the bottom of the list of collected counters, a summary and health indicator show the status of Azure extension for SAP. ![A screenshot of azperflib health summary indicating no issues were encountered.][deployment-guide-figure-1100] Check the result returned for the **Counters total** output, which is reported as empty, and for **Health status**, shown in the preceding figure. Interpret the resulting values as follows: | Azperflib result values | Azure extension for SAP health status | | --- | --- | | **API Calls - not available** | Counters that aren't available might be either not applicable to the VM configuration, or are errors. See **Health status**. | | **Counters total - empty** | The following two Azure storage counters can be empty: <br><ul><li>Storage Read Op Latency Server msec</li><li>Storage Read Op Latency E2E msec</li></ul><br>All other counters must have values. | | **Health status** | Only OK if return status shows **OK**. | | **Diagnostics** | Detailed information about health status. | If the **Health status** value isn't **OK**, follow the instructions in [Health check for the Azure extension for SAP configuration][healthcheck]. # [Linux VM](#tab/linux-vm) 1. Connect to the Azure VM by using SSH. 1. Check the output of the Azure extension for SAP. 1. Run: ```bash more /var/lib/AzureEnhancedMonitor/PerfCounters ``` **Expected result**: Returns list of performance counters. The file shouldn't be empty. 1. Run: ```bash cat /var/lib/AzureEnhancedMonitor/PerfCounters | grep Error ``` **Expected result**: Returns one line where the error is **none**, for example, **3;config;Error;;0;0;none;0;1456416792;tst-servercs;**. 1. Run: ```bash more /var/lib/AzureEnhancedMonitor/LatestErrorRecord ``` **Expected result**: Returns as empty or doesn't exist. If the preceding check wasn't successful, run these extra checks: 1. Make sure that the `waagent` is installed and enabled. 1. Run: ```bash sudo ls -al /var/lib/waagent/ ``` **Expected result**: Lists the content of the `waagent` directory. 1. Run: ```bash 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. 1. Run: ```bash sudo sh -c 'ls -al /var/lib/waagent/Microsoft.OSTCExtensions.AzureEnhancedMonitorForLinux-*/' ``` **Expected result**: Lists the content of the Azure extension for SAP directory. 1. Run: ```bash ps -ax | grep AzureEnhanced ``` **Expected result**: Displays one entry similar to: `python /var/lib/waagent/Microsoft.OSTCExtensions.AzureEnhancedMonitorForLinux-2.0.0.2/handler.py daemon`. 1. Install SAP Host Agent as described in SAP Note [1031096], and check the output of `saposcol`. 1. Run: ```bash /usr/sap/hostctrl/exe/saposcol -d ``` 1. Run: ```bash dump ccm ``` 1. Check whether the **Virtualization_Configuration\Enhanced Monitoring Access** metric is `true`. If you already have an SAP NetWeaver Advanced Business Application Programming (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 for Linux][troubleshoot-linux] or [Troubleshooting for Windows][troubleshoot-windows]. --- ## 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 article. Check whether the Azure infrastructure and the Azure extension for SAP are configured correctly. # [Azure PowerShell](#tab/azure-powershell) 1. Make sure that you installed the latest version of the Azure PowerShell cmdlet, as described in [Deploying Azure PowerShell cmdlets][deployment-guide-4.1]. 1. Run the following 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**. ```powershell $env = Get-AzEnvironment -Name <name of the environment> Connect-AzAccount -Environment $env Set-AzContext -SubscriptionName <subscription name> Test-AzVMAEMExtension -ResourceGroupName <resource group name> -VMName <virtual machine name> ``` 1. The script tests the configuration of the VM you select. ![A screenshot of successfully running a health check of the Azure extension for SAP.][deployment-guide-figure-1300] Make sure that every health check result is **OK**. If some checks don't display **OK**, run the update cmdlet as described in [Configure the Azure VM extension for SAP solutions with Azure CLI][configure-linux] or [Configure the Azure VM extension for SAP solutions with PowerShell][configure-windows]. Wait 15 minutes, and repeat the checks described in [Readiness check][readiness-check] and this chapter. If the checks still indicate a problem with some or all counters, see [Troubleshooting for Linux][troubleshoot-linux] or [Troubleshooting for Windows][troubleshoot-windows]. > [!NOTE] > You can experience some warnings in cases where you use Managed Standard Azure Disks. Warnings are displayed instead of the tests returning **OK**. Warnings are normal and intended for that disk type. See also [Troubleshooting for Linux][troubleshoot-linux] or [Troubleshooting for Windows][troubleshoot-windows]. # [Azure CLI](#tab/azure-cli) 1. Install [Azure CLI 2.0][azure-cli-2]. Ensure that you use at least version 2.19.1 or later (use the latest version). 1. Sign in with your Azure account: ```azurecli az login ``` 1. Install the Azure CLI AEM extension. Ensure that you use version 0.2.2 or later. ```azurecli az extension add --name aem ``` 1. Verify the installation of the extension: ```azurecli az vm aem verify -g <resource-group-name> -n <vm name> ``` The script tests the configuration of the VM you select. Make sure that every health check result is **OK**. If some checks don't display **OK**, run the update cmdlet as described in [Configure the Azure VM extension for SAP solutions with Azure CLI][configure-linux] or [Configure the Azure VM extension for SAP solutions with PowerShell][configure-windows]. Wait 15 minutes, and repeat the checks described in [Readiness check][readiness-check] and this chapter. If the checks still indicate a problem with some or all counters, see [Troubleshooting for Linux][troubleshoot-linux] or [Troubleshooting for Windows][troubleshoot-windows]. --- ## Troubleshooting # [Windows VM](#tab/windows-vm) ### Azure performance counters don't show up at all The AzureEnhancedMonitoring Windows service collects performance metrics in Azure. If the service wasn't installed correctly or if it isn't running in your VM, no performance metrics can be collected. ### The installation directory of the Azure extension for SAP is empty **Issue**: The installation directory `C:\Packages\Plugins\Microsoft.AzureCAT. AzureEnhancedMonitoring.AzureCATExtensionHandler\<version>\drop` is empty. **Solution**: The extension isn't installed. Determine whether it's a proxy issue (as described earlier). You might need to restart the machine or rerun the `Set-AzVMAEMExtension` configuration script. ### Service for Azure extension for SAP doesn't exist **Issue**: The AzureEnhancedMonitoring Windows service doesn't exist. `Azperflib.exe` output throws an error: ![A screenshot of azperflib indicating that the service of the Azure extension for SAP isn't running.][deployment-guide-figure-1400] **Solution**: If the service doesn't exist, the Azure extension for SAP wasn't installed correctly. Redeploy the extension as described in [Configure the Azure VM extension for SAP solutions with Azure CLI][configure-linux] or [Configure the Azure VM extension for SAP solutions with PowerShell][configure-windows]. After you deployed the extension, check again whether the Azure performance counters are provided in the Azure VM. ### Service for Azure extension for SAP exists but fails to start **Issue**: The AzureEnhancedMonitoring Windows service exists and is enabled, but fails to start. For more information, check the Application event log. **Solution**: The configuration is incorrect. Restart the Azure extension for SAP in the VM, as described in Configure the Azure extension for SAP. ### Some Azure performance counters are missing The AzureEnhancedMonitoring Windows service collects performance metrics in Azure. The service gets data from several sources. Some configuration data is collected locally, and some performance metrics are read from Azure Diagnostics. Storage counters are used from your logging on the storage subscription level. If troubleshooting by using SAP Note [1999351] doesn't resolve the issue, rerun the `Set-AzVMAEMExtension` configuration script. You might have to wait an hour because storage analytics or diagnostics counters might not be created immediately after they're enabled. If the problem persists, open an SAP customer support message on the component BC-OP-NT-AZR for Windows or BC-OP-LNX-AZR for a Linux VM. # [Linux VM](#tab/linux-vm) ### Azure performance counters don't show up at all A daemon collects the performance metrics in Azure. If the daemon isn't running, no performance metrics can be collected. ### The installation directory of the Azure extension for SAP is empty **Issue**: The directory `\var\lib\waagent\` doesn't have a subdirectory for the Azure extension for SAP. **Solution**: The extension isn't installed. Determine whether it's a proxy issue (as described earlier). You might need to restart the machine and/or rerun the `Set-AzVMAEMExtension` configuration script. ### The execution of Set-AzVMAEMExtension and Test-AzVMAEMExtension show warning messages stating that Standard Managed Disks aren't supported **Issue**: When you execute `Set-AzVMAEMExtension` or `Test-AzVMAEMExtension`, messages like these are shown: ``` WARNING: [WARN] Standard Managed Disks are not supported. Extension will be installed but no disk metrics will be available. WARNING: [WARN] Standard Managed Disks are not supported. Extension will be installed but no disk metrics will be available. WARNING: [WARN] Standard Managed Disks are not supported. Extension will be installed but no disk metrics will be available. ``` When you run `azperfli.exe`, as described earlier, you can get a result that's indicating an unhealthy state. **Solution**: You receive these messages because the Standard Managed Disks aren't delivering the APIs used by the SAP extension for SAP to check on statistics of the Standard Azure Storage Accounts. Don't worry about these messages. The reason for introducing the collection of data for Standard Disk Storage accounts was throttling inputs and outputs that occurred frequently. Managed disks avoid such throttling by limiting the number of disks in a storage account. Therefore, not having that type of that data isn't critical. ### Some Azure performance counters are missing A daemon collects performance metrics in Azure, which retrieves data from several sources. Some configuration data is collected locally, and some performance metrics are read from Azure Diagnostics. Storage counters come from the logs in your storage subscription. For a complete and up-to-date list of known issues, see SAP Note [1999351], which has more troubleshooting information for Azure extension for SAP. If troubleshooting by using SAP Note [1999351] doesn't resolve the issue, rerun the `Set-AzVMAEMExtension` configuration script as described in [Configure the Azure VM extension for SAP solutions with Azure CLI][configure-linux] or [Configure the Azure VM extension for SAP solutions with PowerShell][configure-windows]. You might have to wait for an hour because storage analytics or diagnostics counters might not be created immediately after they're enabled. If the problem persists, open an SAP customer support message on the component BC-OP-NT-AZR for Windows or BC-OP-LNX-AZR for a Linux VM. --- ## Azure extension error codes | Error ID | Error description | Solution | |---|---|---| | <a name="cfg_018"></a>cfg/018 | App configuration is missing. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_019"></a>cfg/019 | No deployment ID in app config. | [contact support][deployment-guide-contact-support] | | <a name="cfg_020"></a>cfg/020 | No RoleInstanceId in app config. | [contact support][deployment-guide-contact-support] | | <a name="cfg_022"></a>cfg/022 | No RoleInstanceId in app config. | [contact support][deployment-guide-contact-support] | | <a name="cfg_031"></a>cfg/031 | Cannot read Azure configuration. | [contact support][deployment-guide-contact-support] | | <a name="cfg_021"></a>cfg/021 | App configuration file is missing. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_015"></a>cfg/015 | No VM size in app config. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_016"></a>cfg/016 | GlobalMemoryStatusEx counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_023"></a>cfg/023 | MaxHwFrequency counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_024"></a>cfg/024 | NIC counters failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_025"></a>cfg/025 | Disk mapping counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_026"></a>cfg/026 | Processor name counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_027"></a>cfg/027 | Disk mapping counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_038"></a>cfg/038 | The metric 'Disk type' is missing in the extension configuration file config.xml. 'Disk type' along with some other counters was introduced in v2.2.0.68 on December 12, 2015. If you deployed the extension before December 12, 2015, it uses the old configuration file. <br><br> The Azure extension framework automatically upgrades the extension to a newer version, but the config.xml remains unchanged. To update the configuration, download and execute the latest PowerShell setup script. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_039"></a>cfg/039 | No disk caching. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_036"></a>cfg/036 | No disk SLA throughput. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_037"></a>cfg/037 | No disk SLA IOPS. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_028"></a>cfg/028 | Disk mapping counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_029"></a>cfg/029 | Last hardware change counter failed. | [contact support][deployment-guide-contact-support] | | <a name="cfg_030"></a>cfg/030 | NIC counters failed | [contact support][deployment-guide-contact-support] | | <a name="cfg_017"></a>cfg/017 | Due to sysprep of the VM your Windows SID has changed. | [redeploy after sysprep][deployment-guide-redeploy-after-sysprep] | | <a name="str_007"></a>str/007 | Access to the storage analytics failed. <br /><br />As population of storage analytics data on a newly created VM may need up to half an hour, the error might disappear after some time. If the error still appears, re-run the setup script. | [run setup script][deployment-guide-run-the-script] | | <a name="str_010"></a>str/010 | No Storage Analytics counters. | [run setup script][deployment-guide-run-the-script] | | <a name="str_009"></a>str/009 | Storage Analytics failed. | [run setup script][deployment-guide-run-the-script] | | <a name="wad_004"></a>wad/004 | Bad WAD configuration. | [run setup script][deployment-guide-run-the-script] | | <a name="wad_002"></a>wad/002 | Unexpected WAD format. | [contact support][deployment-guide-contact-support] | | <a name="wad_001"></a>wad/001 | No WAD counters found. | [run setup script][deployment-guide-run-the-script] | | <a name="wad_040"></a>wad/040 | Stale WAD counters found. | [contact support][deployment-guide-contact-support] | | <a name="wad_003"></a>wad/003 | Cannot read WAD table. There is no connection to WAD table. There can be several causes of this:<br /><br /> 1) outdated configuration <br />2) no network connection to Azure <br />3) issues with WAD setup | [run setup script][deployment-guide-run-the-script]<br />[fix internet connection][deployment-guide-fix-internet-connection]<br />[contact support][deployment-guide-contact-support] | | <a name="prf_011"></a>prf/011 | Perfmon NIC metrics failed. | [contact support][deployment-guide-contact-support] | | <a name="prf_012"></a>prf/012 | Perfmon disk metrics failed. | [contact support][deployment-guide-contact-support] | | <a name="prf_013"></a>prf/013 | Some perfmon metrics failed. | [contact support][deployment-guide-contact-support] | | <a name="prf_014"></a>prf/014 | Perfmon failed to create a counter. | [contact support][deployment-guide-contact-support] | | <a name="cfg_035"></a>cfg/035 | No metric providers configured. | [contact support][deployment-guide-contact-support] | | <a name="str_006"></a>str/006 | Bad Storage Analytics config. | [run setup script][deployment-guide-run-the-script] | | <a name="str_032"></a>str/032 | Storage Analytics metrics failed. | [run setup script][deployment-guide-run-the-script] | | <a name="cfg_033"></a>cfg/033 | One of the metric providers failed. | [run setup script][deployment-guide-run-the-script] | | <a name="str_034"></a>str/034 | Provider thread failed. | [contact support][deployment-guide-contact-support] | ### Detailed guidelines on solutions provided #### Run the setup script Follow the steps in chapter [Configure the Azure extension for SAP][configure-windows] in this guide to install the extension again. Some counters might need up to 30 minutes for provisioning. If the errors don't disappear, [contact support][deployment-guide-contact-support]. #### Contact Support Unexpected error or there's no known solution. Collect the AzureEnhancedMonitoring_service.log file located in the folder `C:\Packages\Plugins\Microsoft.AzureCAT.AzureEnhancedMonitoring.AzureCATExtensionHandler\<version>\drop` (Windows) or `/var/log/azure/Microsoft.OSTCExtensions.AzureEnhancedMonitorForLinux` (Linux) and contact SAP support for further assistance. #### Redeploy after sysprep If you plan to build a generalized sysprep OS image (which can include SAP software), we recommend that this image doesn't include the Azure extension for SAP. You should install the Azure extension for SAP after the new instance of the generalized OS image is deployed. However, if your generalized and did a sysprep OS image already containing the Azure extension for SAP, you can apply the following workaround to reconfigure the extension on the newly deployed VM instance. On the newly deployed VM instance, delete the content of the following folders: * `C:\Packages\Plugins\Microsoft.AzureCAT.AzureEnhancedMonitoring.AzureCATExtensionHandler\<version>\RuntimeSettings` * `C:\Packages\Plugins\Microsoft.AzureCAT.AzureEnhancedMonitoring.AzureCATExtensionHandler\<version>\Status` * Follow the steps in chapter [Configure the Azure extension for SAP][configure-windows] in this guide to install the extension again. #### Fix internet connection The Microsoft Azure VM running the Azure extension for SAP requires access to the Internet. If this Azure VM is part of an Azure Virtual Network or of an on-premises domain, make sure that the relevant proxy settings are set. These settings must also be valid for the LocalSystem account to access the Internet. Follow chapter [Configure the proxy][configure-proxy] in this guide. In addition, if you need to set a static IP address for your Azure VM, don't set it manually inside the Azure VM, but set it using [Azure PowerShell](../../virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps.md), [Azure CLI](../../virtual-network/ip-services/virtual-networks-static-private-ip-arm-cli.md) [Azure portal](../../virtual-network/ip-services/virtual-networks-static-private-ip-arm-pportal.md). The static IP is propagated via the Azure DHCP service. Manually setting a static IP address inside the Azure VM isn't supported, and might lead to problems with the Azure extension for SAP. ## Next steps * [Azure Virtual Machines deployment for SAP NetWeaver](./deployment-guide.md) * [Azure Virtual Machines planning and implementation for SAP NetWeaver](./planning-guide.md) [new-extension]:vm-extension-for-sap-new.md (New Version of Azure VM extension for SAP solutions) [configure-windows]:vm-extension-for-sap-standard.md#configure-the-azure-vm-extension-for-sap-solutions (Configure the Azure VM extension for SAP solutions with PowerShell) [configure-linux]:vm-extension-for-sap-standard.md#configure-the-azure-vm-extension-for-sap-solutions (Configure the Azure VM extension for SAP solutions with Azure CLI) [configure-proxy]:deployment-guide.md#baccae00-6f79-4307-ade4-40292ce4e02d [troubleshoot-windows]:vm-extension-for-sap-standard.md#troubleshooting (Troubleshooting for Windows) [troubleshoot-linux]:vm-extension-for-sap-standard.md#troubleshooting (Troubleshooting for Linux) [healthcheck]:vm-extension-for-sap-standard.md#health-checks (Health check for the Azure extension for SAP configuration) [deployment-guide-4.1]:vm-extension-for-sap-standard.md#prerequisites (Deploying Azure PowerShell cmdlets) [deploy-cli]:vm-extension-for-sap-standard.md#prerequisites (Deploying Azure CLI) [deployment-guide-figure-1000]:media/virtual-machines-shared-sap-deployment-guide/1000-service-properties.png [deployment-guide-figure-1100]:media/virtual-machines-shared-sap-deployment-guide/1100-azperflib.png [azure-cli-2]:/cli/azure/install-azure-cli [msdn-set-Azvmaemextension]:/powershell/module/az.compute/set-azvmaemextension [deployment-guide-figure-900]:media/virtual-machines-shared-sap-deployment-guide/900-cmd-update-executed.png [readiness-check]:vm-extension-for-sap-standard.md#readiness-check (Readiness check) [deployment-guide-2.2]:deployment-guide.md#42ee2bdb-1efc-4ec7-ab31-fe4c22769b94 (SAP resources) [1031096]:https://launchpad.support.sap.com/#/notes/1031096 [deployment-guide-figure-1300]:media/virtual-machines-shared-sap-deployment-guide/1300-cmd-test-executed.png [deployment-guide-figure-1400]:media/virtual-machines-shared-sap-deployment-guide/1400-azperflib-error-servicenotstarted.png [1999351]:https://launchpad.support.sap.com/#/notes/1999351 [1928533]:https://launchpad.support.sap.com/#/notes/1928533 [2015553]:https://launchpad.support.sap.com/#/notes/2015553 [deployment-guide-contact-support]:vm-extension-for-sap-standard.md#contact-support (Troubleshooting Azure extension for SAP - Contact Support) [deployment-guide-run-the-script]:vm-extension-for-sap-standard.md#run-the-setup-script (Troubleshooting Azure extension for SAP - Run the setup script) [deployment-guide-redeploy-after-sysprep]:vm-extension-for-sap-standard.md#redeploy-after-sysprep (Troubleshooting Azure extension for SAP - Redeploy after sysprep) [deployment-guide-fix-internet-connection]:vm-extension-for-sap-standard.md#fix-internet-connection ( Troubleshooting Azure extension for SAP - Fix internet connection)