Merge branch 'main' of http://github.com/MicrosoftDocs/azure-docs-pr into aca/workload-profiles-ga

craigshoemaker · craigshoemaker · commit dd412d24a563 · 2023-08-29T16:01:52.000-06:00
diff --git a/articles/active-directory/develop/tutorial-v2-windows-uwp.md b/articles/active-directory/develop/tutorial-v2-windows-uwp.md
@@ -387,24 +387,24 @@ private async Task DisplayMessageAsync(string message)
 
 Now, register your application:
 
-1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
+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 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. Browse to **Identity** > **Applications** > **Application registrations**.
+1. Select **New registration**.
 1. Enter a **Name** for your application, for example `UWP-App-calling-MSGraph`. Users of your app might see this name, and you can change it later.
 1. Under **Supported account types**, select **Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)**. 
 1. Select **Register**.
 1. On the overview page, find the **Application (client) ID** value and copy it. Go back to Visual Studio, open *MainPage.xaml.cs*, and replace the value of `ClientId` with this value.
 
 Configure authentication for your application:
 
-1. Back in the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>, under **Manage**, select **Authentication** > **Add a platform**, and then select **Mobile and desktop applications**.
+1. In to the Microsoft Entra admin center, select **Authentication** > **Add a platform**, and then select **Mobile and desktop applications**.
 1. In the **Redirect URIs** section, enter `https://login.microsoftonline.com/common/oauth2/nativeclient`.
 1. Select **Configure**.
 
 Configure API permissions for your application:
 
-1. Under **Manage**, select **API permissions** > **Add a permission**.
+1. Select **API permissions** > **Add a permission**.
 1. Select **Microsoft Graph**.
 1. Select **Delegated permissions**, search for *User.Read*, and verify that **User.Read** is selected.
 1. If you made any changes, select **Add permissions** to save them.
@@ -484,7 +484,7 @@ In the current sample, the `WithRedirectUri("https://login.microsoftonline.com/c
 
     You can then remove the line of code because it's required only once, to fetch the value.
 
-3. In the app registration portal, add the returned value in **RedirectUri** in the **Authentication** pane.
+3. In the Microsoft Entra admin center, add the returned value in **RedirectUri** in the **Authentication** pane.
 
 ## Test your code
 
diff --git a/articles/app-service/app-service-configure-premium-tier.md b/articles/app-service/app-service-configure-premium-tier.md
@@ -4,7 +4,7 @@ description: Learn how to better performance for your web, mobile, and API app i
 keywords: app service, azure app service, scale, scalable, app service plan, app service cost
 ms.assetid: ff00902b-9858-4bee-ab95-d3406018c688
 ms.topic: article
-ms.date: 05/08/2023
+ms.date: 08/29/2023
 ms.author: msangapu
 author: msangapu-msft
 ms.custom: seodec18, devx-track-azurecli, devx-track-azurepowershell
@@ -13,19 +13,19 @@ ms.custom: seodec18, devx-track-azurecli, devx-track-azurepowershell
 
 # Configure Premium V3 tier for Azure App Service
 
-The new Premium V3 pricing tier gives you faster processors, SSD storage, and quadruple the memory-to-core ratio of the existing pricing tiers (double the Premium V2 tier). With the performance advantage, you could save money by running your apps on fewer instances. In this article, you learn how to create an app in Premium V3 tier or scale up an app to Premium V3 tier.
+The new Premium V3 pricing tier gives you faster processors, SSD storage, memory-optimized options, and quadruple the memory-to-core ratio of the existing pricing tiers (double the Premium V2 tier). With the performance advantage, you could save money by running your apps on fewer instances. In this article, you learn how to create an app in Premium V3 tier or scale up an app to Premium V3 tier.
 
 ## Prerequisites
 
-To scale-up an app to Premium V3, you need to have an Azure App Service app that runs in a pricing tier lower than Premium V3, and the app must be running in an App Service deployment that supports Premium V3.
+To scale-up an app to Premium V3, you need to have an Azure App Service app that runs in a pricing tier lower than Premium V3, and the app must be running in an App Service deployment that supports Premium V3. Additionally the App Service deployment must support the desired SKU within Premium V3.
 
 <a name="availability"></a>
 
 ## Premium V3 availability
 
 The Premium V3 tier is available for both native and custom containers, including both Windows containers and Linux containers.
 
-Premium V3 is available in some Azure regions and availability in additional regions is being added continually. To see if it's available in your region, run the following Azure CLI command in the [Azure Cloud Shell](../cloud-shell/overview.md):
+Premium V3 as well as specific Premium V3 SKUs are available in some Azure regions and availability in additional regions is being added continually. To see if a specific PremiumV3 offering is available in your region, run the following Azure CLI command in the [Azure Cloud Shell](../cloud-shell/overview.md) (substitute _P1v3_ with the desired SKU):
 
 ```azurecli-interactive
 az appservice list-locations --sku P1V3
@@ -44,11 +44,12 @@ To see all the Premium V3 options, select **Explore pricing plans**, then select
 :::image type="content" source="media/app-service-configure-premium-tier/explore-pricing-plans.png" alt-text="Screenshot showing the Explore pricing plans page with a Premium V3 plan selected.":::
 
 > [!IMPORTANT] 
-> If you don't see a Premium V3 plan as an option, or if the options are greyed out, then Premium V3 likely isn't available in the underlying App Service deployment that contains the App Service plan. See [Scale up from an unsupported resource group and region combination](#unsupported) for more details.
+> If you don't see **P0V3**, **P1V3**, **P2V3**, **P3V3**, **P1mV3**, **P2mV3**, **P3mV3**, **P4mV3**, and **P5mV3** as options, or if some options are greyed out, then either **Premium V3** or an individual SKU within **Premium V3** isn't available in the underlying App Service deployment that contains the App Service plan. See [Scale up from an unsupported resource group and region combination](#unsupported) for more details.
+>
 
 ## Scale up an existing app to Premium V3 tier
 
-Before scaling an existing app to Premium V3 tier, make sure that Premium V3 is available. For information, see [Premium V3 availability](#availability). If it's not available, see [Scale up from an unsupported resource group and region combination](#unsupported).
+Before scaling an existing app to Premium V3 tier, make sure that both Premium V3 as well as the specific SKU within Premium V3 are available. For information, see [PremiumV3 availability](#availability). If it's not available, see [Scale up from an unsupported resource group and region combination](#unsupported).
 
 Depending on your hosting environment, scaling up may require extra steps. 
 
@@ -74,10 +75,9 @@ Some App Service plans can't scale up to the Premium V3 tier, or to a newer SKU
 
 ## Scale up from an unsupported resource group and region combination
 
-If your app runs in an App Service deployment where Premium V3 isn't available, or if your app runs in a region that currently does not support Premium V3, you need to re-deploy your app to take advantage of Premium V3.  You have two options:
+If your app runs in an App Service deployment where Premium V3 isn't available, or if your app runs in a region that currently does not support Premium V3, you need to re-deploy your app to take advantage of Premium V3. Alternatively newer Premium V3 SKUs may not be available, in which case you also need to re-deploy your app to take advantage of newer SKUs within Premium V3. You have two options:
 
-- Create an app in a new resource group and with a new App Service plan. When creating the App Service plan, select a Premium V3 tier. This step ensures that the App Service plan is deployed into a deployment unit that supports Premium V3. Then, redeploy your application code into the newly created app. Even if you scale the App Service plan down to a lower tier to save costs, you can always scale back up to Premium V3 because the deployment unit supports it.
-- If your app already runs in an existing **Premium** tier, then you can clone your app with all app settings, connection strings, and deployment configuration into a new resource group on a new app service plan that uses Premium V3.
+- Create an app in a new resource group and with a new App Service plan. When creating the App Service plan, select the desired Premium V3 tier. This step ensures that the App Service plan is deployed into a deployment unit that supports Premium V3 as well as the specific SKU within Premium V3. Then, redeploy your application code into the newly created app. Even if you scale the new App Service plan down to a lower tier to save costs, you can always scale back up to Premium V3 and the desired SKU within Premium V3 because the deployment unit supports it.
 
     ![Screenshot showing how to clone your app.](media/app-service-configure-premium-tier/clone-app.png)
 
diff --git a/articles/azure-arc/data/includes/azure-arc-data-preview-release.md b/articles/azure-arc/data/includes/azure-arc-data-preview-release.md
@@ -6,16 +6,18 @@ ms.topic: include
 ms.date: 05/02/2023
 ---
 
-At this time, a test or preview build is not available for the next release.
 
 <!--
+At this time, a test or preview build is not available for the next release.
+
+-->
 
-Aug 2023 preview release is now available.
+Sept 2023 preview release is now available.
 
 |Component|Value|
 |-----------|-----------|
-|Container images registry/repository |`mcr.microsoft.com/arcdata/preview`|
-|Container images tag |`v1.22.0_2023-08-08`|
+|Container images registry/repository |`mcr.microsoft.com/arcdata/test`|
+|Container images tag |`v1.23.0_2023-09-12`|
 |**CRD names and version:**| |
 |`activedirectoryconnectors.arcdata.microsoft.com`| v1beta1, v1beta2, v1, v2|
 |`datacontrollers.arcdata.microsoft.com`| v1beta1, v1 through v5|
@@ -32,17 +34,13 @@ Aug 2023 preview release is now available.
 |`telemetrycollectors.arcdata.microsoft.com`| v1beta1 through v1beta5|
 |`telemetryrouters.arcdata.microsoft.com`| v1beta1 through v1beta5|
 |Azure Resource Manager (ARM) API version|2023-01-15-preview|
-|`arcdata` Azure CLI extension version|1.5.4 ([Download](https://aka.ms/az-cli-arcdata-ext))|
-|Arc-enabled Kubernetes helm chart extension version|1.22.0|
+|`arcdata` Azure CLI extension version|1.5.5 ([Download](https://aka.ms/az-cli-arcdata-ext))|
+|Arc-enabled Kubernetes helm chart extension version|1.23.0|
 |Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|<br/>1.8.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.8.0 ([Download](https://aka.ms/ads-azcli-ext))|
 |SQL Database version | 957 |
 
+<!--
 ### Release notes
 
-- Arc Enabled SQL Server | Automatic certificate rotation for certificates used for Azure Active Directory authentication is now supported.
-    - For Service Managed Certificates the certificate rotation is automatic.
-    - For Customer Managed Certificates user needs to upload the certificate to App Registration manually.
-- Support for configuring and managing Azure Failover groups between two Arc enabled SQL managed instances using Azure portal. 
-- Upgraded OpenSearch and OpenSearch Dashboards from 2.7.0 to 2.8.0
-
 -->
+
diff --git a/articles/communication-services/concepts/numbers/sub-eligibility-number-capability.md b/articles/communication-services/concepts/numbers/sub-eligibility-number-capability.md
@@ -48,6 +48,7 @@ Numbers can be purchased on eligible Azure subscriptions and in geographies wher
 > - [Saudi Arabia](../numbers/phone-number-management-for-saudi-arabia.md)
 > - [Singapore](../numbers/phone-number-management-for-singapore.md)
 > - [Slovakia](../numbers/phone-number-management-for-slovakia.md)
+> - [South Korea](../numbers/phone-number-management-for-south-korea.md)
 > - [Spain](../numbers/phone-number-management-for-spain.md)
 > - [Sweden](../numbers/phone-number-management-for-sweden.md)
 > - [Switzerland](../numbers/phone-number-management-for-switzerland.md)
diff --git a/articles/communication-services/concepts/pstn-pricing.md b/articles/communication-services/concepts/pstn-pricing.md
@@ -428,13 +428,24 @@ All prices shown below are in USD.
 |-------------|---------------|-----------------|
 |Toll-free    |N/A            |USD 0.2377/min   |
 
+
+## South Korea telephony offers
+### Phone number leasing charges
+|Number type   |Monthly fee   |
+|--------------|--------------|
+|Toll-Free     |USD 23.00/mo  |
+### Usage charges
+|Number type  |To make calls  |To receive calls |
+|-------------|---------------|-----------------|
+|Toll-free    |N/A            |USD 0.1287/min   |
+
+
 ## Philippines telephony offers
 
 ### Phone number leasing charges
 |Number type   |Monthly fee   |
 |--------------|--------------|
 |Toll-Free     |USD 25.00/mo  |
-
 ### Usage charges
 |Number type  |To make calls  |To receive calls |
 |-------------|---------------|-----------------|
diff --git a/articles/communication-services/includes/country-dropdown.md b/articles/communication-services/includes/country-dropdown.md
@@ -37,6 +37,7 @@ ms.custom: references_regions
 > - [Saudi Arabia](../concepts/numbers/phone-number-management-for-saudi-arabia.md)
 > - [Singapore](../concepts/numbers/phone-number-management-for-singapore.md)
 > - [Slovakia](../concepts/numbers/phone-number-management-for-slovakia.md)
+> - [South Korea](../concepts/numbers/phone-number-management-for-south-korea.md)
 > - [Spain](../concepts/numbers/phone-number-management-for-spain.md)
 > - [Sweden](../concepts/numbers/phone-number-management-for-sweden.md)
 > - [Switzerland](../concepts/numbers/phone-number-management-for-switzerland.md)
diff --git a/articles/communication-services/toc.yml b/articles/communication-services/toc.yml
@@ -1061,6 +1061,8 @@ items:
       href: concepts/numbers/phone-number-management-for-singapore.md
     - name: Phone number management for Slovakia
       href: concepts/numbers/phone-number-management-for-slovakia.md
+    - name: Phone number management for South Korea
+      href: concepts/numbers/phone-number-management-for-south-korea.md
     - name: Phone number management for Spain
       href: concepts/numbers/phone-number-management-for-spain.md
     - name: Phone number management for Sweden
diff --git a/articles/container-apps/jobs.md b/articles/container-apps/jobs.md
@@ -35,7 +35,7 @@ The following table compares common scenarios for apps and jobs:
 | A continuously running service that processes messages from an Azure Service Bus queue | App | Configure a [custom scale rule](scale-app.md#custom). |
 | A job that processes a single message or a small batch of messages from an Azure queue and exits | Job | Use the *Event* job type and [configure a custom scale rule](tutorial-event-driven-jobs.md) to trigger job executions. |
 | A background task that's triggered on-demand and exits when finished | Job | Use the *Manual* job type and [start executions](#start-a-job-execution-on-demand) manually or programmatically using an API. |
-| A self-hosted GitHub Actions runner that runs a workflow on demand | Job | Use the *Event* job type and [configure a GitHub Actions scale rule](tutorial-ci-cd-runners-jobs.md?pivots=container-apps-jobs-self-hosted-ci-cd-azure-pipelines). |
+| A self-hosted GitHub Actions runner or Azure Pipelines agent | Job | Use the *Event* job type and configure a [GitHub Actions](tutorial-ci-cd-runners-jobs.md?pivots=container-apps-jobs-self-hosted-ci-cd-github-actions) or [Azure Pipelines](tutorial-ci-cd-runners-jobs.md?pivots=container-apps-jobs-self-hosted-ci-cd-azure-pipelines) scale rule. |
 | An Azure Functions app | App | [Deploy Azure Functions to Container Apps](../azure-functions/functions-container-apps-hosting.md). |
 | An event-driven app using the Azure WebJobs SDK | App | [Configure a scale rule](scale-app.md#custom) for each event source. |
 
diff --git a/articles/event-hubs/private-link-service.md b/articles/event-hubs/private-link-service.md
@@ -197,7 +197,7 @@ There are four provisioning states:
 2. In the search bar, type in **event hubs**.
 3. Select the **namespace** that you want to manage.
 4. Select the **Networking** tab.
-5. Go to the appropriate section below based on the operation you want to: approve, reject, or remove.
+5. Go to the appropriate following section based on the operation you want to: approve, reject, or remove.
 
 ### Approve a private endpoint connection
 1. If there are any connections that are pending, you see a connection listed with **Pending** in the provisioning state. 
@@ -252,11 +252,10 @@ Aliases:  <event-hubs-namespace-name>.servicebus.windows.net
 
 ## Limitations and design considerations
 
-**Pricing**: For pricing information, see [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link/).
-
-**Limitations**:  This feature is available in all Azure public regions.
-
-**Maximum number of private endpoints per Event Hubs namespace**: 120.
+- For pricing information, see [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link/).
+- This feature is available in all Azure public regions.
+- Maximum number of private endpoints per Event Hubs namespace: 120.
+- The traffic is blocked at the application layer, not at the TCP layer. Therefore, you see TCP connections or `nslookup` operations succeeding against the public endpoint even though the public access is disabled. 
 
 For more, see [Azure Private Link service: Limitations](../private-link/private-link-service-overview.md#limitations)
 
diff --git a/articles/service-bus-messaging/private-link-service.md b/articles/service-bus-messaging/private-link-service.md
diff --git a/articles/service-bus-messaging/service-bus-prefetch.md b/articles/service-bus-messaging/service-bus-prefetch.md
diff --git a/articles/service-fabric/service-fabric-keyvault-references.md b/articles/service-fabric/service-fabric-keyvault-references.md
diff --git a/articles/spring-apps/includes/quickstart-deploy-java-native-image-app/deploy-enterprise-plan.md b/articles/spring-apps/includes/quickstart-deploy-java-native-image-app/deploy-enterprise-plan.md
