resolving merge conflict

Author: msftrobiro

articles/virtual-machines/workloads/sap/high-availability-guide-rhel-pacemaker.md

@@ -237,7 +237,7 @@ To create a managed identity (MSI), [create a system-assigned](/azure/active-dir
 ### Using Service Principal
 Follow these steps to create a service principal, if not using managed identity.
 
-1. Go to [Azure portal](https://portal.azure.com).
+1. Go to the [Azure portal](https://portal.azure.com).
 1. Open the Azure Active Directory blade  
    Go to Properties and make a note of the Directory ID. This is the **tenant ID**.
 1. Click App registrations

articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md

@@ -637,10 +637,6 @@ Make sure to assign the custom role to the service principal at all VM (cluster
    >[!IMPORTANT]
    > The installed version of the *fence-agents* package must be 4.4.0 or later to benefit from the faster failover times with the Azure fence agent, when a cluster node is fenced. If you're running an earlier version, we recommend that you update the package.  
 
-   >[!IMPORTANT]
-   > If using managed identity, the installed version of the *fence-agents* package must be fence-agents 4.5.2+git.1592573838.1eee0863 or later. Earlier versions will not work correctly with a managed identity configuration.  
-   > Currently only SLES 15 SP1 and older are supported for managed identity configuration.
-
 1. **[A]** Install the Azure Python SDK and Azure Identity Python module.  
 
     Install the Azure Python SDK on SLES 12 SP4 or SLES 12 SP5: