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

Author: tamram

articles/active-directory/authentication/concept-certificate-based-authentication-mobile-ios.md

@@ -16,7 +16,23 @@ ms.reviewer: vimrang
 ms.collection: M365-identity-device-management
 ms.custom: has-adal-ref
 ---
-# Azure Active Directory certificate-based authentication on iOS
+# Azure Active Directory certificate-based authentication on iOS and macOS
+
+## Azure Active Directory certificate-based authentication on macOS devices
+
+macOS Devices can use certificate-based authentication (CBA) to authenticate against Azure Active Directory (Azure AD) using their X.509 client certificate. Azure AD CBA is supported with certificates on-device as well as external hardware protected security keys. On macOS, Azure AD CBA is supported on all browsers and on Microsoft first-party applications.
+
+**Browsers supported on macOS**
+
+|Edge | Chrome | Safari | Firefox |
+|--------|---------|------|-------|
+|✅ |✅ | ✅ |✅ |
+
+**macOS device sign in with Azure AD CBA**
+
+Azure AD CBA today is not supported for device based sign into macOS machines. While the certificate used to sign-into the device can be the same certificate used to subsequently authenticate to Azure AD from a browser/desktop application, the device sign-in itself is not supported against Azure AD yet. 
+
+## Azure Active Directory certificate-based authentication on iOS devices
 
 Devices that run iOS can use certificate-based authentication (CBA) to authenticate to Azure Active Directory (Azure AD) using a client certificate on their device when connecting to:
 

articles/communication-services/concepts/call-automation/call-automation.md

@@ -43,21 +43,21 @@ The following list presents the set of features that are currently available in
 | Pre-call scenarios    | Answer a one-to-one call                          | ✔️    | ✔️    |
 |                       | Answer a group call                               | ✔️    | ✔️    |
 |                       | Place new outbound call to one or more endpoints  | ✔️    | ✔️    |
-|                       | Redirect (forward) a call to one or more endpoints  | ✔️    | ✔️    |
+|                       | Redirect* (forward) a call to one or more endpoints  | ✔️    | ✔️    |
 |                       | Reject an incoming call                           | ✔️    | ✔️    |
 | Mid-call scenarios    | Add one or more endpoints to an existing call     | ✔️    | ✔️    |
 |                       | Play Audio from an audio file                     | ✔️    | ✔️    |
 |                       | Recognize user input through DTMF                 | ✔️    | ✔️    |
 |                       | Remove one or more endpoints from an existing call| ✔️    | ✔️    |
-|                       | Blind Transfer* a call to another endpoint         | ✔️    | ✔️    |
+|                       | Blind Transfer* a 1:1 call to another endpoint    | ✔️    | ✔️    |
 |                       | Hang up a call (remove the call leg)              | ✔️    | ✔️    |
 |                       | Terminate a call (remove all participants and end call)| ✔️ | ✔️  |
 | Query scenarios       | Get the call state                                | ✔️    | ✔️    |
 |                       | Get a participant in a call                       | ✔️    | ✔️    |
 |                       | List all participants in a call                   | ✔️    | ✔️    |
 | Call Recording        | Start/pause/resume/stop recording                 | ✔️    | ✔️    |
 
-*Transfer of VoIP call to a phone number is currently not supported.
+*Transfer or redirect of a VoIP call to a phone number is currently not supported.
 
 ## Architecture
 

articles/communication-services/samples/includes/ui-maui.md

@@ -0,0 +1,61 @@
+---
+title: include file
+description: include file
+services: azure-communication-services
+author: iaulakh
+manager: james.cheng
+ms.service: azure-communication-services
+ms.subservice: azure-communication-services
+ms.date: 02/09/2023
+ms.topic: include
+ms.custom: include file
+ms.author: iaulakh
+---
+
+## Azure Communication UI Mobile Library for .NET MAUI
+
+This project demonstrates the integration of Azure Communication UI library into .NET MAUI application. It utilizes Azure Communication Services and the native Azure Communication Services UI library to build a calling experience that features both voice and video calling.
+
+### Download code
+
+Find the project for this sample on [GitHub](https://github.com/Azure-Samples/communication-services-ui-library-maui).
+
+### Features
+
+Refer to the native [UI Library overview](../../concepts/ui-library/ui-library-overview.md)
+
+### Prerequisites
+
+- Visual Studio [Setup Instructions](https://learn.microsoft.com/dotnet/maui/get-started/installation)
+- An Azure account with an active subscription. For details, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- iOS [Requirements](https://github.com/Azure/communication-ui-library-ios#requirements)
+- Android [Requirements](https://github.com/Azure/communication-ui-library-android#prerequisites)
+- An Azure Communication Services resource. For details, see [Create an Azure Communication Services resource](../../quickstarts/create-communication-resource.md).
+- An Azure Function running the [Authentication Endpoint](../../tutorials/trusted-service-tutorial.md) to fetch access tokens.
+
+### Run sample app
+
+Clone [repo](https://github.com/Azure-Samples/communication-services-ui-library-maui).
+
+#### For Android
+
+##### Visual Studio Mac/Windows 2022
+
+1. Navigate to `/AndroidMauiBindings` and in this directory in terminal run `./downloadJarScript.sh`. `GitBash` or `Windows Subsystem for Linux (WSL)` should be enabled to run `.sh` on Windows.
+2. Open `CommunicationCallingSampleMauiApp/CommunicationCallingSampleMauiApp.sln` in Visual Studio
+3. Edit `CommunicationCallingSampleMauiApp/CommunicationCallingSampleMauiApp.csproj` and set `<TargetFrameworks>net7.0-android</TargetFrameworks>`.
+4. Select android device/emulator in visual studio and run `CommunicationCallingSampleMauiApp` app.
+
+#### For iOS
+
+##### Visual Studio Mac 2022
+
+1. Navigate to `communication-services-ui-library-maui/iOSMauiBindings/ProxyLibs/CommunicationUI-Proxy` and in this directory in terminal run `./iOSFramework.sh -d`.
+2. Open `CommunicationCallingSampleMauiApp/CommunicationCallingSampleMauiApp.sln` in Visual Studio
+3. Edit `CommunicationCallingSampleMauiApp/CommunicationCallingSampleMauiApp.csproj` and set `<TargetFrameworks>net7.0-ios</TargetFrameworks>`.
+4. Select iOS device/simulator in visual studio and run `CommunicationCallingSampleMauiApp` app.
+
+### Highlights and feedback
+
+Visit [GitHub](https://github.com/Azure-Samples/communication-services-ui-library-maui#key-sample-highlights) to learn more and discover more capabilities and share your valuable feedback.
+

articles/communication-services/samples/ui-library-cross-platform.md

@@ -1,7 +1,7 @@
 ---
 title: Cross Platform development using the UI library
 titleSuffix: An Azure Communication Services sample overview
-description: Cross Platform development solutions using the UI library to enable Xamarin and React Native developers build communication applications
+description: Cross Platform development solutions using the UI library to enable .NET MAUI, Xamarin and React Native developers build communication applications
 author: jorgegarc
 manager: anujbh
 services: azure-communication-services
@@ -11,14 +11,18 @@ ms.date: 08/30/2021
 ms.topic: overview
 ms.service: azure-communication-services
 ms.subservice: calling
-zone_pivot_groups: acs-xamarin-react
+zone_pivot_groups: acs-maui-xamarin-react
 ---
 
 # Get started with Cross Platform development using the UI library
 
 [!INCLUDE [Public Preview Notice](../includes/public-preview-include.md)]
 
-Azure Communication Services introduces Cross Platform development using **Xamarin and React Native** solutions. This sample demonstrates how Azure Communication Services Calling integrates the UI Library for mobile platforms and create the bindings to allow developers to begin building with the calling capabilities.
+Azure Communication Services introduces Cross Platform development using **.NET MAUI, Xamarin and React Native** solutions. This sample demonstrates how Azure Communication Services Calling integrates the UI Library for mobile platforms and create the bindings to allow developers to begin building with the calling capabilities.
+
+::: zone pivot="platform-maui"
+[!INCLUDE [.NET MAUI](./includes/ui-maui.md)]
+::: zone-end
 
 ::: zone pivot="platform-xamarin"
 [!INCLUDE [Xamarin](./includes/ui-xamarin.md)]

articles/event-hubs/event-hubs-java-get-started-send.md

@@ -11,6 +11,9 @@ ms.custom: devx-track-java, mode-api
 
 This quickstart shows how to send events to and receive events from an event hub using the **azure-messaging-eventhubs** Java package.
 
+> [!TIP]
+> If you're working with Azure Event Hubs resources in a Spring application, we recommend that you consider [Spring Cloud Azure](/azure/developer/java/spring-framework/) as an alternative. Spring Cloud Azure is an open-source project that provides seamless Spring integration with Azure services. To learn more about Spring Cloud Azure, and to see an example using Event Hubs, see [Spring Cloud Stream with Azure Event Hubs](/azure/developer/java/spring-framework/configure-spring-cloud-stream-binder-java-app-azure-event-hub).
+
 ## Prerequisites
 
 If you're new to Azure Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you do this quickstart.

articles/event-hubs/event-hubs-premium-overview.md

@@ -14,7 +14,9 @@ It replicates events to three replicas, distributed across Azure availability zo
 In addition to these storage-related features and all capabilities and protocol support of the standard tier, the isolation model of the premium tier enables features like [dynamic partition scale-up](dynamically-add-partitions.md). You also get far more generous [quota allocations](event-hubs-quotas.md). Event Hubs Capture is included at no extra cost.
 
 > [!NOTE]
-> Event Hubs Premium supports TLS 1.2 or greater. 
+> - Event Hubs Premium supports TLS 1.2 or greater. 
+> - The premium tier isn't available in all regions. Try to create a namespace in the Azure portal and see supported regions in the **Location** drop-down list on the **Create Namespace** page.
+
 
 You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
 

articles/healthcare-apis/azure-api-for-fhir/release-notes.md

@@ -8,7 +8,7 @@ ms.subservice: fhir
 ms.topic: reference
 ms.date: 06/16/2022
 ms.custom: references_regions
-ms.author: kesheth
+ms.author: kavitagaddam
 ---
 
 # Release notes: Azure API for FHIR

articles/healthcare-apis/release-notes.md

@@ -7,7 +7,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: reference
 ms.date: 01/25/2023
-ms.author: mikaelw
+ms.author: kavitagaddam 
 ms.custom: references_regions
 ---
 
@@ -21,11 +21,11 @@ Azure Health Data Services is a set of managed API services based on open standa
 
 ## January 2023
 
-### MedTech service
+### Azure Health Data Services
 
-**Qatar Central region is Generally Available (GA)**
+**Azure Health Data services General Available (GA) in new regions**
 
-Customers in Qatar Central can now access the MedTech service.
+General availability (GA) of Azure Health Data services in France Central, North Central US and Qatar Central Regions.
 
 
 ### DICOM service
@@ -47,13 +47,7 @@ One new sample app has been released in the [Health Data Services samples repo](
 
 ## **December 2022**
 
-#### Azure Health Data Services
-
-**Azure Health Data services General Available (GA) in new regions**
-
-General availability (GA) of Azure Health Data services in France Central, North Central US and Qatar Central Regions.
 
-   
 #### DICOM service
 
 

articles/machine-learning/concept-model-management-and-deployment.md

@@ -178,6 +178,7 @@ For more information on using Azure Pipelines with Machine Learning, see:
 
 Learn more by reading and exploring the following resources:
 
++ [Set up MLOps with Azure DevOps](how-to-setup-mlops-azureml.md)
 + [Learning path: End-to-end MLOps with Azure Machine Learning](/training/paths/build-first-machine-operations-workflow/)
 + [How to deploy a model to an online endpoint](how-to-deploy-online-endpoints.md) with Machine Learning
 + [Tutorial: Train and deploy a model](tutorial-train-deploy-notebook.md)

articles/machine-learning/how-to-deploy-mlflow-models-online-endpoints.md

@@ -251,7 +251,7 @@ version = registered_model.version
     
     __endpoint.yaml__
 
-    <!--    :::code language="yaml" source="~/azureml-examples-main/cli/endpoints/online/mlflow/create-endpoint.yaml"::: -->
+    :::code language="yaml" source="~/azureml-examples-main/cli/endpoints/online/ncd/create-endpoint.yaml":::
 
     # [Python (Azure ML SDK)](#tab/sdk)
 
@@ -295,7 +295,7 @@ version = registered_model.version
     
     # [Azure CLI](#tab/cli)
     
-    <!--    :::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-mlflow.sh" ID="create_endpoint"::: -->
+    :::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-ncd.sh" ID="create_endpoint":::
 
     # [Python (Azure ML SDK)](#tab/sdk)
     
@@ -322,7 +322,7 @@ version = registered_model.version
 
     __sklearn-deployment.yaml__
 
-    <!--    :::code language="yaml" source="~/azureml-examples-main/cli/endpoints/online/mlflow/sklearn-deployment.yaml"::: -->
+    :::code language="yaml" source="~/azureml-examples-main/cli/endpoints/online/ncd/sklearn-deployment.yaml":::
 
     # [Python (Azure ML SDK)](#tab/sdk)
 
@@ -375,7 +375,7 @@ version = registered_model.version
     
     # [Azure CLI](#tab/cli)
     
-    <!--    :::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-mlflow.sh" ID="create_sklearn_deployment"::: -->
+    :::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-ncd.sh" ID="create_sklearn_deployment":::
 
     # [Python (Azure ML SDK)](#tab/sdk)
 
@@ -471,7 +471,7 @@ Once your deployment completes, your deployment is ready to serve request. One o
 
 **sample-request-sklearn.json**
 
-<!-- :::code language="json" source="~/azureml-examples-main/cli/endpoints/online/mlflow/sample-request-sklearn.json"::: -->
+:::code language="json" source="~/azureml-examples-main/cli/endpoints/online/ncd/sample-request-sklearn.json":::
 
 > [!NOTE]
 > Notice how the key `input_data` has been used in this example instead of `inputs` as used in MLflow serving. This is because Azure Machine Learning requires a different input format to be able to automatically generate the swagger contracts for the endpoints. See [Differences between models deployed in Azure Machine Learning and MLflow built-in server](how-to-deploy-mlflow-models.md#differences-between-models-deployed-in-azure-machine-learning-and-mlflow-built-in-server) for details about expected input format.
@@ -480,7 +480,7 @@ To submit a request to the endpoint, you can do as follows:
 
 # [Azure CLI](#tab/cli)
 
-<!-- :::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-mlflow.sh" ID="test_sklearn_deployment"::: -->
+:::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-ncd.sh" ID="test_sklearn_deployment":::
 
 # [Python (Azure ML SDK)](#tab/sdk)
 
@@ -719,7 +719,7 @@ Use the following steps to deploy an MLflow model with a custom scoring script.
 
     **sample-request-sklearn.json**
     
-    <!--    :::code language="json" source="~/azureml-examples-main/cli/endpoints/online/mlflow/sample-request-sklearn.json"::: -->
+    :::code language="json" source="~/azureml-examples-main/cli/endpoints/online/ncd/sample-request-sklearn.json":::
 
     To submit a request to the endpoint, you can do as follows:
     
@@ -776,7 +776,7 @@ Once you're done with the endpoint, you can delete the associated resources:
 
 # [Azure CLI](#tab/cli)
 
-<!-- :::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-mlflow.sh" ID="delete_endpoint"::: -->
+:::code language="azurecli" source="~/azureml-examples-main/cli/deploy-managed-online-endpoint-ncd.sh" ID="delete_endpoint":::
 
 # [Python (Azure ML SDK)](#tab/sdk)