Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-roles-oct

Author: rolyon

articles/active-directory/develop/identity-platform-integration-checklist.md

@@ -71,7 +71,7 @@ Use the following checklist to ensure that your application is effectively integ
 |---|---|
 | ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) | Use modern authentication solutions (OAuth 2.0, [OpenID Connect](v2-protocols-oidc.md)) to securely sign in users. |
 | ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) |  Don't program directly against protocols such as OAuth 2.0 and Open ID. Instead, leverage the [Microsoft Authentication Library (MSAL)](msal-overview.md). The MSAL libraries securely wrap security protocols in an easy-to-use library, and you get built-in support for [Conditional Access](/azure/active-directory/conditional-access/overview) scenarios, device-wide [single sign-on (SSO)](/azure/active-directory/manage-apps/what-is-single-sign-on), and built-in token caching support. For more info, see the list of Microsoft supported [client libraries](reference-v2-libraries.md#microsoft-supported-client-libraries) and [middleware libraries](reference-v2-libraries.md#microsoft-supported-server-middleware-libraries) and the list of [compatible third-party client libraries](reference-v2-libraries.md#compatible-client-libraries).<br/><br/>If you must hand code for the authentication protocols, you should follow a methodology such as [Microsoft SDL](https://www.microsoft.com/sdl/default.aspx). Pay close attention to the security considerations in the standards specifications for each protocol.|
-| ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) |  Migrate existing apps from [Azure Active Directory Authentication Library (ADAL)](active-directory-authentication-libraries.md) to [Microsoft Authentication Library](msal-overview.md). MSAL is Microsoft’s latest identity platform solution and is preferred to ADAL. It is available on .NET and JavaScript and is also in public preview for Android, iOS, Python, and Java. Read more about migrating [ADAL.NET](msal-net-migration.md), [ADAL.js](msal-compare-msal-js-and-adal-js.md), and [ADAL.NET and iOS broker](msal-net-migration-ios-broker.md) apps.|
+| ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) |  Migrate existing apps from [Azure Active Directory Authentication Library (ADAL)](active-directory-authentication-libraries.md) to [Microsoft Authentication Library](msal-overview.md). MSAL is Microsoft’s latest identity platform solution and is preferred to ADAL. It is available on .NET, JavaScript, Android, iOS, macOS and is also in public preview for Python and Java. Read more about migrating [ADAL.NET](msal-net-migration.md), [ADAL.js](msal-compare-msal-js-and-adal-js.md), and [ADAL.NET and iOS broker](msal-net-migration-ios-broker.md) apps.|
 | ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) |  For mobile apps, configure each platform using the application registration experience. In order for your application to take advantage of the Microsoft Authenticator or Microsoft Company Portal for single sign-in, your app needs a “broker redirect URI” configured. This allows Microsoft to return control to your application after authentication. When configuring each platform, the app registration experience will guide you through the process. Use the quickstart to download a working example. On iOS, use brokers and system webview whenever possible.|
 | ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) |  In web apps or web APIs, keep one token cache per account.  For web apps, the token cache should be keyed by the account ID.  For web APIs, the account should be keyed by the hash of the token used to call the API. MSAL.NET provides custom token cache serialization in the .NET Framework and .NET Core subplatforms. For security and performance reasons, our recommendation is to serialize one cache per user. For more information, read about [token cache serialization](msal-net-token-cache-serialization.md#token-cache-for-a-web-app-confidential-client-application).|
 | ![checkbox](./media/active-directory-integration-checklist/checkbox-two.svg) | If the data your app requires is available through [Microsoft Graph](https://developer.microsoft.com/graph), request permissions for this data using the Microsoft Graph endpoint rather than the individual API. |

articles/app-service/app-service-hybrid-connections.md

@@ -35,7 +35,7 @@ Through the two joined connections, your app has a TCP tunnel to a fixed host:po
 When your app makes a DNS request that matches a configured Hybrid Connection endpoint, the outbound TCP traffic will be redirected through the Hybrid Connection.  
 
 > [!NOTE]
-> This means that you should try to always use a DNS name for your Hybrid Connection. Some client software does not do a DNS lookup if the endpoint uses an IP address instead.
+> This means that you should try to always use a DNS name for your Hybrid Connection. Some client software does not do a DNS lookup if the endpoint uses an IP address instead. 
 >
 
 ### App Service Hybrid Connection benefits ###
@@ -60,6 +60,9 @@ Things you cannot do with Hybrid Connections include:
 - Support LDAP, because it can require UDP.
 - Support Active Directory, because you cannot domain join an App Service worker.
 
+### Prerequisites ###
+ - Windows App service is required. It is only available in Windows.  
+
 ## Add and Create Hybrid Connections in your app ##
 
 To create a Hybrid Connection, go to the [Azure portal][portal] and select your app. Select **Networking** > **Configure your Hybrid Connection endpoints**. Here you can see the Hybrid Connections that are configured for your app.  

articles/event-grid/compare-messaging-services.md

@@ -1,13 +1,13 @@
 ---
-title: Azure messaging comparison - Event Grid, Event Hubs, Service Bus
+title: Compare Azure messaging services
 description: Describes the three Azure messaging services - Azure Event Grid, Event Hubs, and Service Bus. Recommends which service to use for different scenarios.
 services: event-grid
 author: spelluru
 manager: timlt
 
 ms.service: event-grid
 ms.topic: overview
-ms.date: 01/30/2019
+ms.date: 10/22/2019
 ms.author: spelluru
 ms.custom: seodec18
 ---

articles/event-grid/custom-disaster-recovery.md

@@ -1,12 +1,12 @@
 ---
-title: 'Build your own disaster recovery for Custom Topics in Azure Event Grid | Microsoft Docs'
-description: Survive regional outages to keep Azure Event Grid connected.
+title: Disaster recovery for custom topics in Azure Event Grid
+description: Learn how to survive regional outages to keep Azure Event Grid connected.
 services: event-grid
 author: banisadr
 
 ms.service: event-grid
 ms.topic: tutorial
-ms.date: 05/16/2019
+ms.date: 10/22/2019
 ms.author: babanisa
 
 ---

articles/event-grid/custom-event-to-hybrid-connection.md

@@ -1,11 +1,11 @@
 ---
-title: Send custom events to hybrid connection - Event Grid, Azure CLI
+title: Send custom events to hybrid connection - Event Grid
 description: Use Azure Event Grid and Azure CLI to publish a topic, and subscribe to that event. A hybrid connection is used for the endpoint. 
 services: event-grid 
 keywords: 
 author: spelluru
 ms.author: spelluru
-ms.date: 02/02/2019
+ms.date: 10/22/2019
 ms.topic: tutorial
 ms.service: event-grid
 ms.custom: seodec18

articles/event-grid/how-to-event-domains.md

@@ -1,13 +1,13 @@
 ---
-title: Manage large sets of topics in Azure Event Grid with event domains
+title: Publish events with event domains with Azure Event Grid
 description: Shows how to manage large sets of topics in Azure Event Grid and publish events to them using event domains.
 services: event-grid
 author: banisadr
 
 ms.service: event-grid
 ms.author: babanisa
 ms.topic: conceptual
-ms.date: 07/11/2019
+ms.date: 10/22/2019
 ---
 
 # Manage topics and publish events using event domains

articles/event-grid/manage-event-delivery.md

@@ -1,12 +1,12 @@
 ---
-title: Dead letter and retry policies for Azure Event Grid subscriptions
+title: Dead letter and retry policies - Azure Event Grid
 description: Describes how to customize event delivery options for Event Grid. Set a dead-letter destination, and specify how long to retry delivery.
 services: event-grid
 author: spelluru
 
 ms.service: event-grid
 ms.topic: conceptual
-ms.date: 01/06/2019
+ms.date: 10/22/2019
 ms.author: spelluru
 ---
 

articles/event-grid/overview.md

@@ -1,13 +1,13 @@
 ---
-title: Publish and subscribe to application events - Azure Event Grid
+title: What is Azure Event Grid? 
 description: Send event data from a source to handlers with Azure Event Grid. Build event-based applications, and integrate with Azure services.
 services: event-grid
 author: banisadr
 manager: timlt
 
 ms.service: event-grid
 ms.topic: overview
-ms.date: 05/25/2019
+ms.date: 10/22/2019
 ms.author: babanisa
 ms.custom: seodec18
 ---

articles/event-grid/scripts/event-grid-cli-resource-group-filter.md

@@ -1,17 +1,17 @@
 ---
-title: Azure CLI script sample - Subscribe to resource group and filter by resource | Microsoft Docs
+title: Azure CLI - subscribe to resource group & filter by resource
 description: Azure CLI Script Sample - Subscribe to resource group and filter by resource
 services: event-grid
 documentationcenter: na
-author: tfitzmac
+author: spelluru
 
 ms.service: event-grid
 ms.devlang: azurecli
 ms.topic: sample
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 11/02/2018
-ms.author: tomfitz
+ms.date: 10/22/2019
+ms.author: spelluru
 ---
 
 # Subscribe to events for a resource group and filter for a resource with Azure CLI

articles/hdinsight/hdinsight-restrict-outbound-traffic.md

@@ -145,7 +145,7 @@ AzureDiagnostics | where msg_s contains "Deny" | where TimeGenerated >= ago(1h)
 
 Integrating your Azure Firewall with Azure Monitor logs is useful when first getting an application working when you are not aware of all of the application dependencies. You can learn more about Azure Monitor logs from [Analyze log data in Azure Monitor](../azure-monitor/log-query/log-query-overview.md)
 
-To learn about the scale limits of Azure Firewall and request increases, see [this](https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#azure-firewall-limits) document.
+To learn about the scale limits of Azure Firewall and request increases, see [this](https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#azure-firewall-limits) document or refer to the [FAQs](https://docs.microsoft.com/en-us/azure/firewall/firewall-faq). 
 
 ## Access to the cluster
 After having the firewall setup successfully, you can use the internal endpoint (`https://<clustername>-int.azurehdinsight.net`) to access the Ambari from inside the VNET.