Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ds-qsrt1720714

Author: davidsmatlak

articles/azure-resource-manager/templates/template-functions-resource.md

@@ -2,7 +2,7 @@
 title: Template functions - resources
 description: Describes the functions to use in an Azure Resource Manager template to retrieve values about resources.
 ms.topic: conceptual
-ms.date: 04/28/2020
+ms.date: 05/20/2020
 ---
 # Resource functions for ARM templates
 
@@ -102,7 +102,7 @@ The following example returns the resource ID for a resource group lock.
 
 `list{Value}(resourceName or resourceIdentifier, apiVersion, functionValues)`
 
-The syntax for this function varies by name of the list operations. Each implementation returns values for the resource type that supports a list operation. The operation name must start with `list`. Some common usages are `listKeys` and `listSecrets`.
+The syntax for this function varies by name of the list operations. Each implementation returns values for the resource type that supports a list operation. The operation name must start with `list`. Some common usages are `listKeys`, `listKeyValue` and `listSecrets`.
 
 ### Parameters
 
@@ -123,6 +123,7 @@ The possible uses of list* are shown in the following table.
 | Resource type | Function name |
 | ------------- | ------------- |
 | Microsoft.AnalysisServices/servers | [listGatewayStatus](/rest/api/analysisservices/servers/listgatewaystatus) |
+| Microsoft.AppConfiguration] | [ListKeyValue](/rest/api/appconfiguration/configurationstores/listkeyvalue) |
 | Microsoft.AppConfiguration/configurationStores | ListKeys |
 | Microsoft.Automation/automationAccounts | [listKeys](/rest/api/automation/keys/listbyautomationaccount) |
 | Microsoft.Batch/batchAccounts | [listkeys](/rest/api/batchmanagement/batchaccount/getkeys) |

articles/event-grid/auth0-overview.md

@@ -12,6 +12,7 @@ ms.author: babanisa
 
 # Auth0 Partner Topics
 ![Auth0 Logo](./media/auth0-overview/auth0-logo.png)
+
 Auth0, the identity platform for application builders, provides developers and enterprises with the building blocks they need to secure their applications.
 
 The Auth0 Partner Topic allows you to use events that are emitted by Auth0’s system to accomplish a number of tasks. Engage with users in meaningful ways after the authentication or automate security and infrastructure tasks.

articles/event-grid/media/partner-onboarding-how-to/activate-partner-topic.png

@@ -30,10 +30,14 @@ Partner topics allow you to publish events to Azure Event Grid for multitenant c
 #### Partner flow
 
 1. Create an Azure tenant if you don't already have one.
-1. Using CLI create a new Event Grid `partnerRegistration`. This resource includes information such as display name, description, setup URI and so on. 
-![Create Partner Topic](./media/partner-onboarding-how-to/create-partner-registration.png)
+1. Using CLI create a new Event Grid `partnerRegistration`. This resource includes information such as display name, description, setup URI and so on.
+
+    ![Create Partner Topic](./media/partner-onboarding-how-to/create-partner-registration.png)
+
 1. Create one or more `partnerNamespaces` in each region you want to publish events. As part of this, Event Grid service will provision a publishing endpoint (for example, https://contoso.westus-1.eventgrid.azure.net/api/events) and access keys.
-![Create Partner Namespace](./media/partner-onboarding-how-to/create-partner-namespace.png)
+
+    ![Create Partner Namespace](./media/partner-onboarding-how-to/create-partner-namespace.png)
+
 1. Provide a way for customers to register in your system that they would like a partner topic.
 1. Contact the Event Grid team to let us know you would like your Partner Topic Type to become public.
 
@@ -42,9 +46,12 @@ Partner topics allow you to publish events to Azure Event Grid for multitenant c
 1. Your customer will visit the Azure portal to note the Azure Subscription ID and Resource Group they would like the Partner Topic created in.
 1. The customer will request a Partner Topic via your system. In response, you'll create an Event Tunnel your Partner Namespace.
 1. Event Grid will create a **Pending** Partner Topic in the customer's Azure Subscription and Resource Group.
-![Create Event Channel](./media/partner-onboarding-how-to/create-event-tunnel-partner-topic.png)
+
+    ![Create Event Channel](./media/partner-onboarding-how-to/create-event-tunnel-partner-topic.png)
+
 1. The customer activates the Partner Topic via the Azure portal. Events may now flow from your service to the customer's Azure Subscription.
-![Activate Partner Topic](./media/partner-onboarding-how-to/activate-partner-topic.png)
+
+    ![Activate Partner Topic](./media/partner-onboarding-how-to/activate-partner-topic.png)
 
 ## Resource Model
 
@@ -60,21 +67,14 @@ Below is the resource model for Partner Topics.
     Only Microsoft approved partnerRegistrations are discoverable by customers.
 * Scope: Created in partner's Azure Subscription. Metadata visible to customers once public.
 
-### Event Types
-* Resource: `partnerRegistrations/eventTypes`
-* Used by: Partners
-* Description: Captures metadata about event types supported by a partner registration.
-* Scope: Discoverable by customers once made public. Lives in a partner’s subscription as a child resource of Partner Registration.
-		
-
 ### Partner Namespaces
 * Resource: partnerNamespaces
 * Used by: Partners
 * Description: Provides a regional resource for publishing customer events to. Each Partner Namespace has a publishing endpoint and auth keys. The namespace is also how the partner requests a Partner Topic for a given customer and lists active customers.
 * Scope: Lives in partner’s subscription.
 
-### Event Tunnels
-* Resource: `partnerNamespaces/eventTunnels`
+### Event Channel
+* Resource: `partnerNamespaces/eventChannels`
 * Used by: Partners
 * Description: The Event Tunnels are a mirror of the customer's Partner Topic. By creating an Event Tunnel and specifying the customer's Azure Subscription and resource Group in the metadata, you're signaling to Event Grid to create a Partner Topic for the customer. Event Grid will issue an ARM call to create a corresponding partnerTopic in the customer’s subscription. The partner topic will be created in a "pending" state. There’s a 1-1 link between each eventTunnel and a partnerTopic.
 * Scope: Lives in partner’s subscription.

articles/event-grid/media/partner-onboarding-how-to/create-event-tunnel-partner-topic.png

@@ -134,12 +134,12 @@
         href: event-schema-subscriptions.md
   - name: Partner topics
     items:
-    - name: Overview of Partner topics
+    - name: Overview of partner topics
       href: partner-topics-overview.md
     - name: Auth0
       href: auth0-overview.md
     - name: Become and Event Grid Partner
-    href: partner-onboarding-overview.md
+      href: partner-onboarding-overview.md
   - name: Event Domains
     href: event-domains.md
   - name: Event schema formats

articles/event-grid/media/partner-onboarding-how-to/create-partner-namespace.png

@@ -4,19 +4,16 @@ titlesuffix: Azure Virtual Network
 description: Learn how Azure routes virtual network traffic, and how you can customize Azure's routing.
 services: virtual-network
 documentationcenter: na
-author: malopMSFT
+author: KumudD
 manager: 
-editor: v-miegge
-tags:
-
 ms.service: virtual-network
 ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
 ms.date: 10/26/2017
-ms.author: malop
-ms.reviewer: kumud
+ms.author: aldomel
+
 ---
 
 # Virtual network traffic routing
@@ -166,7 +163,7 @@ When you override the 0.0.0.0/0 address prefix, in addition to outbound traffic
 
 If your virtual network is connected to an Azure VPN gateway, do not associate a route table to the [gateway subnet](../vpn-gateway/vpn-gateway-about-vpn-gateway-settings.md?toc=%2fazure%2fvirtual-network%2ftoc.json#gwsub) that includes a route with a destination of 0.0.0.0/0. Doing so can prevent the gateway from functioning properly. For details, see the *Why are certain ports opened on my VPN gateway?* question in the [VPN Gateway FAQ](../vpn-gateway/vpn-gateway-vpn-faq.md?toc=%2fazure%2fvirtual-network%2ftoc.json#gatewayports).
 
-See [DMZ between Azure and your on-premises datacenter](/azure/architecture/reference-architectures/dmz/secure-vnet-hybrid?toc=%2fazure%2fvirtual-network%2ftoc.json) and [DMZ between Azure and the Internet](/azure/architecture/reference-architectures/dmz/secure-vnet-dmz?toc=%2fazure%2fvirtual-network%2ftoc.json) for implementation details when using virtual network gateways and virtual appliances between the Internet and Azure.
+See [DMZ between Azure and your on-premises datacenter](/azure/architecture/reference-architectures/dmz/secure-vnet-hybrid?toc=%2fazure%2fvirtual-network%2ftoc.json) for implementation details when using virtual network gateways between the Internet and Azure.
 
 ## Routing example