Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into managed-identity-title-updates

daveba · daveba · commit d4b771790a9c · 2019-11-18T15:22:03.000-08:00
diff --git a/articles/active-directory/privileged-identity-management/media/pim-resource-roles-configure-role-settings/role-settings-notification-tab.png b/articles/active-directory/privileged-identity-management/media/pim-resource-roles-configure-role-settings/role-settings-notification-tab.png
diff --git a/articles/active-directory/privileged-identity-management/pim-resource-roles-configure-role-settings.md b/articles/active-directory/privileged-identity-management/pim-resource-roles-configure-role-settings.md
@@ -53,6 +53,9 @@ Follow these steps to open the settings for an Azure resource role.
 
 1. Use the **Notification** tab or the **Next: Activation** button at the bottom of the page to get to the notification setting tab for this role. These settings control all the email notifications related to this role.
 
+    > [!NOTE]
+    > This notifications UI is currently being rolled across Azure regions and subscriptions. If you can't configure these granular notifications, please check back in a day or two.
+
     ![Role Notifications tab in role settings page](./media/pim-resource-roles-configure-role-settings/role-settings-notification-tab.png)
 
 1. Select the **Update** button at any time to update the role settings.
diff --git a/articles/api-management/api-management-howto-developer-portal.md b/articles/api-management/api-management-howto-developer-portal.md
@@ -139,6 +139,14 @@ The interactive console makes a client-side API request from the browser. You ca
 </cors>
 ```
 
+> [!NOTE]
+> 
+> If you apply the CORS policy in the Product scope, instead of the API(s) scope, and your API uses subscription key authentication through a header, your console won't work.
+>
+> The browser automatically issues an OPTIONS HTTP request, which doesn’t contain a header with the subscription key. Because of the missing subscription key, API Management can't associate the OPTIONS call with a Product, so it can’t apply the CORS policy.
+>
+> As a workaround you can pass the subscription key in a query parameter.
+
 ## Next steps
 
 Learn more about the new developer portal:
diff --git a/articles/cognitive-services/Translator/reference/v3-0-translate.md b/articles/cognitive-services/Translator/reference/v3-0-translate.md
@@ -9,7 +9,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: translator-text
 ms.topic: reference
-ms.date: 10/16/2019
+ms.date: 11/12/2019
 ms.author: swmachan
 ---
 
@@ -29,21 +29,30 @@ https://api.cognitive.microsofttranslator.com/translate?api-version=3.0
 
 Request parameters passed on the query string are:
 
+### Required parameters
+
 <table width="100%">
   <th width="20%">Query parameter</th>
   <th>Description</th>
   <tr>
     <td>api-version</td>
     <td><em>Required parameter</em>.<br/>Version of the API requested by the client. Value must be <code>3.0</code>.</td>
   </tr>
-  <tr>
-    <td>from</td>
-    <td><em>Optional parameter</em>.<br/>Specifies the language of the input text. Find which languages are available to translate from by looking up <a href="./v3-0-languages.md">supported languages</a> using the <code>translation</code> scope. If the <code>from</code> parameter is not specified, automatic language detection is applied to determine the source language. <br/><br/>You must use the <code>from</code> parameter rather than autodetection when using the <a href="https://docs.microsoft.com/azure/cognitive-services/translator/dynamic-dictionary">dynamic dictionary</a> feature.</td>
-  </tr>
   <tr>
     <td>to</td>
     <td><em>Required parameter</em>.<br/>Specifies the language of the output text. The target language must be one of the <a href="./v3-0-languages.md">supported languages</a> included in the <code>translation</code> scope. For example, use <code>to=de</code> to translate to German.<br/>It's possible to translate to multiple languages simultaneously by repeating the parameter in the query string. For example, use <code>to=de&to=it</code> to translate to German and Italian.</td>
   </tr>
+</table>
+
+### Optional parameters
+
+<table width="100%">
+  <th width="20%">Query parameter</th>
+  <th>Description</th>
+  <tr>
+    <td>from</td>
+    <td><em>Optional parameter</em>.<br/>Specifies the language of the input text. Find which languages are available to translate from by looking up <a href="./v3-0-languages.md">supported languages</a> using the <code>translation</code> scope. If the <code>from</code> parameter is not specified, automatic language detection is applied to determine the source language. <br/><br/>You must use the <code>from</code> parameter rather than autodetection when using the <a href="https://docs.microsoft.com/azure/cognitive-services/translator/dynamic-dictionary">dynamic dictionary</a> feature.</td>
+  </tr>  
   <tr>
     <td>textType</td>
     <td><em>Optional parameter</em>.<br/>Defines whether the text being translated is plain text or HTML text. Any HTML needs to be a well-formed, complete element. Possible values are: <code>plain</code> (default) or <code>html</code>.</td>
diff --git a/articles/data-lake-analytics/understand-spark-code-concepts.md b/articles/data-lake-analytics/understand-spark-code-concepts.md
@@ -138,13 +138,13 @@ In Spark, NULL indicates that the value is unknown. A Spark NULL value is differ
 
 This behavior is different from U-SQL, which follows C# semantics where `null` is different from any value but equal to itself.  
 
-Thus a SparkSQL `SELECT` statement that uses `WHERE column_name = NULL` returns zero rows even if there are NULL values in `column_name`, while in U-SQL, it would return the rows where `column_name` is set to `null`. Similarly, A Spark `SELECT` statement that uses `WHERE column_name != NULL` returns zero rows even if there are non-null values in `column_name`, while in U-SQL, it would return the rows that have non-null. Thus, if you want the U-SQL null-check semantics, you should use [isnull](https://spark.apache.org/docs/2.3.0/api/sql/index.html#isnull)) and [isnotnull](https://spark.apache.org/docs/2.3.0/api/sql/index.html#isnotnull) respectively (or their DSL equivalent).
+Thus a SparkSQL `SELECT` statement that uses `WHERE column_name = NULL` returns zero rows even if there are NULL values in `column_name`, while in U-SQL, it would return the rows where `column_name` is set to `null`. Similarly, A Spark `SELECT` statement that uses `WHERE column_name != NULL` returns zero rows even if there are non-null values in `column_name`, while in U-SQL, it would return the rows that have non-null. Thus, if you want the U-SQL null-check semantics, you should use [isnull](https://spark.apache.org/docs/2.3.0/api/sql/index.html#isnull) and [isnotnull](https://spark.apache.org/docs/2.3.0/api/sql/index.html#isnotnull) respectively (or their DSL equivalent).
 
 ## Transform U-SQL catalog objects
 
 One major difference is that U-SQL Scripts can make use of its catalog objects, many of which have no direct Spark equivalent.
 
-Spark does provide support for the Hive Meta store concepts, mainly databases, and tables, so you can map U-SQL databases and schemas to Hive databases, and U-SQL tables to Spark tables (see [Moving data stored in U-SQL tables](understand-spark-data-formats.md#move-data-stored-in-u-sql-tables)), but it has no support for views, table-valued functions (TVFs), stored procedures, U-SQL assemblies, external data sources etc.
+Spark does provide support for the Hive Meta store concepts, mainly databases, and tables, so you can map U-SQL databases and schemas to Hive databases, and U-SQL tables to Spark tables (see [Moving data stored in U-SQL tables](understand-spark-data-formats.md#move-data-stored-in-u-sql-tables), but it has no support for views, table-valued functions (TVFs), stored procedures, U-SQL assemblies, external data sources etc.
 
 The U-SQL code objects such as views, TVFs, stored procedures, and assemblies can be modeled through code functions and libraries in Spark and referenced using the host language's function and procedural abstraction mechanisms (for example, through importing Python modules or referencing Scala functions).
 
diff --git a/articles/virtual-network/tutorial-restrict-network-access-to-resources-cli.md b/articles/virtual-network/tutorial-restrict-network-access-to-resources-cli.md
@@ -1,10 +1,10 @@
 ---
-title: Restrict network access to PaaS resources - Azure CLI | Microsoft Docs
+title: Restrict network access to PaaS resources - Azure CLI
 description: In this article, you learn how to limit and restrict network access to Azure resources, such as Azure Storage and Azure SQL Database, with virtual network service endpoints using the Azure CLI.
 services: virtual-network
 documentationcenter: virtual-network
 author: KumudD
-manager: twooley
+manager: mtillman
 editor: ''
 tags: azure-resource-manager
 Customer intent: I want only resources in a virtual network subnet to access an Azure PaaS resource, such as an Azure Storage account.
diff --git a/articles/virtual-network/tutorial-restrict-network-access-to-resources-powershell.md b/articles/virtual-network/tutorial-restrict-network-access-to-resources-powershell.md
@@ -1,10 +1,10 @@
 ﻿---
-title: Restrict network access to PaaS resources - Azure PowerShell | Microsoft Docs
+title: Restrict network access to PaaS resources - Azure PowerShell
 description: In this article, you learn how to limit and restrict network access to Azure resources, such as Azure Storage and Azure SQL Database, with virtual network service endpoints using Azure PowerShell.
 services: virtual-network
 documentationcenter: virtual-network
 author: KumudD
-manager: twooley
+manager: mtillman
 editor: ''
 tags: azure-resource-manager
 Customer intent: I want only resources in a virtual network subnet to access an Azure PaaS resource, such as an Azure Storage account.
diff --git a/articles/virtual-network/tutorial-restrict-network-access-to-resources.md b/articles/virtual-network/tutorial-restrict-network-access-to-resources.md
@@ -1,10 +1,10 @@
 ---
-title: Restrict network access to PaaS resources - tutorial - Azure portal | Microsoft Docs
+title: Restrict access to PaaS resources - tutorial - Azure portal
 description: In this tutorial, you learn how to limit and restrict network access to Azure resources, such as Azure Storage and Azure SQL Database, with virtual network service endpoints using the Azure portal.
 services: virtual-network
 documentationcenter: virtual-network
 author: KumudD
-manager: twooley
+manager: mtillman
 editor: ''
 tags: azure-resource-manager
 Customer intent: I want only resources in a virtual network subnet to access an Azure PaaS resource, such as an Azure Storage account.
diff --git a/articles/virtual-network/tutorial-tap-virtual-network-cli.md b/articles/virtual-network/tutorial-tap-virtual-network-cli.md
@@ -1,5 +1,5 @@
 ---
-title: Create, change, or delete a virtual network TAP - Azure CLI | Microsoft Docs
+title: Create, change, or delete a VNet TAP - Azure CLI
 description: Learn how to create, change, or delete a virtual network TAP using the Azure CLI.
 services: virtual-network
 documentationcenter: na
diff --git a/articles/virtual-network/virtual-network-create-udr-classic-ps.md b/articles/virtual-network/virtual-network-create-udr-classic-ps.md
@@ -1,5 +1,5 @@
 ---
-title: Control routing in an Azure Virtual Network - PowerShell - Classic | Microsoft Docs
+title: Control routing in an Azure VNet - PowerShell - Classic
 description: Learn how to control routing in VNets using PowerShell | Classic
 services: virtual-network
 documentationcenter: na
diff --git a/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-cli.md b/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-cli.md
@@ -1,11 +1,11 @@
 ---
-title: Deploy an IPv6 dual stack application using Basic Load Balancer in Azure - CLI
+title: Deploy IPv6 dual stack application - Basic Load Balancer - CLI
 titlesuffix: Azure Virtual Network
 description: This article shows how deploy an IPv6 dual stack application in Azure virtual network using Azure CLI.
 services: virtual-network
 documentationcenter: na
 author: KumudD
-manager: twooley
+manager: mtillman
 ms.service: virtual-network
 ms.devlang: na
 ms.topic: article
diff --git a/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-powershell.md b/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-powershell.md
@@ -1,11 +1,11 @@
 ---
-title: Deploy an IPv6 dual stack application using Basic Load Balancer in Azure - PowerShell
+title: Deploy IPv6 dual stack application - Basic Load Balancer - PowerShell
 titlesuffix: Azure Virtual Network
 description: This article shows how deploy an IPv6 dual stack application in Azure virtual network using Azure Powershell.
 services: virtual-network
 documentationcenter: na
 author: KumudD
-manager: twooley
+manager: mtillman
 ms.service: virtual-network
 ms.devlang: na
 ms.topic: article
@@ -17,7 +17,7 @@ ms.author: kumud
 
 # Deploy an IPv6 dual stack application using Basic Load Balancer - PowerShell (Preview)
 
-This article shows you how to deploy a dual stack (IPv4 + IPv6) application with Basic Load Balancer using Azure CLI that includes a dual stack virtual network and subnet, a Basic Load Balancer with dual (IPv4 + IPv6) front-end configurations, VMs with NICs that have a dual IP configuration, network security group, and public IPs.
+This article shows you how to deploy a dual stack (IPv4 + IPv6) application with Basic Load Balancer using Azure PowerShell that includes a dual stack virtual network and subnet, a Basic Load Balancer with dual (IPv4 + IPv6) front-end configurations, VMs with NICs that have a dual IP configuration, network security group, and public IPs.
 
 To deploy a dual stack (IPV4 + IPv6) application using Standard Load Balancer, see [Deploy an IPv6 dual stack application with Standard Load Balancer using Azure PowerShell](virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md).
 
@@ -376,4 +376,4 @@ Remove-AzResourceGroup -Name dsRG1
 
 ## Next steps
 
-In this article, you created a Basic Load Balancer with a dual frontend IP configuration (IPv4 and IPv6). You also created a two virtual machines that included NICs with dual IP configurations (IPV4 + IPv6) that were added to the back-end pool of the load balancer. To learn more about IPv6 support in Azure virtual networks, see [What is IPv6 for Azure Virtual Network?](ipv6-overview.md)
+In this article, you created a Basic Load Balancer with a dual frontend IP configuration (IPv4 and IPv6). You also created a two virtual machines that included NICs with dual IP configurations (IPV4 + IPv6) that were added to the back-end pool of the load balancer. To learn more about IPv6 support in Azure virtual networks, see [What is IPv6 for Azure Virtual Network?](ipv6-overview.md)
diff --git a/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-cli.md b/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-cli.md
@@ -1,11 +1,11 @@
 ---
-title: Deploy an IPv6 dual stack application in Azure virtual network - CLI
+title: Deploy IPv6 dual stack application - Standard Load Balancer - CLI
 titlesuffix: Azure Virtual Network
 description: This article shows how deploy an IPv6 dual stack application in Azure virtual network using Azure CLI.
 services: virtual-network
 documentationcenter: na
 author: KumudD
-manager: twooley
+manager: mtillman
 ms.service: virtual-network
 ms.devlang: na
 ms.topic: article
diff --git a/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md b/articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md
@@ -1,11 +1,11 @@
 ---
-title: Deploy an IPv6 dual stack application in Azure virtual network - PowerShell
+title: Deploy IPv6 dual stack application - Standard Load Balancer - PowerShell
 titlesuffix: Azure Virtual Network
 description: This article shows how deploy an IPv6 dual stack application with Standard Load Balancer in Azure virtual network using Azure Powershell.
 services: virtual-network
 documentationcenter: na
 author: KumudD
-manager: twooley
+manager: mtillman
 ms.service: virtual-network
 ms.devlang: na
 ms.topic: article
@@ -377,4 +377,4 @@ Remove-AzResourceGroup -Name dsRG1
 
 ## Next steps
 
-In this article, you created a Standard Load Balancer with a dual frontend IP configuration (IPv4 and IPv6). You also created a two virtual machines that included NICs with dual IP configurations (IPV4 + IPv6) that were added to the back-end pool of the load balancer. To learn more about IPv6 support in Azure virtual networks, see [What is IPv6 for Azure Virtual Network?](ipv6-overview.md)
+In this article, you created a Standard Load Balancer with a dual frontend IP configuration (IPv4 and IPv6). You also created a two virtual machines that included NICs with dual IP configurations (IPV4 + IPv6) that were added to the back-end pool of the load balancer. To learn more about IPv6 support in Azure virtual networks, see [What is IPv6 for Azure Virtual Network?](ipv6-overview.md)
diff --git a/articles/web-application-firewall/afds/waf-front-door-configure-custom-response-code.md b/articles/web-application-firewall/afds/waf-front-door-configure-custom-response-code.md
@@ -1,5 +1,5 @@
 ---
-title: Configure a custom response for Web Application Firewall with Azure Front Door
+title: Configure a custom response for WAF with Azure Front Door
 description: Learn how to configure a custom response code and message when Web Application Firewall (WAF) blocks a request.
 services: web-application-firewall
 author: vhorne
diff --git a/articles/web-application-firewall/afds/waf-front-door-configure-ip-restriction.md b/articles/web-application-firewall/afds/waf-front-door-configure-ip-restriction.md
@@ -1,5 +1,5 @@
 ---
-title: Configure an IP restriction rule with a Web Application Firewall rule for Azure Front Door Service
+title: Configure IP restriction WAF rule for Azure Front Door Service
 description: Learn how to configure a Web Application Firewall rule to restrict IP addresses for an existing Azure Front Door Service endpoint.
 services: web-application-firewall
 author: vhorne
diff --git a/articles/web-application-firewall/afds/waf-front-door-create-portal.md b/articles/web-application-firewall/afds/waf-front-door-create-portal.md
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Create a Web Application Firewall policy for Azure Front Door using the Azure portal'
+title: 'Tutorial: Create WAF policy for Azure Front Door - Azure portal'
 description: In this tutorial, you learn how to create a Web Application Firewall (WAF) policy by using the Azure portal.
 author: vhorne
 ms.service: web-application-firewall
diff --git a/articles/web-application-firewall/afds/waf-front-door-custom-rules-powershell.md b/articles/web-application-firewall/afds/waf-front-door-custom-rules-powershell.md
@@ -1,5 +1,5 @@
 ---
-title: Configure a Web Application Firewall (WAF) policy with custom rules and Default Ruse Set for Front Door - Azure PowerShell
+title: Configure WAF custom rules & Default Rule Set for Azure Front Door
 description: Learn how to configure a WAF policy consist of both custom and managed rules for an existing Front Door endpoint.
 services: web-application-firewall
 author: vhorne
diff --git a/articles/web-application-firewall/afds/waf-front-door-policy-configure-bot-protection.md b/articles/web-application-firewall/afds/waf-front-door-policy-configure-bot-protection.md
@@ -1,5 +1,5 @@
 ---
-title: Configure bot protection for Web Application Firewall with Azure Front Door (Preview)
+title: Configure bot protection for WAF with Azure Front Door (Preview)
 description: Learn Web Application Firewall (WAF).
 author: vhorne
 ms.service: web-application-firewall
diff --git a/articles/web-application-firewall/afds/waf-front-door-rate-limit-powershell.md b/articles/web-application-firewall/afds/waf-front-door-rate-limit-powershell.md
@@ -1,5 +1,5 @@
 ---
-title: Configure a Web Application Firewall rate limit rule for Front Door - Azure PowerShell
+title: Configure WAF rate limit rule for Front Door - Azure PowerShell
 description: Learn how to configure a rate limit rule for an existing Front Door endpoint.
 author: vhorne
 ms.service: web-application-firewall
