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

Author: tamram

articles/aks/azure-cni-overlay.md

@@ -43,7 +43,7 @@ Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address spa
 
 ## IP address planning
 
-- **Cluster Nodes**: Cluster nodes go into a subnet in your VNet, so verify you have a subnet large enough to account for future scale. A simple `/24` subnet can host up to 251 nodes (the first three IP addresses in a subnet are reserved for management operations).
+- **Cluster Nodes**: Cluster nodes go into a subnet in your VNet, so verify you have a subnet large enough to account for future scale. Cluster can't scale to another subnet but you can add new nodepools in another subnet within the same VNet for expansion. A simple `/24` subnet can host up to 251 nodes (the first three IP addresses in a subnet are reserved for management operations).
 
 - **Pods**: The overlay solution assigns a `/24` address space for pods on every node from the private CIDR that you specify during cluster creation. The `/24` size is fixed and can't be increased or decreased. You can run up to 250 pods on a node. When planning the pod address space, ensure that the private CIDR is large enough to provide `/24` address spaces for new nodes to support future cluster expansion.
 

articles/app-service/environment/migrate.md

@@ -3,7 +3,7 @@ title: Migrate to App Service Environment v3 by using the migration feature
 description: Overview of the migration feature for migration to App Service Environment v3
 author: seligj95
 ms.topic: article
-ms.date: 03/20/2023
+ms.date: 04/07/2023
 ms.author: jordanselig
 ms.custom: references_regions
 ---
@@ -90,6 +90,7 @@ If your App Service Environment doesn't pass the validation checks or you try to
 |`<ZoneRedundant><DedicatedHosts><ASEv3/ASE>` is not available in this location. |This error appears if you're trying to migrate an App Service Environment in a region that doesn't support one of your requested features. |Migrate using one of the [manual migration options](migration-alternatives.md) if you want to migrate immediately. Otherwise, wait for the migration feature to support this App Service Environment configuration.  |
 |Migrate cannot be called on this ASE until the active upgrade has finished.    |App Service Environments can't be migrated during platform upgrades. You can set your [upgrade preference](how-to-upgrade-preference.md) from the Azure portal. In some cases, an upgrade is initiated when visiting the migration page if your App Service Environment isn't on the current build.  |Wait until the upgrade finishes and then migrate.   |
 |App Service Environment management operation in progress.    |Your App Service Environment is undergoing a management operation. These operations can include activities such as deployments or upgrades. Migration is blocked until these operations are complete.   |You can migrate once these operations are complete.  |
+|Migrate is not available for this subscription|Support needs to be engaged for migrating this App Service Environment.|Open a support case to engage support to resolve your issue.|
 
 ## Overview of the migration process using the migration feature
 

articles/application-gateway/media/tutorial-protect-application-gateway/enable-ddos-vnet.png

@@ -1,22 +1,22 @@
 ---
-title: 'Tutorial: Protect your application gateway with Azure DDoS Protection Standard'
+title: 'Tutorial: Protect your application gateway with Azure DDoS Network Protection'
 titleSuffix: Azure Application Gateway
 description: Learn how to set up an application gateway and protect it with Azure DDoS protection
 services: application-gateway
 author: duongau
 ms.author: duau
-ms.date: 12/21/2022
+ms.date: 04/06/2023
 ms.topic: quickstart
 ms.service: application-gateway
 ms.custom: template tutorial
 ---
 
-# Tutorial: Protect your application gateway with Azure DDoS Protection Standard
+# Tutorial: Protect your application gateway with Azure DDoS Network Protection
 
-This article helps you create an Azure Application Gateway with a DDoS protected virtual network. Azure DDoS Protection Standard enables enhanced DDoS mitigation capabilities such as adaptive tuning, attack alert notifications, and monitoring to protect your application gateways from large scale DDoS attacks.
+This article helps you create an Azure Application Gateway with a DDoS protected virtual network. Azure DDoS Network Protection enables enhanced DDoS mitigation capabilities such as adaptive tuning, attack alert notifications, and monitoring to protect your application gateways from large scale DDoS attacks.
 
 > [!IMPORTANT]
-> Azure DDoS Protection incurs a cost when you use the Standard SKU. Overages charges only apply if more than 100 public IPs are protected in the tenant. Ensure you delete the resources in this tutorial if you aren't using the resources in the future. For information about pricing, see [Azure DDoS Protection Pricing]( https://azure.microsoft.com/pricing/details/ddos-protection/). For more information about Azure DDoS protection, see [What is Azure DDoS Protection?](../ddos-protection/ddos-protection-overview.md).
+> Azure DDoS Protection incurs a cost when you use the Network Protection SKU. Overages charges only apply if more than 100 public IPs are protected in the tenant. Ensure you delete the resources in this tutorial if you aren't using the resources in the future. For information about pricing, see [Azure DDoS Protection Pricing]( https://azure.microsoft.com/pricing/details/ddos-protection/). For more information about Azure DDoS protection, see [What is Azure DDoS Protection?](../ddos-protection/ddos-protection-overview.md).
 
 In this tutorial, you learn how to:
 
@@ -156,7 +156,7 @@ Review the settings on the **Review + create** tab, and then select **Create** t
 
 ## Enable DDoS protection
 
-Azure DDoS protection Standard is enabled at the virtual network where the resource you want to protect reside. 
+Azure DDoS Network Protection is enabled at the virtual network where the resource you want to protect reside. 
 
 1. In the search box at the top of the portal, enter **Virtual network**. Select **Virtual networks** in the search results.
 
@@ -168,7 +168,7 @@ Azure DDoS protection Standard is enabled at the virtual network where the resou
 
 5. In the pull-down box in DDoS protection plan, select **myDDoSProtectionPlan**.
 
-    :::image type="content" source="./media/tutorial-protect-application-gateway/enable-ddos-vnet.png" alt-text="Screenshot of ddos protection.":::
+    :::image type="content" source="./media/tutorial-protect-application-gateway/enable-ddos-vnet.png" alt-text="Screenshot of D D o S network protection.":::
 
 6. Select **Save**.
 
@@ -276,4 +276,4 @@ To delete the resource group:
 Advance to the next article to learn how to:
 
 > [!div class="nextstepaction"]
-> [Configure an application gateway with TLS termination using the Azure portal](create-ssl-portal.md)
+> [Configure an application gateway with TLS termination using the Azure portal](create-ssl-portal.md)

articles/application-gateway/tutorial-protect-application-gateway-ddos.md

@@ -230,7 +230,7 @@ Yes, geo-replication of caches in VNets is supported with caveats:
 - Geo-replication between caches in the same VNet is supported.
 - Geo-replication between caches in different VNets is also supported.
   - If the VNets are in the same region, you can connect them using [VNet peering](../virtual-network/virtual-network-peering-overview.md) or a [VPN Gateway VNet-to-VNet connection](../vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md).
-  - If the VNets are in different regions, geo-replication using VNet peering is supported. A client VM in VNet 1 (region 1) isn't able to access the cache in VNet 2 (region 2) using its DNS name because of a constraint with Basic internal load balancers. For more information about VNet peering constraints, see [Virtual Network - Peering - Requirements and constraints](../virtual-network/virtual-network-manage-peering.md#requirements-and-constraints). We recommend using a VPN Gateway VNet-to-VNet connection.
+  - If the VNets are in different regions, geo-replication using VNet peering is not supported. A client VM in VNet 1 (region 1) isn't able to access the cache in VNet 2 (region 2) using its DNS name because of a constraint with Basic internal load balancers. For more information about VNet peering constraints, see [Virtual Network - Peering - Requirements and constraints](../virtual-network/virtual-network-manage-peering.md#requirements-and-constraints). We recommend using a VPN Gateway VNet-to-VNet connection.
 
 To configure your VNet effectively and avoid geo-replication issues, you must configure both the inbound and outbound ports correctly. For more information on avoiding the most common VNet misconfiguration issues, see [Geo-replication peer port requirements](cache-how-to-premium-vnet.md#geo-replication-peer-port-requirements).
 

articles/azure-cache-for-redis/cache-how-to-geo-replication.md

@@ -14,19 +14,18 @@ ms.subservice: pstn
 # List of Session Border Controllers certified for Azure Communication Services direct routing
 This document contains a list of Session Border Controllers certified for Azure Communication Services direct routing. It also includes known limitations.
 
-Microsoft is working with the selected Session Border Controllers (SBC) vendors certified for Teams Direct Routing to work with Azure direct routing. You can watch the progress on this page. While the SBC, certified for Teams Direct Routing, can work with Azure direct routing, we encourage not to put any workload on the SBC until it appears on this page. We also do not support the uncertified SBC. While Azure direct routing is built on the same backend as Teams Direct Routing, there are some differences. The certification covers comprehensive validation of the SBC for the Azure direct routing.
+Microsoft is working with the selected Session Border Controllers (SBC) vendors certified for Teams Direct Routing to work with Azure direct routing. You can watch the progress on this page. While the SBC, certified for Teams Direct Routing, can work with Azure direct routing, we encourage not to put any workload on the SBC until it appears on this page. We also don't support the uncertified SBC. While Azure direct routing is built on the same backend as Teams Direct Routing, there are some differences. The certification covers comprehensive validation of the SBC for the Azure direct routing.
 
 Microsoft works with each vendor to:
 - Jointly work on the SIP interconnection protocols.
 - Perform intense tests using a third-party lab. Only devices that pass the tests are certified.
-- Run daily tests with all certified devices in production and pre-production environments. Validating the devices in pre-production environments guarantees that new versions of Azure Communication Services code in the cloud will work with certified SBCs.
+- Run daily tests with all certified devices in production and preproduction environments. Validating the devices in preproduction environments guarantees that new versions of Azure Communication Services code in the cloud work with certified SBCs.
 - Establish a joint support process with the SBC vendors.
 
 [!INCLUDE [Public Preview](../../includes/public-preview-include-document.md)]
 [!INCLUDE [Dynamics 365 Omnichannel Notice](../includes/direct-routing-omnichannel-note.md)]
 
 Media bypass is not yet supported by Azure Communication Services. 
-Early media is not supported by a web-based client.
 The table that follows list devices certified for Azure Communication Services direct routing.
 
 If you have any questions about the SBC certification program for Communication Services direct routing, contact [email protected].

articles/communication-services/concepts/telephony/certified-session-border-controllers.md

@@ -14,8 +14,6 @@ items:
       href: quickstart-configure-dev-box-service.md
     - name: Create a dev box
       href: quickstart-create-dev-box.md
-    - name: Connect with Remote Desktop App
-      href: tutorial-connect-to-dev-box-with-remote-desktop-app.md
 - name: Tutorials
   expanded: true
   items:
@@ -26,7 +24,7 @@ items:
   items:
     - name: Key concepts
       href: concept-dev-box-concepts.md
-    - name: Components common to Dev Box and ADE
+    - name: Components common to Dev Box and Deployment Environments
       href: concept-common-components.md
 - name: How-to guides
   expanded: true

articles/dev-box/toc.yml

@@ -229,6 +229,8 @@
         href: ../site-recovery/site-recovery-overview.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
       - name: Azure Blob Storage
         href: ../storage/common/storage-disaster-recovery-guidance.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
+      - name: Azure Storage Mover
+        href: reliability-azure-storage-mover.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json 
       - name: Azure SQL
         href: /azure/azure-sql/database/high-availability-sla?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
       - name: Azure Virtual WAN