Merge pull request #250232 from divargas-msft/main

Updating high-availability-guide-rhel-pacemaker.md and high-availability-guide-suse-pacemaker.md

Author: prmerger-automator[bot]

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

@@ -293,7 +293,7 @@ Follow these steps to create a service principal, if not using managed identity.
 6. Select Application Type "Web", enter a sign-on URL (for example http:\//localhost) and click Add.
    The sign-on URL isn't used and can be any valid URL.
 7. Select Certificates and Secrets, then click New client secret.
-8. Enter a description for a new key, select "Never expires" and click Add.
+8. Enter a description for a new key, select "Two years" and click Add.
 9. Make a node the Value. It is used as the **password** for the service principal.
 10. Select Overview. Make a note the Application ID. It's used as the username (**login ID** in the steps below) of the service principal.
 

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

@@ -559,7 +559,7 @@ To create a service principal, do the following:
 5. For **Application type**, select **Web**, enter a sign-on URL (for example, *http://localhost*), and then select **Add**.  
    The sign-on URL isn't used and can be any valid URL.
 6. Select **Certificates and secrets**, and then select **New client secret**.
-7. Enter a description for a new key, select **Never expires**, and then select **Add**.
+7. Enter a description for a new key, select **Two years**, and then select **Add**.
 8. Write down the value, which you'll use as the password for the service principal.
 9. Select **Overview**, and then write down the application ID, which you'll use as the username of the service principal.