Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram23-0406

Author: tamram

articles/active-directory/hybrid/migrate-from-federation-to-cloud-authentication.md

@@ -94,7 +94,7 @@ Modern authentication clients (Office 2016 and Office 2013, iOS, and Android app
 
 To plan for rollback, use the [documented current federation settings](#document-current-federation-settings) and check the [federation design and deployment documentation](/windows-server/identity/ad-fs/deployment/windows-server-2012-r2-ad-fs-deployment-guide). 
 
-The rollback process should include converting managed domains to federated domains by using the [Convert-MSOLDomainToFederated](/powershell/module/msonline/convert-msoldomaintofederated) cmdlet. If necessary, configuring extra claims rules.
+The rollback process should include converting managed domains to federated domains by using the [Convert-MSOLDomainToFederated](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true) cmdlet. If necessary, configuring extra claims rules.
 
 ## Migration considerations 
 
@@ -136,7 +136,7 @@ The following table explains the behavior for each option. For more information,
 | rejectMfaByFederatedIdp | Azure AD always performs MFA and rejects MFA that federated identity provider performs. |
 
 >[!NOTE]
-> The **federatedIdpMfaBehavior** setting is an evolved version of the **SupportsMfa** property of the [Set-MsolDomainFederationSettings MSOnline v1 PowerShell cmdlet](/powershell/module/msonline/set-msoldomainfederationsettings). 
+> The **federatedIdpMfaBehavior** setting is an evolved version of the **SupportsMfa** property of the [Set-MsolDomainFederationSettings MSOnline v1 PowerShell cmdlet](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true). 
 
 For domains that have already set the **SupportsMfa** property, these rules determine how **federatedIdpMfaBehavior** and **SupportsMfa** work together:
 
@@ -251,9 +251,11 @@ Sign in to the [Azure portal](https://portal.azure.com/), browse to **Azure Acti
 
 4. On the **User sign-in** page:
 
-    - If you select **Pass-through authentication** option button, check **Enable single sign-on**, and then select **Next**.
+    - If you select **Pass-through authentication** option button, and if SSO is needed for Windows 7 and 8.1 devices, check **Enable single sign-on**, and then select **Next**.
 
-    -  If you select the **Password hash synchronization** option button, make sure to select the **Do not convert user accounts** check box. The option is deprecated. Check **Enable single sign-on**, and then select **Next**.
+    - If you select the **Password hash synchronization** option button, make sure to select the **Do not convert user accounts** check box. The option is deprecated. If SSO is needed for Windows 7 and 8.1 devices, check **Enable single sign-on**, and then select **Next**. 
+
+      Learn more: [Enable seamless SSO using PowerShell](how-to-connect-staged-rollout.md#pre-work-for-seamless-sso). 
 
       ![Check enable single sign-on on User sign-in page](media/deploy-cloud-user-authentication/user-sign-in.png)
 
@@ -268,6 +270,8 @@ Sign in to the [Azure portal](https://portal.azure.com/), browse to **Azure Acti
 
     The domain administrator credentials aren't stored in Azure AD Connect or Azure AD and get discarded when the process successfully finishes. They are  used to turn ON this feature.
 
+    Learn more: [Seamless SSO technical deep dive.](how-to-connect-sso-how-it-works.md) 
+
 6. On the **Ready to configure** page, make sure that the **Start the synchronization process when configuration completes** check box is selected. Then, select **Configure**.
 
     ![Ready to configure page](media/deploy-cloud-user-authentication/ready-to-configure.png)

articles/azure-cache-for-redis/cache-configure.md

@@ -203,7 +203,7 @@ The **maxfragmentationmemory-reserved** setting configures the amount of memory
 When choosing a new memory reservation value (**maxmemory-reserved** or **maxfragmentationmemory-reserved**), consider how this change might affect a cache that is already running with large amounts of data in it. For instance, if you have a 53-GB cache with 49 GB of data, then change the reservation value to 8 GB, this change drops the max available memory for the system down to 45 GB. If either your current `used_memory` or your `used_memory_rss` values are higher than the new limit of 45 GB, then the system will have to evict data until both `used_memory` and `used_memory_rss` are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](cache-how-to-monitor.md#create-your-own-metrics).
 
 > [!IMPORTANT]
-> The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available only for Standard and Premium caches.
+> The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available for Basic,Standard and Premium caches.
 >
 
 #### Keyspace notifications (advanced settings)

articles/cosmos-db/nosql/troubleshoot-changefeed-functions.md

@@ -5,7 +5,7 @@ author: ealsur
 ms.service: cosmos-db
 ms.subservice: nosql
 ms.custom: ignite-2022
-ms.date: 01/03/2023
+ms.date: 04/07/2023
 ms.author: maquaran
 ms.topic: troubleshooting
 ms.reviewer: mjbrown
@@ -42,17 +42,17 @@ The error text itself tells you which Azure Cosmos DB database and container the
 
 To resolve this issue:
 
-1. Verify the `ConnectionStringSetting` attribute and that it references a setting that exists in your Azure function app. 
+1. Verify the `Connection` attribute and that it references a setting that exists in your Azure function app.
 
    The value on this attribute shouldn't be the connection string itself, but the name of the configuration setting.
 
-1. Verify that the `databaseName` and `collectionName` values exist in your Azure Cosmos DB account. 
+1. Verify that the `databaseName` and `containerName` values exist in your Azure Cosmos DB account.
 
    If you're using automatic value replacement (using `%settingName%` patterns), make sure that the name of the setting exists in your Azure function app.
 
-1. If you don't specify a `LeaseCollectionName/leaseCollectionName` value, the default is `leases`. Verify that such a container exists. 
+1. If you don't specify a `LeaseContainerName/leaseContainerName` value, the default is `leases`. Verify that such a container exists. 
 
-   Optionally, you can set the `CreateLeaseCollectionIfNotExists` attribute in your trigger to `true` to automatically create it.
+   Optionally, you can set the `CreateLeaseContainerIfNotExists` attribute in your trigger to `true` to automatically create it.
 
 1. Verify your [Azure Cosmos DB account's firewall configuration](../how-to-configure-firewall.md) to ensure that it's not blocking the Azure function.
 
@@ -108,6 +108,8 @@ This scenario can have multiple causes. Consider trying any or all of the follow
 
 * The speed at which your trigger receives new changes is dictated by the speed at which you're processing them. Verify the function's [execution time, or duration](../../azure-functions/analyze-telemetry-data.md). If your function is slow, that will increase the time it takes for the trigger to get new changes. If you see a recent increase in duration, a recent code change might be affecting it. If the speed at which you're receiving operations on your Azure Cosmos DB container is faster than the speed of your trigger, it will keep lagging behind. You might want to investigate the function's code to determine the most time-consuming operation and how to optimize it.
 
+* You can use [Debug logs](how-to-configure-cosmos-db-trigger.md#enabling-trigger-specific-logs) to check the Diagnostics and verify if there are networking delays.
+
 ### Some changes are repeated in my trigger
 
 The concept of a *change* is an operation on a document. The most common scenarios where events for the same document are received are:
@@ -122,6 +124,8 @@ The concept of a *change* is an operation on a document. The most common scenari
 
 You might find that some of the changes that occurred in your Azure Cosmos DB container aren't being picked up by the Azure function. Or some changes are missing at the destination when you're copying them. If so, try the solutions in this section.
 
+* Make sure you have [logs](how-to-configure-cosmos-db-trigger.md#enabling-trigger-specific-logs) enabled. Verify no errors are happening during processing.
+
 * When your Azure function receives the changes, it often processes them and could, optionally, send the result to another destination. When you're investigating missing changes, make sure that you measure which changes are being received at the ingestion point (that is, when the Azure function starts), not at the destination.
 
 * If some changes are missing on the destination, this could mean that some error is happening during the Azure function execution after the changes were received.

articles/sap/workloads/get-started.md

@@ -14,7 +14,7 @@ ms.assetid: ad8e5c75-0cf6-4564-ae62-ea1246b4e5f2
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 03/27/2023
+ms.date: 04/06/2023
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 
@@ -65,6 +65,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- April 6, 2023: Updates for RHEL 9 in [Setting up Pacemaker on RHEL in Azure](./high-availability-guide-rhel-pacemaker.md)
 - March 26, 2023: Adding recommended sector size in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md)
 - March 1, 2023: Change in [HA for SAP HANA on Azure VMs on RHEL](./sap-hana-high-availability-rhel.md) to add configuration for cluster default properties
 - February 21, 2023: Correct link to HANA hardware directory in [SAP HANA infrastructure configurations and operations on Azure](./hana-vm-operations.md) and fixed a bug in [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md)

articles/vpn-gateway/openvpn-azure-ad-client-mac.md

@@ -5,7 +5,7 @@ titleSuffix: Azure VPN Gateway
 author: cherylmc
 ms.service: vpn-gateway
 ms.topic: conceptual
-ms.date: 11/22/2022
+ms.date: 04/07/2023
 ms.author: cherylmc
 
 ---
@@ -47,7 +47,7 @@ Before you can connect and authenticate using Azure AD, you must first configure
 1. Navigate to the profile file that you want to import, select it, then click **Open**.
 
    :::image type="content" source="media/openvpn-azure-ad-client-mac/import-2.png" alt-text="Screenshot of Azure VPN Client import clicking open.":::
-1. View the connection profile information, then click **Save**.
+1. View the connection profile information. Change the **Certificate Information** value to show **DigiCert Global Root G2**, rather than the default or blank, then click **Save**.
 
    :::image type="content" source="media/openvpn-azure-ad-client-mac/import-3.png" alt-text="Screenshot of Azure VPN Client saving the imported profile settings.":::
 1. In the VPN connections pane, select the connection profile that you saved. Then, click **Connect**.
@@ -63,7 +63,7 @@ Before you can connect and authenticate using Azure AD, you must first configure
 
    :::image type="content" source="media/openvpn-azure-ad-client-mac/add-1.png" alt-text="Screenshot of Azure VPN Client selecting Add.":::
 
-1. On the **Azure VPN Client** page, you can configure the profile settings.
+1. On the **Azure VPN Client** page, you can configure the profile settings. Change the **Certificate Information** value to show **DigiCert Global Root G2**, rather than the default or blank, then click **Save**.
 
    :::image type="content" source="media/openvpn-azure-ad-client-mac/add-2.png" alt-text="Screenshot of Azure VPN Client profile settings.":::