Merge pull request #250013 from MicrosoftDocs/main

8/31/2023 AM Publish

Author: Taojunshen

articles/active-directory/develop/scenario-mobile-app-registration.md

@@ -40,25 +40,23 @@ For more information, see [Scenarios and supported authentication flows](authent
 
 ### Interactive authentication
 
-When you build a mobile app that uses interactive authentication, the most critical registration step is the redirect URI. You can set interactive authentication through the [platform configuration on the **Authentication** blade](https://aka.ms/MobileAppReg).
+When you build a mobile app that uses interactive authentication, the most critical registration step is the redirect URI. This experience enables your app to get single sign-on (SSO) through Microsoft Authenticator (and Intune Company Portal on Android). It also supports device management policies.
 
-This experience will enable your app to get single sign-on (SSO) through Microsoft Authenticator (and Intune Company Portal on Android). It will also support device management policies.
-
-The app registration portal provides a preview experience to help you compute the brokered reply URI for iOS and Android applications:
-
-1. In the app registration portal, select **Authentication** > **Try out the new experience**.
-
-   ![The Authentication blade, where you choose a new experience](https://user-images.githubusercontent.com/13203188/60799285-2d031b00-a173-11e9-9d28-ac07a7ae894a.png)
-
-2. Select **Add a platform**.
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
+1. Browse to **Identity** > **Applications** > **App registrations**.
+1. Select **New registration**.
+1. Enter a **Name** for the application.
+1. For **Supported account types**, select **Accounts in this organizational directory only**.
+1. Select **Register**.
+1. Select **Authentication** and then select **Add a platform**.
 
    ![Add a platform](https://user-images.githubusercontent.com/13203188/60799366-4c01ad00-a173-11e9-934f-f02e26c9429e.png)
 
-3. When the list of platforms is supported, select **iOS**.
+1. When the list of platforms is supported, select **iOS / macOS**.
 
    ![Choose a mobile application](https://user-images.githubusercontent.com/13203188/60799411-60de4080-a173-11e9-9dcc-d39a45826d42.png)
 
-4. Enter your bundle ID, and then select **Register**.
+1. Enter your bundle ID, and then select **Configure**.
 
    ![Enter your bundle ID](https://user-images.githubusercontent.com/13203188/60799477-7eaba580-a173-11e9-9f8b-431f5b09344e.png)
 
@@ -81,7 +79,7 @@ If your app uses only username-password authentication, you don't need to regist
 
 However, identify your application as a public client application. To do so:
 
-1. Still in the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>, select your app in **App registrations**, and then select **Authentication**.
+1. Still in the Microsoft Entra admin center, select your app in **App registrations**, and then select **Authentication**.
 1. In **Advanced settings** > **Allow public client flows** > **Enable the following mobile and desktop flows:**, select **Yes**.
 
    :::image type="content" source="media/scenarios/default-client-type.png" alt-text="Enable public client setting on Authentication pane in Azure portal":::

articles/active-directory/develop/tutorial-blazor-webassembly.md

@@ -32,7 +32,7 @@ We also have a [tutorial for Blazor Server](tutorial-blazor-server.md).
 - [.NET Core 7.0 SDK](https://dotnet.microsoft.com/download/dotnet-core/7.0)
 - An Azure AD tenant where you can register an app. If you don't have access to an Azure AD tenant, you can get one by registering with the [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program) or by creating an [Azure free account](https://azure.microsoft.com/free).
 
-## Register the app in the Azure portal
+## Register the app
 
 Every app that uses Azure AD for authentication must be registered with Azure AD. Follow the instructions in [Register an application](quickstart-register-app.md) with these specifications:
 
@@ -47,11 +47,11 @@ To create the application, run the following command. Replace the placeholders i
 dotnet new blazorwasm --auth SingleOrg --calls-graph -o {APP NAME} --client-id "{CLIENT ID}" --tenant-id "{TENANT ID}" -f net7.0
 ```
 
-| Placeholder   | Azure portal name       | Example                                |
-| ------------- | ----------------------- | -------------------------------------- |
-| `{APP NAME}`  | —                 | `BlazorWASMSample`                     |
+| Placeholder | Name | Example |
+| ----------- | ---- |-------- |
+| `{APP NAME}`  | — | `BlazorWASMSample` |
 | `{CLIENT ID}` | Application (client) ID | `41451fa7-0000-0000-0000-69eff5a761fd` |
-| `{TENANT ID}` | Directory (tenant) ID   | `e86c78e2-0000-0000-0000-918e0565a45e` |
+| `{TENANT ID}` | Directory (tenant) ID | `e86c78e2-0000-0000-0000-918e0565a45e` |
 
 ## Test the app
 
@@ -77,7 +77,7 @@ Now you'll update your app's registration and code to pull a user's emails and d
 
 First, add the `Mail.Read` API permission to the app's registration so that Azure AD is aware that the app will request to access its users' email.
 
-1. In the Azure portal, select your app in **App registrations**.
+1. In the Microsoft Entra admin center, select your app in **App registrations**.
 1. Under **Manage**, select **API permissions**.
 1. Select **Add a permission** > **Microsoft Graph**.
 1. Select **Delegated Permissions**, then search for and select the **Mail.Read** permission.

articles/active-directory/develop/tutorial-v2-android.md

@@ -26,7 +26,7 @@ In this tutorial:
 > [!div class="checklist"]
 >
 > - Create an Android app project in _Android Studio_
-> - Register the app in the Azure portal
+> - Register the app in the Microsoft Entra admin center
 > - Add code to support user sign-in and sign-out
 > - Add code to call the Microsoft Graph API
 > - Test the app
@@ -51,18 +51,18 @@ Follow these steps to create a new project if you don't already have an Android
 1. Open Android Studio, and select **Start a new Android Studio project**.
 2. Select **Basic Activity** and select **Next**.
 3. Enter a name for the application, such as _MSALAndroidapp_.
-4. Record the package name to be used in the Azure portal in later steps.
+4. Record the package name to be used in later steps.
 5. Change the language from **Kotlin** to **Java**.
 6. Set the **Minimum SDK API level** to **API 19** or higher, and select **Finish**.
 
 ### Register your application with Azure AD
 
 [!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)]
 
-1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
-1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
-1. Search for and select **Azure Active Directory**.
-1. Under **Manage**, select **App registrations** > **New registration**.
+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
+1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
+1. Browse to **Identity** > **Applications** > **App registrations**.
+1. Select **New registration**.
 1. Enter a **Name** for your application. Users of your app might see this name, and you can change it later.
 1. For **Supported account types**, select **Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)**. For information on different account types, select the **Help me choose** option.
 1. Select **Register**.
@@ -129,8 +129,8 @@ Follow these steps to create a new project if you don't already have an Android
    </activity>
    ```
 
-   - Use your Azure portal **Package name** to replace `android:host=.` value. It should look like `com.azuresamples.msalandroidapp`.
-   - Use your Azure portal **Signature Hash** to replace `android:path=` value. Ensure that there's a leading `/` at the beginning of your Signature Hash. It should look like `/1wIqXSqBj7w+h11ZifsnqwgyKrY=`.
+   - Use the **Package name** to replace `android:host=.` value. It should look like `com.azuresamples.msalandroidapp`.
+   - Use the **Signature Hash** to replace `android:path=` value. Ensure that there's a leading `/` at the beginning of your Signature Hash. It should look like `/1wIqXSqBj7w+h11ZifsnqwgyKrY=`.
 
    You can find these values in the Authentication blade of your app registration as well.
 

articles/active-directory/external-identities/customers/faq-customers.md

@@ -67,6 +67,10 @@ Opt for the next generation Microsoft Entra External ID platform if:
 - You’re starting fresh building identities into apps or you're in the early stages of product discovery.
 - The benefits of rapid innovation, new features and capabilities are a priority.
 
+### Why is Azure AD B2C not part of Entra ID/External ID?
+
+Microsoft Entra External ID and Azure AD B2C are two separate platforms powered by ESTS and IEF respectively. Entra External ID is our new converged platform which is future proof and developer friendly to meet all your identity needs – B2E, B2B and B2C. At the same time, we will still continue to support Azure AD B2C as a separate product offering with no change in SLA, and we’ll continue investments in the product to ensure security, availability, and reliability.
+
 ## Next steps
 
-[Learn more about Microsoft Entra External ID for customers](index.yml)
+[Learn more about Microsoft Entra External ID for customers](index.yml)

articles/ai-services/openai/concepts/use-your-data.md

@@ -224,7 +224,7 @@ Azure OpenAI on your data provides several search options you can use when you a
 | *semantic*          |  Semantic search  |  Additional pricing for [semantic search](/azure/search/semantic-search-overview#availability-and-pricing) usage.                  |      
 | *vector*            | Vector search       | [Additional pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) on your Azure OpenAI account from calling the embedding model.                    |   
 | *vector + simple*   | A hybrid of vector search and simple search | [Additional pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) on your Azure OpenAI account from calling the embedding model.            |      
-| *vector + semantic* | A hybrid of vector search and semantic search for retrieval.     | [Additional pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) on your Azure OpenAI account from calling the embedding model, and additional pricing for [semantic search](/azure/search/semantic-search-overview#availability-and-pricing) usage.                    |     
+| *vector + semantic + simple * | A hybrid of vector search, simple search (keyword based) and  semantic search for retrieval     | [Additional pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) on your Azure OpenAI account from calling the embedding model, and additional pricing for [semantic search](/azure/search/semantic-search-overview#availability-and-pricing) usage.                    |     
 
 The optimal search option can vary depending on your dataset and use-case. You may need to experiment with multiple options to determine which works best for your use-case.
 

articles/azure-large-instances/toc.yml

@@ -20,5 +20,5 @@
   items:
   - name: Azure Large Instances for Epic workload
     href: ./workloads/epic/index.yml
-- name: FAQ
-  href: faq.md
+  - name: FAQ
+    href: faq.md

articles/azure-vmware/enable-sql-azure-hybrid-benefit.md

@@ -1,49 +1,53 @@
 ---
-title: Enable SQL Azure hybrid benefit for Azure VMware Solution
-description: This article shows you how to apply SQL Azure hybrid benefits to your Azure VMware Solution private cloud by configuring a placement policy.
+title: Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution
+author: jjaygbay1
+ms.author: jacobjaygbay
+description: This article shows you how to apply Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution to your Azure VMware Solution private cloud by configuring a placement policy.
 ms.topic: how-to
 ms.service: azure-vmware
 ms.date: 02/14/2023
 ---
 
-# Enable SQL Azure hybrid benefit for Azure VMware Solution
+# Enable Azure Hybrid Benefit for SQL Server in Azure VMware Solution
 
-In this article, you’ll learn how to configure SQL Azure hybrid benefits to an Azure VMware Solution private cloud by configuring a placement policy. The placement policy defines the hosts that are running SQL as well as the virtual machines on that host. 
->[!IMPORTANT]
-> It is important to note that SQL benefits are applied at the host level. 
+In this article, you’ll learn how to configure Azure Hybrid Benefit for SQL Server in an Azure VMware Solution private cloud by configuring a placement policy. The placement policy defines the hosts that are running SQL Server as well as the virtual machines on that host.  
 
-For example, if each host in Azure VMware Solution has 36 cores and you signal that two hosts run SQL, then SQL Azure hybrid benefit will apply to 72 cores irrespective of the number of SQL or other virtual machines on that host.
+> [!IMPORTANT]
+> It is important to note that SQL Server benefits are applied at the host level.  
 
-You can also choose to view a video tutorial for configuring SQL Azure hybrid benefits for Azure VMware Solution [here](https://www.youtube.com/watch?v=vJIQ1K2KTa0).
+For example, if each host in Azure VMware Solution has 36 cores and you intend to have 2 hosts run SQL Server then the Azure Hybrid Benefit will apply to 72 cores, irrespective of the number of SQL Server instances or other virtual machines are on that host. 
 
-## Configure host-VM placement policy
-1.	From your Azure VMware Solution private cloud, select Azure hybrid benefit, then Create host-VM placement policy.
- :::image type="content" source="media/sql-azure-hybrid-benefit/azure-hybrid-benefit.png" alt-text="Diagram that shows how to create a host new virtual machine placement policy.":::
+You can also choose to view a video tutorial for configuring Azure Hybrid Benefit for SQL Server in Azure VMware Solution [here](https://www.youtube.com/watch?v=vJIQ1K2KTa0).
 
-1.	Fill in the required fields for creating the placement policy.
-     1.	**Name** – Select the name that identifies this policy.
+## Configure host-VM placement policy 
+
+1. From your Azure VMware Solution private cloud, select Azure hybrid benefit, then Create host-VM placement policy.
+
+    :::image type="content" source="media/sql-azure-hybrid-benefit/azure-hybrid-benefit.png" alt-text="Diagram that shows how to create a host new virtual machine placement policy.":::
+
+1. Fill in the required fields for creating the placement policy.
+     1. **Name** – Select the name that identifies this policy.
      2. **Type** – Select the type of policy. This type must be a VM-Host affinity rule only.
      3. **Azure hybrid benefit** – Select the checkbox to apply the SQL Azure hybrid benefit.
      4. **Cluster** – Select the correct cluster. The policy is scoped to host in this cluster only.
-     1. **Enabled** – Select enabled to apply the policy immediately once created.
-     
+     5. **Enabled** – Select enabled to apply the policy immediately once created.
      :::image type="content" source="media/sql-azure-hybrid-benefit/create-placement-policy.png" alt-text="Diagram that shows how to create a host virtual machine placement policy using the host VM affinity.":::
-3.	Select the hosts and VMs that will be applied to the VM-Host affinity policy.
+2. Select the hosts and VMs that will be applied to the VM-Host affinity policy.
      1.	**Add Hosts** – Select the hosts that will be running SQL. When hosts are replaced, policies are re-created on the new hosts automatically.
      2.	**Add VMs** – Select the VMs that should run on the selected hosts.
      3. **Review and Create** the policy.
      :::image type="content" source="media/sql-azure-hybrid-benefit/select-policy-host.png" alt-text="Diagram that shows how to create a host virtual machine affinity.":::
 
-## Manage placement policies
+## Manage placement policies 
 
-After creating the placement policy, you can review, manage, or edit the policy by way of the Placement policies menu in the Azure VMware Solution private cloud. 
+After creating the placement policy, you can review, manage, or edit the policy by way of the Placement policies menu in the Azure VMware Solution private cloud.  
 
-By checking the Azure hybrid benefit checkbox in the configuration setting, you can enable existing host-VM affinity policies with the SQL Azure hybrid benefit.
+By checking the Azure Hybrid Benefit checkbox in the configuration setting, you can enable existing host-VM affinity policies with the Azure Hybrid Benefit for SQL Server. 
 
-:::image type="content" source="media/sql-azure-hybrid-benefit/placement-policies.png" alt-text="Diagram that shows how to configure virtual machine placement policies.":::
+:::image type="content" source="media/sql-azure-hybrid-benefit/placement-policies.png" alt-text="Diagram that shows how to configure virtual machine placement policies."::: 
 
 ## Next steps
-[Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/)
 
-[Attach Azure NetApp Files datastores to Azure VMware Solution hosts](attach-azure-netapp-files-to-azure-vmware-solution-hosts.md)
+[Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/)
 
+[Attach Azure NetApp Files datastores to Azure VMware Solution hosts](attach-azure-netapp-files-to-azure-vmware-solution-hosts.md)