Skip to content

Commit 53097a8

Browse files
authored
Merge pull request #296580 from imnotfromhere/main
Spin off Troubleshooting page from Azure Enhanced Monitoring Extension for SAP
2 parents 9584e06 + cecc433 commit 53097a8

File tree

5 files changed

+136
-99
lines changed

5 files changed

+136
-99
lines changed

articles/sap/workloads/deployment-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -509,7 +509,7 @@ This section has detailed steps for doing specific tasks in the configuration an
509509

510510
### <a name="31d9ecd6-b136-4c73-b61e-da4a29bbc9cc"></a>Join a VM to an on-premises domain (Windows only)
511511

512-
If you deploy SAP VMs in a cross-premises scenario, where on-premises Active Directory and DNS are extended in Azure, it's expected that the VMs are joining an on-premises domain. The detailed steps you take to join a VM to an on-premises domain, and the additional software required to be a member of an on-premises domain, varies by customer. Usually, to join a VM to an on-premises domain, you need to install additional software, like antimalware software, and backup or monitoring software.
512+
If you deploy SAP VMs in a cross-premises scenario, where on-premises Active Directory and DNS are extended in Azure, it's expected that the VMs are joining an on-premises domain. The detailed steps you take to join a VM to an on-premises domain, and the additional software required to be a member of an on-premises domain, varies by customer. Usually, to join a VM to an on-premises domain, you need to install additional software, like anti-malware software, and backup or monitoring software.
513513

514514
In this scenario, you also need to make sure that if Internet proxy settings are forced when a VM joins a domain in your environment, the Windows Local System Account (S-1-5-18) in the Guest VM has the same proxy settings. The easiest option is to force the proxy by using a domain Group Policy, which applies to systems in the domain.
515515

@@ -596,7 +596,7 @@ Set the following parameters:
596596

597597
If you want to use the Azure repositories, make sure that the traffic to these repositories isn't going through your on-premises intranet. If you created user-defined routes to enable forced tunneling, make sure that you add a route that routes traffic to the repositories directly to the Internet, and not through your site-to-site VPN connection.
598598

599-
The VM Extension for SAP also needs to be able to access the internet. Make sure to install the new VM Extension for SAP and follow the steps in [Configure the Azure VM extension for SAP solutions with Azure CLI](vm-extension-for-sap-new.md#fa4428b9-bed6-459a-9dfb-74cc27454481) in the VM Extension for SAP installation guide to configure the proxy.
599+
The VM Extension for SAP also needs to be able to access the internet. Make sure to install the new VM Extension for SAP and follow the steps in [Configure the Azure VM extension for SAP solutions](vm-extension-for-sap-new.md#configure) in the VM Extension for SAP installation guide to configure the proxy.
600600

601601
* **SLES**
602602

articles/sap/workloads/get-started.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Besides hosting SAP NetWeaver and S/4HANA scenarios with the different DBMS on A
1818

1919
We just announced our new services of Azure Center for SAP solutions and Azure Monitor for SAP solutions 2.0 entering the public preview stage. These services give you the possibility to deploy SAP workload on Azure in a highly automated manner in an optimal architecture and configuration. And monitor your Azure infrastructure, OS, DBMS, and ABAP stack deployments on one single pane of glass.
2020

21-
For customers and partners who are focused on deploying and operating their assets in public cloud through Terraform and Ansible, use our SAP on Azure Deployment Automation Framework to jump start your SAP deployments into Azure using our public Terraform and Ansible modules on [github](https://github.com/Azure/sap-automation).
21+
For customers and partners who are focused on deploying and operating their assets in public cloud through Terraform and Ansible, use our SAP on Azure Deployment Automation Framework to jump start your SAP deployments into Azure using our public Terraform and Ansible modules on [GitHub](https://github.com/Azure/sap-automation).
2222

2323
Hosting SAP workload scenarios in Azure also can create requirements of identity integration and single sign-on. This situation can occur when you use Microsoft Entra ID to connect different SAP components and SAP software-as-a-service (SaaS) or platform-as-a-service (PaaS) offers. A list of such integration and single sign-on scenarios with Microsoft Entra ID and SAP entities is described and documented in the section "Microsoft Entra SAP identity integration and single sign-on."
2424

@@ -55,8 +55,10 @@ In the SAP workload documentation space, you can find the following areas:
5555

5656
## Change Log
5757

58-
- March 31, 2025: Updated Azure NetApp Files Application Volume Group guideliness for SAP HANA in [FAQs for Virtual Machine Scale Set for SAP workload](./virtual-machine-scale-set-sap-faq.md)
58+
59+
- March 31, 2025: Updated Azure NetApp Files Application Volume Group guidelines for SAP HANA in [FAQs for Virtual Machine Scale Set for SAP workload](./virtual-machine-scale-set-sap-faq.md)
5960
- March 27, 2025: Update meta attributes for health-azure-events resource and clone, to correctly operate with unhealthy nodes with pacemaker versions 2.1.3 and higher. Documents [Set up Pacemaker on Red Hat Enterprise Linux in Azure](./high-availability-guide-rhel-pacemaker.md) and [Set up Pacemaker on SUSE Linux Enterprise Server in Azure](./high-availability-guide-suse-pacemaker.md).
61+
- March 20, 2025: Spun off troubleshooting section from [New Version of Azure VM extension for SAP solutions](./vm-extension-for-sap-new.md) to its own article: [Troubleshooting the Azure VM Extension for SAP](./vm-extension-for-sap-troubleshooting.md) and added tab panels to [New Version of Azure VM extension for SAP solutions](./vm-extension-for-sap-new.md) for better readability.
6062
- November 19, 2024: Update parameter `enque/encni/set_so_keepalive` to uppercase, as the parameter is case sensitive. Updated in [SAP workloads on Azure: planning and deployment checklist](deployment-checklist.md),[HA for SAP NW on Azure VMs on RHEL multi-SID guide](./high-availability-guide-rhel-multi-sid.md), [Azure VMs high availability for SAP NW on RHEL with Azure NetApp Files](./high-availability-guide-rhel-netapp-files.md),[Azure VMs high availability for SAP NW on RHEL with NFS on Azure Files](./high-availability-guide-rhel-nfs-azure-files.md),[HA for SAP NW on Azure VMs on RHEL for SAP applications](./high-availability-guide-rhel.md),[Azure VMs high availability for SAP NetWeaver on SLES multi-SID guide](./high-availability-guide-suse-multi-sid.md), [Azure VMs high availability for SAP NW on SLES with NFS on Azure Files](./high-availability-guide-suse-netapp-files.md),[Azure VMs high availability for SAP NW on SLES with NFS on Azure Files](./high-availability-guide-suse-nfs-azure-files.md), [Azure VMs high availability for SAP NetWeaver on SLES for SAP Applications with simple mount and NFS](./high-availability-guide-suse-nfs-simple-mount.md),[Azure VMs high availability for SAP NetWeaver on SLES](./high-availability-guide-suse.md),[HA for SAP NetWeaver on Azure VMs on Windows with Azure NetApp Files(SMB)](./high-availability-guide-windows-netapp-files-smb.md),[SAP ASCS/SCS instance multi-SID high availability with Windows server failover clustering and Azure shared disk](./sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md),[SAP ASCS/SCS installation on Windows with file share](sap-high-availability-installation-wsfc-file-share.md),[SAP ASCS/ERS installation on Windows with shared disk](sap-high-availability-installation-wsfc-shared-disk.md).
6163
- November 5, 2024: Add missing step to start HANA [High availability of SAP HANA on Azure VMs on RHEL](./sap-hana-high-availability-rhel.md).
6264
- November 1, 2024: Adding HANA high-availability hook ChkSrv for [dying indexserver for RHEL based cluster setups](./sap-hana-high-availability-rhel.md#implement-sap-hana-system-replication-hooks).

articles/sap/workloads/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,12 @@ items:
4747
items:
4848
- name: Prerequisites Azure VM Extension for SAP
4949
href: vm-extension-for-sap.md
50-
- name: Standard version of Azure VM Extension for SAP
51-
href: vm-extension-for-sap-standard.md
5250
- name: New version of Azure VM Extension for SAP
5351
href: vm-extension-for-sap-new.md
52+
- name: Troubleshoot the Azure VM Extension for SAP
53+
href: vm-extension-for-sap-troubleshooting.md
54+
- name: Standard version of Azure VM Extension for SAP
55+
href: vm-extension-for-sap-standard.md
5456
- name: SAP BOBI platform on Azure
5557
items:
5658
- name: SAP BOBI planning and implementation guide on Azure

0 commit comments

Comments
 (0)