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

Author: duongau

articles/azure-functions/create-first-function-vs-code-python.md

@@ -91,7 +91,7 @@ In this section, you use Visual Studio Code to create a local Azure Functions pr
 7. Replace the `app.route()` method call with the following code:
 
     ```python
-    @app.route(route="hello", auth_level=func.AuthLevel.ANONYMOUS)
+    @app.route(route="hello", http_auth_level=func.AuthLevel.ANONYMOUS)
     ```
 
     This code enables your HTTP function endpoint to be called in Azure without having to provide an [Authorization keys](functions-bindings-http-webhook-trigger.md#authorization-keys). Local execution doesn't require authorization keys. 
@@ -100,7 +100,7 @@ In this section, you use Visual Studio Code to create a local Azure Functions pr
 
     ```python
     @app.function_name(name="HttpTrigger1")
-    @app.route(route="hello", auth_level=func.AuthLevel.ANONYMOUS)
+    @app.route(route="hello", http_auth_level=func.AuthLevel.ANONYMOUS)
     def test_function(req: func.HttpRequest) -> func.HttpResponse:
         logging.info('Python HTTP trigger function processed a request.')
 

articles/azure-monitor/essentials/data-collection-transformations-structure.md

@@ -39,6 +39,8 @@ Transformations in a [data collection rule (DCR)](data-collection-rule-overview.
 
 
 
+### Required columns
+The output of every transformation must contain a valid timestamp in a column called `TimeGenerated` of type `datetime`. Make sure to include it in the final `extend` or `project` block! Creating or updating a DCR without `TimeGenerated` in the output of a transformation will lead to an error.
 
 ## Inline reference table
 The [datatable](/azure/data-explorer/kusto/query/datatableoperator?pivots=azuremonitor) operator isn't supported in the subset of KQL available to use in transformations. This operator would normally be used in KQL to define an inline query-time table. Use dynamic literals instead to work around this limitation.
@@ -329,4 +331,4 @@ Use [Identifier quoting](/azure/data-explorer/kusto/query/schema-entities/entity
 
 ## Next steps
 
-- [Create a data collection rule](../agents/data-collection-rule-azure-monitor-agent.md) and an association to it from a virtual machine using the Azure Monitor agent.
+- [Create a data collection rule](../agents/data-collection-rule-azure-monitor-agent.md) and an association to it from a virtual machine using the Azure Monitor agent.

articles/azure-video-indexer/toc.yml

@@ -96,6 +96,7 @@
   - name: Manage accounts
     items:
     - name: Manage access to your account
+      displayName: RBAC, User, Users
       href: restricted-viewer-role.md
     - name: Connect an existing account to ARM
       href: connect-classic-account-to-arm.md

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -3,7 +3,7 @@ title: Concepts - Network design considerations
 description: Learn about network design considerations for Azure VMware Solution
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 08/19/2022
+ms.date: 12/22/2022
 ---
 
 # Azure VMware Solution network design considerations
@@ -12,14 +12,14 @@ Azure VMware Solution offers a VMware private cloud environment accessible for u
 
 ## Azure VMware Solution compatibility with AS-Path Prepend
 
-Azure VMware Solution is incompatible with AS-Path Prepend for redundant ExpressRoute configurations and doesn't honor the outbound path selection from Azure towards on-premises.  If you're running 2 or more ExpressRoute paths between on-premises and Azure, and the listed [Prerequisites](#prerequisites) are true; you may experience impaired connectivity or no connectivity between your on-premises networks and Azure VMware Solution. The connectivity issue is caused when Azure VMware Solution doesn't see the AS-Path Prepend and uses ECMP to send traffic towards your environment over both ExR circuits. That action causes issues with stateful firewall inspection.
+Azure VMware Solution is incompatible with AS-Path Prepend for redundant ExpressRoute configurations and doesn't honor the outbound path selection from Azure towards on-premises. If you're running two or more ExpressRoute paths between on-premises and Azure, and the listed [Prerequisites](#prerequisites) are not met, you may experience impaired connectivity or no connectivity between your on-premises networks and Azure VMware Solution. The connectivity issue is caused when Azure VMware Solution doesn't see the AS-Path Prepend and uses equal cost multi-pathing (ECMP) to send traffic towards your environment over both ExpressRoute circuits. That action causes issues with stateful firewall inspection.
 
 ### Prerequisites
 
 For AS-Path Prepend, you'll need to verify that all of the following listed connections are true:
 
 > [!div class="checklist"]
-> * Both or all circuits are connected to Azure VMware Solution with global reach.
+> * Both or all circuits are connected to Azure VMware Solution with ExpressRoute Global Reach.
 > * The same netblocks are being advertised from two or more circuits.
 > * Stateful firewalls are in the network path.
 > * You're using AS-Path Prepend to force Azure to prefer one path over others.
@@ -29,7 +29,7 @@ Either 2 or 4 byte Public ASN numbers should be used and be compatible with Azur
 ## Management VMs and default routes from on-premises
 
 > [!IMPORTANT]
-> Azure VMware Solution Management VMs don't honor a default route from on-premises.
+> Azure VMware Solution Management VMs will not honor a default route from on-premises.
 
 If you're routing back to your on-premises networks using only a default route advertised towards Azure, the vCenter Server and NSX-T Manager VMs won't be compatible with that route.
 
@@ -98,7 +98,7 @@ The following diagram demonstrates how a single 0.0.0.0/0 is advertised to Azure
 > [!IMPORTANT]
 > An encapsulation protocol such as VXLAN or IPsec is required between the NVAs. Encapsulation is needed because the NVA NICs would learn the routes from Azure Route Server with the NVA as next hop and create a routing loop.
 
-There's an alternative to using an overlay. Apply secondary NICs in the NVA that won't learn the routes from Azure Route Server and configure UDRs so that Azure can route traffic to the remote environment over those NICs. You can find more details in [Enterprise-scale network topology and connectivity for Azure VMware Solution](https://learn.microsoft.com/azure/cloud-adoption-framework/scenarios/azure-vmware/eslz-network-topology-connectivity#scenario-2-a-third-party-nva-in-hub-azure-virtual-network-inspects-all-network-traffic).
+There's an alternative to using an overlay. Apply secondary NICs in the NVA that won't learn the routes from Azure Route Server and configure UDRs so that Azure can route traffic to the remote environment over those NICs. You can find more details in [Enterprise-scale network topology and connectivity for Azure VMware Solution](/azure/cloud-adoption-framework/scenarios/azure-vmware/eslz-network-topology-connectivity#scenario-2-a-third-party-nva-in-hub-azure-virtual-network-inspects-all-network-traffic).
 
 **This topology requires a complex initial set-up. Once the set-up is complete, the topology works as expected with minimal management overhead. See the following list of specific set-up complexities.**
 

articles/azure-vmware/concepts-network-design-considerations.md

@@ -4,7 +4,7 @@ description: Learn how to configure port mirroring to monitor network traffic th
 ms.topic: how-to
 ms.custom: contperf-fy22q1
 ms.service: azure-vmware
-ms.date: 04/11/2022
+ms.date: 12/22/2022
 
 # Customer intent: As an Azure service administrator, I want to configure port mirroring to monitor network traffic that involves forwarding a copy of each packet from one network switch port to another.
 
@@ -16,6 +16,9 @@ After deploying Azure VMware Solution, you can configure port mirroring from the
 
 In this how-to, you'll configure port mirroring to monitor network traffic, which involves forwarding a copy of each packet from one network switch port to another. 
 
+   >[!IMPORTANT]
+   >Port Mirroring is intended to be used as a temporary investigative tool and not a permanent network data collection feature. This is because NSX-T Data Center does not have the resoures to port mirror all traffic continuously. The IPFIX feature should be used if a continuous meta-data network flow logging solution is required.
+
 ## Prerequisites
 
 An Azure VMware Solution private cloud with access to the vCenter Server and NSX-T Manager interfaces. For more information, see the [Configure networking](tutorial-configure-networking.md) tutorial.

articles/azure-vmware/configure-port-mirroring-azure-vmware-solution.md

@@ -3,7 +3,7 @@ title: Configure VMware syslogs for Azure VMware Solution
 description: Learn how to configure diagnostic settings to collect VMware syslogs for your Azure VMware Solution private cloud.
 ms.topic: how-to 
 ms.service: azure-vmware
-ms.date: 12/07/2022
+ms.date: 12/22/2022
 
 #Customer intent: As an Azure service administrator, I want to collect VMware syslogs and store it in my storage account so that I can view the vCenter Server logs and analyze for any diagnostic purposes.
 
@@ -16,11 +16,12 @@ Diagnostic settings are used to configure streaming export of platform logs and
 In this article, you'll configure a diagnostic setting to collect VMware syslogs for your Azure VMware Solution private cloud. You'll store the syslog to a storage account to view the vCenter Server logs and analyze for diagnostic purposes. 
  >[!IMPORTANT]
    >The **VMware syslogs** contains the following logs:
-   >- NSX-T Data Center Distributed Firewall logs
+   >- vCenter Server logs
+   >- ESXi logs
+   >- vSAN logs
    >- NSX-T Manager logs
+   >- NSX-T Data Center Distributed Firewall logs
    >- NSX-T Data Center Gateway Firewall logs
-   >- ESXi logs
-   >- vCenter Server logs
    >- NSX-T Data Center Edge Appliance logs
 
 ## Prerequisites

articles/azure-vmware/configure-vmware-syslogs.md

@@ -3,7 +3,7 @@ title: Introduction
 description: Learn the features and benefits of Azure VMware Solution to deploy and manage VMware-based workloads in Azure. Azure VMware Solution SLA guarantees that Azure VMware management tools (vCenter Server and NSX Manager) will be available at least 99.9% of the time.
 ms.topic: overview
 ms.service: azure-vmware
-ms.date: 10/28/2022
+ms.date: 12/22/2022
 ms.custom: engagement-fy23
 ---
 
@@ -36,7 +36,7 @@ Frequency of 2.7Ghz and Turbo of 4.0Ghz.
 - 38.4TB storage capacity with all NVMe based SSDs (With Random Read of 636500 IOPS and Random Write of 223300 IOPS)
 - 1.5TB of NVMe Cache
 
-For pricing and region availability, see the [Azure VMware Solution pricing page](https://azure.microsoft.com/pricing/details/azure-vmware/) and see the [Products available by region page](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
+For pricing and region availability, see the [Azure VMware Solution pricing page](https://azure.microsoft.com/pricing/details/azure-vmware/) and see the [Products available by region page](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-vmware&regions=all).
 
 ## Hosts, clusters, and private clouds
 

articles/azure-vmware/introduction.md

@@ -4,7 +4,7 @@ description: This article describes how to move Azure VMware Solution subscripti
 ms.custom: "subject-moving-resources, engagement-fy23"
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 10/26/2022
+ms.date: 12/22/2022
 
 # Customer intent: As an Azure service administrator, I want to move my Azure VMware Solution subscription to another subscription.
 ---
@@ -18,7 +18,7 @@ This article describes how to move an Azure VMware Solution subscription to anot
 You should have at least contributor rights on both **source** and **target** subscriptions.
 
 >[!IMPORTANT]
->VNet and VNet gateway can't' be moved from one subscription to another. Additionally, moving your subscriptions has no impact on the management and workloads, like the vCenter, NSX, and workload virtual machines.
+>VNet and VNet gateway can't be moved from one subscription to another. Additionally, moving your subscriptions has no impact on the management and workloads, like the vCenter Server, NSX-T Data Center, vSAN, and workload virtual machines.
 
 ## Prepare and move
 

articles/azure-vmware/move-ea-csp-subscriptions.md

@@ -3,7 +3,7 @@ title: Rotate the cloudadmin credentials for Azure VMware Solution
 description: Learn how to rotate the vCenter Server credentials for your Azure VMware Solution private cloud. 
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 04/11/2022
+ms.date: 12/22/2022
 
 #Customer intent: As an Azure service administrator, I want to rotate my cloudadmin credentials so that the HCX Connector has the latest vCenter Server CloudAdmin credentials.
 
@@ -12,7 +12,7 @@ ms.date: 04/11/2022
 # Rotate the cloudadmin credentials for Azure VMware Solution
 
 >[!IMPORTANT]
->Currently, rotating your NSX-T Manager *admin* credentials isn't supported.  To rotate your NSX-T Manager password, submit a [support request](https://rc.portal.azure.com/#create/Microsoft.Support). This process might impact running HCX services.
+>Currently, rotating your NSX-T Manager *cloudadmin* credentials isn't supported.  To rotate your NSX-T Manager password, submit a [support request](https://rc.portal.azure.com/#create/Microsoft.Support). This process might impact running HCX services.
 
 In this article, you'll rotate the cloudadmin credentials (vCenter Server *CloudAdmin* credentials) for your Azure VMware Solution private cloud.  Although the password for this account doesn't expire, you can generate a new one at any time.
 
@@ -25,7 +25,7 @@ Consider and determine which services connect to vCenter Server as *cloudadmin@v
 
 One way to determine which services authenticate to vCenter Server with the cloudadmin user is to inspect vSphere events using the vSphere Client for your private cloud. After you identify such services, and before rotating the password, you must stop these services. Otherwise, the services won't work after you rotate the password. You'll also experience temporary locks on your vCenter Server CloudAdmin account, as these services continuously attempt to authenticate using a cached version of the old credentials. 
 
-Instead of using the cloudadmin user to connect services to vCenter, we recommend individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and Identity Concepts](./concepts-identity.md).
+Instead of using the cloudadmin user to connect services to vCenter Server, we recommend individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and Identity Concepts](./concepts-identity.md).
 
 ## Reset your vCenter Server credentials
 
@@ -48,7 +48,7 @@ To begin using Azure CLI:
 
 1. In your Azure VMware Solution private cloud, open an Azure Cloud Shell session.
 
-2. Update your vCenter *CloudAdmin* credentials.  Remember to replace **{SubscriptionID}**, **{ResourceGroup}**, and **{PrivateCloudName}** with your private cloud information. 
+2. Update your vCenter Server *CloudAdmin* credentials.  Remember to replace **{SubscriptionID}**, **{ResourceGroup}**, and **{PrivateCloudName}** with your private cloud information. 
 
    ```azurecli-interactive
    az resource invoke-action --action rotateVcenterPassword --ids "/subscriptions/{SubscriptionID}/resourceGroups/{ResourceGroup}/providers/Microsoft.AVS/privateClouds/{PrivateCloudName}" --api-version "2020-07-17-preview"