Merge pull request #217243 from MicrosoftDocs/main

11/04 AM Publish

Author: huypub

.openpublishing.publish.config.json

@@ -849,11 +849,17 @@
       "branch_mapping": {}
     },
     {
-      "path_to_root": "azure-cosmos-dotnet-v3",
+      "path_to_root": "cosmos-db-nosql-dotnet-samples",
       "url": "https://github.com/azure-samples/cosmos-db-nosql-dotnet-samples",
       "branch": "main",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "cosmos-db-nosql-python-samples",
+      "url": "https://github.com/azure-samples/cosmos-db-nosql-python-samples",
+      "branch": "main",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azure-cosmos-db-table-dotnet-v12",
       "url": "https://github.com/Azure-Samples/cosmos-db-table-api-dotnet-samples",

articles/active-directory-domain-services/policy-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Built-in policy definitions for Azure Active Directory Domain Services
 description: Lists Azure Policy built-in policy definitions for Azure Active Directory Domain Services. These built-in policy definitions provide common approaches to managing your Azure resources.
-ms.date: 09/12/2022
+ms.date: 11/04/2022
 ms.service: active-directory
 ms.subservice: domain-services
 author: justinha

articles/aks/api-server-vnet-integration.md

@@ -22,12 +22,9 @@ API Server VNet Integration is supported for public or private clusters, and pub
 
 ## Region availability
 
-API Server VNet Integration is available in the following regions at this time:
+API Server VNet Integration is available in all Public Azure regions except the following at this time:
 
-- eastus2
-- northcentralus
-- westcentralus
-- westus2
+- southcentralus
 
 ## Prerequisites
 

articles/aks/configure-kube-proxy.md

@@ -116,6 +116,12 @@ Configure your cluster using `az aks update` and pass in the configuration file:
 az aks update -g <resourceGroup> -n <clusterName> --kube-proxy-config kube-proxy.json
 ```
 
+### Limitations
+
+When using kube-proxy IPVS, the following restrictions apply:
+
+- Azure Network Policy is not supported.
+
 ## Next steps
 
 Learn more about utilizing the Standard Load Balancer for inbound traffic at the [AKS Standard Load Balancer documentation](load-balancer-standard.md).

articles/aks/policy-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Built-in policy definitions for Azure Kubernetes Service
 description: Lists Azure Policy built-in policy definitions for Azure Kubernetes Service. These built-in policy definitions provide common approaches to managing your Azure resources.
-ms.date: 09/12/2022
+ms.date: 11/04/2022
 ms.topic: reference
 ms.custom: subject-policy-reference
 ---

articles/api-management/policy-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Built-in policy definitions for Azure API Management
 description: Lists Azure Policy built-in policy definitions for Azure API Management. These built-in policy definitions provide approaches to managing your Azure resources.
-ms.date: 09/12/2022
+ms.date: 11/04/2022
 author: dlepow
 ms.author: danlep
 ms.service: api-management

articles/app-service/environment/networking.md

@@ -141,10 +141,6 @@ In addition to setting up DNS, you also need to enable it in the [App Service En
 
 The apps in your App Service Environment will use the DNS that your virtual network is configured with. If you want some apps to use a different DNS server, you can manually set it on a per app basis, with the app settings `WEBSITE_DNS_SERVER` and `WEBSITE_DNS_ALT_SERVER`. `WEBSITE_DNS_ALT_SERVER` configures the secondary DNS server. The secondary DNS server is only used when there is no response from the primary DNS server.
 
-## Limitations
-
-While App Service Environment does deploy into your virtual network, you currently cannot use Azure Network Watcher or NSG flow to monitor outbound traffic.
-
 ## More resources
 
 - [Environment variables and app settings reference](../reference-app-settings.md)

articles/app-service/overview-vnet-integration.md

@@ -44,8 +44,6 @@ When all traffic routing is enabled, all outbound traffic is sent into your virt
 
 The feature supports two virtual interface per worker. Two virtual interfaces per worker means two regional virtual network integrations per App Service plan. The apps in the same App Service plan can only use one of the virtual network integrations to a specific subnet. If you need an app to connect to additional virtual networks or additional subnets in the same virtual network, you need to create another App Service plan. The virtual interfaces used isn't a resource that customers have direct access to.
 
-Because of the nature of how this technology operates, the traffic that's used with virtual network integration doesn't show up in Azure Network Watcher or NSG flow logs.
-
 ### Subnet requirements
 
 Virtual network integration depends on a dedicated subnet. When you create a subnet, the Azure subnet loses five IPs from the start. One address is used from the integration subnet for each plan instance. If you scale your app to four instances, then four addresses are used.

articles/app-service/policy-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Built-in policy definitions for Azure App Service
 description: Lists Azure Policy built-in policy definitions for Azure App Service. These built-in policy definitions provide common approaches to managing your Azure resources.
-ms.date: 09/12/2022
+ms.date: 11/04/2022
 ms.topic: reference
 ms.custom: subject-policy-reference
 ---