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

Author: asudbring

.openpublishing.redirection.json

@@ -10979,6 +10979,17 @@
             "redirect_document_id": false
         },
         {
+            "source_path_from_root": "/articles/notification-hubs/notification-hubs-high-availability.md",
+            "redirect_url": "/azure/reliability/reliability-notification-hubs",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/reliability/reliability-guidance-overview.md",
+            "redirect_url": "/azure/reliability/overview-reliability-guidance",
+            "redirect_document_id": false
+        },
+        {
+
             "source_path_from_root": "/articles/event-hubs/move-across-regions.md",
             "redirect_url": "/azure/operational-excellence/relocation-event-hub",
             "redirect_document_id": false
@@ -11004,5 +11015,6 @@
             "redirect_document_id": false 
         }
 
+        
     ]
 }

articles/ai-services/speech-service/includes/how-to/compressed-audio-input/gstreamer-android.md

@@ -73,7 +73,7 @@ APP_PLATFORM = android-21
 APP_BUILD_SCRIPT = Android.mk
 ```
 
-You can build `libgstreamer_android.so` by using the following command on Ubuntu 18.04 or 20.04. The following command lines have been tested for [GStreamer Android version 1.14.4](https://gstreamer.freedesktop.org/data/pkg/android/1.14.4/gstreamer-1.0-android-universal-1.14.4.tar.bz2) with [Android NDK b16b.](https://dl.google.com/android/repository/android-ndk-r16b-linux-x86_64.zip)
+You can build `libgstreamer_android.so` by using the following command on Ubuntu 18.04 or 20.04. The following command lines have been tested for [GStreamer Android version 1.14.4](https://gstreamer.freedesktop.org/download/) with [Android NDK b16b.](https://dl.google.com/android/repository/android-ndk-r16b-linux-x86_64.zip)
 
 ```sh
 # Assuming wget and unzip are already installed on the system
@@ -83,7 +83,7 @@ wget https://dl.google.com/android/repository/android-ndk-r16b-linux-x86_64.zip
 unzip -q -o android-ndk-r16b-linux-x86_64.zip
 export PATH=$PATH:$(pwd)/android-ndk-r16b
 export NDK_PROJECT_PATH=$(pwd)/android-ndk-r16b
-wget https://gstreamer.freedesktop.org/data/pkg/android/1.14.4/gstreamer-1.0-android-universal-1.14.4.tar.bz2
+wget https://gstreamer.freedesktop.org/download/
 mkdir gstreamer_android
 tar -xjf gstreamer-1.0-android-universal-1.14.4.tar.bz2 -C $(pwd)/gstreamer_android/
 export GSTREAMER_ROOT_ANDROID=$(pwd)/gstreamer_android

articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md

@@ -125,7 +125,7 @@ let keepaliveAgent = new Agent({
     maxSockets: 32,
     maxFreeSockets: 10,
     timeout: 60000,
-    keepAliveTimeout: 300000
+    freeSocketTimeout: 300000
 });
 ```
 

articles/automation/update-management/overview.md

@@ -46,7 +46,7 @@ The following table summarizes the supported connected sources with Update Manag
 | Linux |Yes |Update Management collects information about system updates from Linux machines with the Log Analytics agent and installation of required updates on supported distributions.<br> Machines need to report to a local or remote repository. |
 | Operations Manager management group |Yes |Update Management collects information about software updates from agents in a connected management group.<br/><br/>A direct connection from the Operations Manager agent to Azure Monitor logs isn't required. Log data is forwarded from the management group to the Log Analytics workspace. |
 
-The machines assigned to Update Management report how up to date they are based on what source they are configured to synchronize with. Windows machines need to be configured to report to either [Windows Server Update Services](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) or [Microsoft Update](https://www.update.microsoft.com), and Linux machines need to be configured to report to a local or public repository. You can also use Update Management with Microsoft Configuration Manager, and to learn more see [Integrate Update Management with Windows Configuration Manager](mecmintegration.md). 
+The machines assigned to Update Management report how up to date they are based on what source they are configured to synchronize with. Windows machines need to be configured to report to either [Windows Server Update Services](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) or [Microsoft Update](https://support.microsoft.com/windows/update-windows-3c5ae7fc-9fb6-9af1-1984-b5e0412c556a), and Linux machines need to be configured to report to a local or public repository. You can also use Update Management with Microsoft Configuration Manager, and to learn more see [Integrate Update Management with Windows Configuration Manager](mecmintegration.md). 
 
 If the Windows Update Agent (WUA) on the Windows machine is configured to report to WSUS, depending on when WSUS last synchronized with Microsoft Update, the results might differ from what Microsoft Update shows. This behavior is the same for Linux machines that are configured to report to a local repo instead of a public repo. On a Windows machine, the compliance scan is run every 12 hours by default. For a Linux machine, the compliance scan is performed every hour by default. If the Log Analytics agent is restarted, a compliance scan is started within 15 minutes. When a machine completes a scan for update compliance, the agent forwards the information in bulk to Azure Monitor Logs. 
 

articles/azure-linux/concepts-core.md

@@ -17,7 +17,7 @@ Microsoft Azure Linux is an open-sourced project maintained by Microsoft, which
 
 One of the responsibilities of Microsoft in maintaining the Azure Linux Container Host is establishing a process for CVEs, such as identifying applicable CVEs and publishing CVE fixes, and adhering to defined Service Level Agreements (SLAs) for package fixes. The Azure Linux team builds and maintains the SLA for package fixes for production purposes. For more information, see the [Azure Linux package repo structure](https://github.com/microsoft/CBL-Mariner/blob/2.0/toolkit/docs/building/building.md#packagesmicrosoftcom-repository-structure). For the packages included in the Azure Linux Container Host, Azure Linux scans for security vulnerabilities twice a day via CVEs in the [National Vulnerability Database (NVD)](https://nvd.nist.gov/).
 
-Azure Linux CVEs are published in the [Security Update Guide (SUG) Common Vulnerability Reporting Framework (CVRF) API](https://api.msrc.microsoft.com/cvrf/v2.0/swagger/index). This allows you to get detailed Microsoft security updates about security vulnerabilities that have been investigated by the [Microsoft Security Response Center (MSRC)](https://www.microsoft.com/msrc). By collaborating with MSRC, Azure Linux can quickly and consistently discover, evaluate, and patch CVEs, and contribute critical fixes back upstream.
+Azure Linux CVEs are published in the [Security Update Guide (SUG) Common Vulnerability Reporting Framework (CVRF) API](https://github.com/microsoft/MSRC-Microsoft-Security-Updates-API). This allows you to get detailed Microsoft security updates about security vulnerabilities that have been investigated by the [Microsoft Security Response Center (MSRC)](https://www.microsoft.com/msrc). By collaborating with MSRC, Azure Linux can quickly and consistently discover, evaluate, and patch CVEs, and contribute critical fixes back upstream.
 
 High and critical CVEs are taken seriously and may be released out-of-band as a package update before a new AKS node image is available. Medium and low CVEs are included in the next image release.
 

articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

@@ -236,7 +236,6 @@ This section provides solutions for Azure platform services.
 * [Comparing and Contrasting the AKS/ANF NFS subdir external provisioner with Astra Trident](https://techcommunity.microsoft.com/t5/azure-architecture-blog/comparing-and-contrasting-the-aks-anf-nfs-subdir-external/ba-p/3057547)
 * [Out-of-This-World Kubernetes performance on Azure with Azure NetApp Files](https://cloud.netapp.com/blog/ma-anf-blg-configure-kubernetes-openshift)
 * [Azure NetApp Files + Trident = Dynamic and Persistent Storage for Kubernetes](https://anfcommunity.com/2021/02/16/azure-netapp-files-trident-dynamic-and-persistent-storage-for-kubernetes/)
-* [Trident - Storage Orchestrator for Containers](https://netapp-trident.readthedocs.io/en/stable-v20.04/kubernetes/operations/tasks/backends/anf.html)
 * [Magento e-commerce platform in Azure Kubernetes Service (AKS)](/azure/architecture/example-scenario/magento/magento-azure)
 * [Protecting Magento e-commerce platform in AKS against disasters with Astra Control Service](https://techcommunity.microsoft.com/t5/azure-architecture-blog/protecting-magento-e-commerce-platform-in-aks-against-disasters/ba-p/3285525)
 * [Protecting applications on private Azure Kubernetes Service clusters with Astra Control Service](https://techcommunity.microsoft.com/t5/azure-architecture-blog/protecting-applications-on-private-azure-kubernetes-service/ba-p/3289422)

articles/communication-services/concepts/media/try-phone-calling.png

@@ -105,6 +105,7 @@ Omnichannel for Customer Service customers, refer to [these instructions](/dynam
 - [Session Border Controllers certified for Azure Communication Services direct routing](./certified-session-border-controllers.md)
 - [Call Automation overview](../call-automation/call-automation.md)
 - [Pricing](../pricing.md)
+- [Try Phone Calling](./try-phone-calling.md)
 
 ### Quickstarts
 

articles/communication-services/concepts/telephony/direct-routing-provisioning.md

@@ -37,7 +37,7 @@ If you answer **yes** to the following questions, then Voice Calling (PSTN) is t
 With this option:
 - You get numbers directly from Microsoft and can call phones around the world.
 - You don't need to deploy or maintain any on-premises system because Voice Calling (PSTN) operates through Azure Communication Services.
-- Note: If necessary, you can choose to connect a supported Session Border Controller (SBC) through Azure Communication Services direct routing for interoperability with third-party Pprivate branch exchanges (PBXs), analog devices, and other third-party telephony equipment supported by the SBC.
+- Note: If necessary, you can choose to connect a supported Session Border Controller (SBC) through Azure Communication Services direct routing for interoperability with third-party private branch exchanges (PBXs), analog devices, and other third-party telephony equipment supported by the SBC.
 
 This option requires an uninterrupted connection to Azure Communication Services.  
 
@@ -79,6 +79,8 @@ This option requires:
 - [Pricing](../pricing.md)
 - Learn about [call automation API](../call-automation/call-automation.md) that enables you to build server-based calling workflows to control and manage calls for phone numbers and direct routing
 - [Number lookup overview](../../concepts/numbers/number-lookup-concept.md)
+- [Try Phone Calling](./try-phone-calling.md)
+
 
 ### Quickstarts
 

articles/communication-services/concepts/telephony/telephony-concept.md

@@ -0,0 +1,47 @@
+---
+title: Try Phone Calling - Azure Communication Services
+description: Confirm a phone number can connect without an app or other code.
+author: boris-bazilevskiy
+manager: dacarte
+services: azure-communication-services
+
+ms.author: bobazile
+ms.date: 3/13/2024
+ms.topic: conceptual
+ms.service: azure-communication-services
+ms.subservice: pstn
+---
+
+# Try Phone Calling
+
+[!INCLUDE [Public Preview Notice](../../includes/public-preview-include-document.md)]
+
+Try Phone Calling, now in public preview, is a tool in Azure preview portal to help customers confirm the setup of a telephony connection by making a phone call. It applies to both Voice Calling (PSTN) and direct routing. Try Phone Calling enables developers to quickly test Azure Communication Services calling capabilities, without an existing app or code on their end.
+
+## Prerequisites
+
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/).
+- A deployed Communication Services resource. Create an [Azure Communication Resource](../../quickstarts/create-communication-resource.md).
+- A [phone number acquired](../../quickstarts/telephony/get-phone-number.md) in your Communication Services resource, or Azure Communication Services Direct routing configured. If you have a free subscription, you can [get a trial phone number](../../quickstarts/telephony/get-trial-phone-number.md).
+- A User Access Token to enable the call client. For more information, see [how to get a User Access Token](../../quickstarts/identity/access-tokens.md).
+
+
+## Overview
+
+Open the [Azure preview portal](https://preview.portal.azure.com/#home) and search for **Try Phone Calling**. Then Enter a phone number, select a caller ID for this call, and the tool generates the code. You can also select **Use my connection string** and Try Phone Calling automatically gets the `connection string` for the resource.
+
+![alt text](../media/try-phone-calling.png "Make a phone call")
+
+You can run generated code right from the tool page and see the status of the call. You can also copy the generated code into an application and enrich it with other Azure Communication Services features such as chat, SMS, and voice and video calling.
+
+## Azure preview portal
+
+The Try Phone Calling tool is in public preview, and is only available from the [Azure preview portal](https://preview.portal.azure.com/#home).
+
+## Next steps
+
+Making a phone call is just the start. Now you can integrate other Azure Communication Services features into your application.
+
+- [Calling SDK overview](../voice-video-calling/calling-sdk-features.md)
+- [Chat concepts](../chat/concepts.md)
+- [SMS overview](../sms/concepts.md)