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

Author: roygara

articles/aks/create-node-pools.md

@@ -155,21 +155,10 @@ The Azure Linux container host for AKS is an open-source Linux distribution avai
 
 ### Migrate Ubuntu nodes to Azure Linux nodes
 
-1. [Add an Azure Linux node pool into your existing cluster](#add-an-azure-linux-node-pool).
+You can migrate your existing Ubuntu nodes to Azure Linux using one of the following methods:
 
-    > [!NOTE]
-    > When adding a new Azure Linux node pool, you need to add at least one as `--mode System`. Otherwise, AKS won't allow you to delete your existing Ubuntu node pool.
-
-2. [Cordon the existing Ubuntu nodes](resize-node-pool.md#cordon-the-existing-nodes).
-3. [Drain the existing Ubuntu nodes](resize-node-pool.md#drain-the-existing-nodes).
-4. Remove the existing Ubuntu nodes using the [`az aks delete`][az-aks-delete] command.
-
-    ```azurecli-interactive
-    az aks nodepool delete \
-        --resource-group myResourceGroup \
-        --cluster-name myAKSCluster \
-        --name mynodepool
-    ```
+* [Remove existing node pools and add new Azure Linux node pools](../azure-linux/tutorial-azure-linux-migration.md#add-azure-linux-node-pools-and-remove-existing-node-pools).
+* [In-place OS SKU migration (preview)](../azure-linux/tutorial-azure-linux-migration.md#in-place-os-sku-migration-preview).
 
 ## Node pools with unique subnets
 

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

@@ -38,7 +38,7 @@ To resolve this issue, delete the appliance and update the appliance YAML file.
 
 ### Appliance Network Unavailable 
 
-If Arc resource bridge is experiencing a network communication problem, you may see an "Appliance Network Unavailable" error when trying to perform an action that interacts with the resource bridge or an extension operating on top of the bridge. This error can also surface as "Error while dialing dial tcp xx.xx.xxx.xx:55000: connect: no route to host" and this is typically a network communication problem. The problem could be that communication from the host to the Arc resource bridge VM needs to be opened with the help of your network administrator. It could be that there was a temporary network issue not allowing the host to reach the Arc resource bridge VM and once the network issue is resolved, you can retry the operation. 
+If Arc resource bridge is experiencing a network communication problem or is offline, you may see an "Appliance Network Unavailable" error when trying to perform an action that interacts with the resource bridge or an extension operating on top of the bridge. In general, any network or infrastructure connectivity issue to the appliance VM may cause this error. This error can also surface as "Error while dialing dial tcp xx.xx.xxx.xx:55000: connect: no route to host" and this is typically a network communication problem. The problem could be that communication from the host to the Arc resource bridge VM needs to be opened with the help of your network administrator. It could be that there was a temporary network issue not allowing the host to reach the Arc resource bridge VM and once the network issue is resolved, you can retry the operation. You may also need to check that the appliance VM for Arc resource bridge is not stopped. In the case of Azure Stack HCI, the host storage may be full which has caused the appliance VM to pause and the storage will need to be addressed. 
 
 ### Connection closed before server preface received
 

articles/azure-functions/language-support-policy.md

@@ -15,7 +15,7 @@ Azure Functions runtime is built around various components, including operating
 
 ### Notification phase
 
-The Functions team sends notification emails to function app users about upcoming language version retirements. The notifications are sent at least one year before the date of retirement. When you receive the notification, you should prepare to upgrade functions apps to use to a supported version.
+The Functions team sends notification emails to function app users about upcoming language version retirements. When you receive the notification, you should prepare to upgrade functions apps to use to a supported version.
 
 ### Retirement phase
 

articles/azure-linux/tutorial-azure-linux-migration.md

@@ -26,7 +26,7 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 | Azure NetApp Files features | Azure public cloud availability |  Azure Government availability |
 |:--- |:--- |:--- |
 | Azure NetApp Files backup | Public preview | No |
-| Azure NetApp Files large volumes | Public preview | No |
+| Azure NetApp Files large volumes | Public preview | Public preview [(select regions)](large-volumes-requirements-considerations.md#supported-regions) |
 
 ## Portal access
 

articles/azure-netapp-files/azure-government.md

@@ -43,6 +43,7 @@ The following requirements and considerations apply to large volumes. For perfor
     | Ultra | 100 to 500 | 10,240 | 
 
 * Large volumes aren't currently supported with standard storage with cool access.
+
 ## Supported regions
 
 Support for Azure NetApp Files large volumes is available in the following regions:
@@ -67,6 +68,7 @@ Support for Azure NetApp Files large volumes is available in the following regio
 * UAE North
 * UK West
 * UK South
+* US Gov Virginia 
 * West Europe
 * West US
 * West US 2

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -15,7 +15,6 @@ ms.date: 09/28/2022
 > * [Node.js](../nosql/sdk-nodejs.md)
 > * [Java SDK v4](../nosql/sdk-java-v4.md)
 > * [Async Java SDK v2](../nosql/sdk-java-async-v2.md)
-> * [Sync Java SDK v2](../nosql/sdk-java-v2.md)
 > * [Spring Data v2](../nosql/sdk-java-spring-data-v2.md)
 > * [Spring Data v3](../nosql/sdk-java-spring-data-v3.md)
 > * [Spring Data v5](../nosql/sdk-java-spring-data-v5.md)

articles/cosmos-db/includes/cosmos-db-sdk-list.md

@@ -938,8 +938,6 @@
           href: sdk-java-v4.md
         - name: Async Java SDK v2 (legacy)
           href: sdk-java-async-v2.md
-        - name: Sync Java SDK v2 (legacy)
-          href: sdk-java-v2.md
         - name: Spring Data Connector v2 (legacy)
           href: sdk-java-spring-data-v2.md
         - name: Spring Data Connector v3

articles/cosmos-db/nosql/TOC.yml

@@ -89,7 +89,7 @@ DocumentCollection createdCollection = client.createCollection(databaseUri, coll
 
 # [Sync Java V2 SDK](#tab/sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 DocumentCollection lwwCollection = new DocumentCollection();
@@ -274,7 +274,7 @@ DocumentCollection createdCollection = client.createCollection(databaseUri, coll
 
 # [Sync Java V2 SDK](#tab/sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 DocumentCollection udpCollection = new DocumentCollection();
@@ -384,7 +384,7 @@ DocumentCollection createdCollection = client.createCollection(databaseUri, coll
 
 # [Sync Java V2 SDK](#tab/sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 DocumentCollection manualCollection = new DocumentCollection();
@@ -478,7 +478,7 @@ for (Conflict conflict : response.getResults()) {
 ```
 # [Sync Java V2 SDK](#tab/v2sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 Iterator<Conflict> conflictsIterator = client.readConflicts(this.collectionLink, null).getQueryIterator();

articles/cosmos-db/nosql/how-to-manage-conflicts.md

@@ -20,7 +20,7 @@ ms.custom: devx-track-csharp
 
 The API for NoSQL in Azure Cosmos DB supports registering and invoking stored procedures, triggers, and user-defined functions (UDFs) written in JavaScript. After you define one or more stored procedures, triggers, or user-defined functions, you can load and view them in the [Azure portal](https://portal.azure.com/) by using Data Explorer.
 
-You can use the API for NoSQL SDK across multiple platforms including [.NET v2 (legacy)](sdk-dotnet-v2.md), [.NET v3](sdk-dotnet-v3.md), [Java](sdk-java-v2.md), [JavaScript](sdk-nodejs.md), or [Python](sdk-python.md) SDKs to do these tasks. If you haven't worked with one of these SDKs before, see the quickstart article for the appropriate SDK:
+You can use the API for NoSQL SDK across multiple platforms including [.NET v2 (legacy)](sdk-dotnet-v2.md), [.NET v3](sdk-dotnet-v3.md), [Java](/java/api/overview/azure/cosmos-readme), [JavaScript](sdk-nodejs.md), or [Python](sdk-python.md) SDKs to do these tasks. If you haven't worked with one of these SDKs before, see the quickstart article for the appropriate SDK:
 
 | SDK | Getting started |
 | :--- | :--- |