Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

.openpublishing.redirection.json

@@ -4776,6 +4776,11 @@
       "redirect_url": "/azure/app-service-mobile",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/application-gateway/application-gateway-ssl-cli.md",
+      "redirect_url": "/azure/application-gateway/tutorial-ssl-cli",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/application-gateway/application-gateway-ssl-arm.md",
       "redirect_url": "/azure/application-gateway/tutorial-ssl-powershell",

articles/application-gateway/application-gateway-ssl-cli.md

@@ -128,7 +128,7 @@ Log data collected by the [Microsoft Monitoring Agent (MMA)](https://docs.micros
 
 - Machines that already have the MMA agent installed, will have **Azure Arc** functionality enabled via updated Management Packs.
 - [MMA agent version 10.20.18011 or above](https://docs.microsoft.com/azure/virtual-machines/extensions/oms-windows#agent-and-vm-extension-version) is required for Azure Arc for servers integration.
-- When querying for log data in [Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/log-query/log-query-overview#log-queries), the returned data schema will contain the Hybrid **ResourceId** in the form `/subscriptions/<SubscriptionId/resourceGroups/<ResourceGroup>/providers/Microsoft.HybridCompute/machines/<MachineName>`.
+- When querying for log data in [Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/log-query/log-query-overview), the returned data schema will contain the Hybrid **ResourceId** in the form `/subscriptions/<SubscriptionId/resourceGroups/<ResourceGroup>/providers/Microsoft.HybridCompute/machines/<MachineName>`.
 
 For more information, see [Get started with Log Analytics in Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/log-query/get-started-portal).
 

articles/azure-arc/servers/overview.md

@@ -15,9 +15,6 @@ ms.author: alehall
 
 # Tutorial: Stream data into Azure Databricks using Event Hubs
 
-> [!IMPORTANT]
-> This tutorial works with the version of Azure Databricks runtime 5.2.
-
 In this tutorial, you connect a data ingestion system with Azure Databricks to stream data into an Apache Spark cluster in near real-time. You set up data ingestion system using Azure Event Hubs and then connect it to Azure Databricks to process the messages coming through. To access a stream of data, you use Twitter APIs to ingest tweets into Event Hubs. Once you have the data in Azure Databricks, you can run analytical jobs to further analyze the data.
 
 By the end of this tutorial, you would have streamed tweets from Twitter (that have the term "Azure" in them) and read the tweets in Azure Databricks.
@@ -100,7 +97,7 @@ In this section, you create an Azure Databricks workspace using the Azure portal
     Accept all other default values other than the following:
 
    * Enter a name for the cluster.
-   * For this article, create a cluster with **5.2** runtime.
+   * For this article, create a cluster with **6.0* runtime.
    * Make sure you select the **Terminate after \_\_ minutes of inactivity** checkbox. Provide a duration (in minutes) to terminate the cluster, if the cluster is not being used.
 
    Select cluster worker and driver node size suitable for your technical criteria and [budget](https://azure.microsoft.com/pricing/details/databricks/).

articles/azure-databricks/databricks-stream-from-eventhubs.md

@@ -1444,6 +1444,7 @@ Azure Monitor provides several ways to interact with metrics, including charting
 |cpu_limit|CPU limit|Count|Average|CPU limit. Applies to vCore-based databases.|No Dimensions|
 |cpu_used|CPU used|Count|Average|CPU used. Applies to vCore-based databases.|No Dimensions|
 |deadlock|Deadlocks|Count|Total|Deadlocks. Not applicable to data warehouses.|No Dimensions|
+|diff_backup_size_bytes|Differential backup storage size|Bytes|Maximum|Cumulative differential backup storage size. Applies to vCore-based databases. Not applicable to Hyperscale databases.|No Dimensions|
 |dtu_limit|DTU Limit|Count|Average|DTU Limit. Applies to DTU-based databases.|No Dimensions|
 |dtu_consumption_percent|DTU percentage|Percent|Average|DTU percentage. Applies to DTU-based databases.|No Dimensions|
 |dtu_used|DTU used|Count|Average|DTU used. Applies to DTU-based databases.|No Dimensions|
@@ -1452,7 +1453,9 @@ Azure Monitor provides several ways to interact with metrics, including charting
 |dwu_consumption_percent|DWU percentage|Percent|Maximum|DWU percentage. Applies only to data warehouses.|No Dimensions|
 |dwu_limit|DWU limit|Count|Maximum|DWU limit. Applies only to data warehouses.|No Dimensions|
 |dwu_used|DWU used|Count|Maximum|DWU used. Applies only to data warehouses.|No Dimensions|
+|full_backup_size_bytes|Full backup storage size|Bytes|Maximum|Cumulative full backup storage size. Applies to vCore-based databases. Not applicable to Hyperscale databases.|No Dimensions|
 |local_tempdb_usage_percent|Local tempdb percentage|Percent|Average|Local tempdb percentage. Applies only to data warehouses.|No Dimensions|
+|log_backup_size_bytes|Log backup storage size|Bytes|Maximum|Cumulative log backup storage size. Applies to vCore-based databases. Not applicable to Hyperscale databases.|No Dimensions|
 |log_write_percent|Log IO percentage|Percent|Average|Log IO percentage. Not applicable to data warehouses.|No Dimensions|
 |physical_data_read_percent|Data IO percentage|Percent|Average|Data IO percentage|No Dimensions|
 |sessions_percent|Sessions percentage|Percent|Average|Sessions percentage. Not applicable to data warehouses.|No Dimensions|

articles/azure-monitor/platform/metrics-supported.md

@@ -9,16 +9,15 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: academic-knowledge
 ms.topic: conceptual
-ms.date: 10/22/2019
+ms.date: 11/14/2019
 ms.author: darrine
 ROBOTS: NOINDEX
 ---
 
 # Paper Entity
 
-<sub>
-*Below attributes are specific to paper entity. (Ty = '0')
-</sub>
+> [!NOTE]
+> Below attributes are specific to paper entity. (Ty = '0')
 
 Name | Description | Type | Operations
 --- | --- | --- | ---
@@ -29,43 +28,78 @@ AA.AuN | Normalized author name | String | Equals, StartsWith
 AA.DAuN | Original author name | String | None
 AA.DAfN | Original affiliation name | String | None
 AA.S | Numeric position in author list | Int32 | Equals
-CC | Citation count | Int32 | None  
+BT | BibTex document type ('a':Journal article, 'b':Book, 'c':Book chapter, 'p':Conference paper) | String | None
+BV | BibTex venue name | String | None
 C.CId | Conference series ID | Int64 | Equals
 C.CN | Conference series name | String | Equals, StartsWith
+CC | Citation count | Int32 | None  
+CitCon | Citation contexts</br></br>List of referenced paper ID’s and the corresponding context in the paper (e.g. [{123:["brown foxes are known for jumping as referenced in paper 123", "the lazy dogs are a historical misnomer as shown in paper 123"]}) | Custom | None
 D | Date published in YYYY-MM-DD format | Date | Equals, IsBetween
-E | Extended metadata (see table below) | String | N/A  
+DN | Original paper title | String | None
+DOI | Digital Object Identifier | String | Equals, StartsWith
+E | Extended metadata</br></br>**IMPORTANT**: This attribute has been deprecated and is only supported for legacy applications. Requesting this attribute individually (i.e. attributes=Id,Ti,E) will result in all extended metadata attributes being returned in a *serialized JSON string*</br></br>All attributes contained in the extended metadata are now available as a top-level attribute and can be requested as such (i.e. attributes=Id,Ti,DOI,IA) | [Extended](#extended) | None
 ECC | Estimated citation count | Int32 | None
 F.DFN | Original field of study name | String | None
 F.FId | Field of study ID | Int64 | Equals
 F.FN | Normalized field of study name | String | Equals, StartsWith
+FP | First page of paper in publication | String | Equals
+I | Publication issue | String | Equals
+IA | Inverted abstract | [InvertedAbstract](#invertedabstract) | None
 Id | Paper ID | Int64 | Equals
 J.JId | Journal ID | Int64 | Equals
 J.JN | Journal name | String | Equals, StartsWith
+LP | Last page of paper in publication | String | Equals
+PB | Publisher | String | None
 Pt | Publication type (0:Unknown, 1:Journal article, 2:Patent, 3:Conference paper, 4:Book chapter, 5:Book, 6:Book reference entry, 7:Dataset, 8:Repository | String | Equals
 RId | List of referenced paper IDs | Int64[] | Equals
+S | List of source URLs of the paper, sorted by relevance | [Source](#source)[] | None
 Ti | Normalized title | String | Equals, StartsWith
+V | Publication volume | String | Equals
+VFN | Full name of the Journal or Conference venue | String | None
+VSN | Short name of the Journal or Conference venue | String | None
 W | Unique words in title | String[] | Equals
 Y | Year published | Int32 | Equals, IsBetween
 
-## Extended Metadata Attributes ##
+## Extended
+> [!IMPORTANT]
+> This attribute has been deprecated and is only supported for legacy applications. Requesting this attribute individually (i.e. attributes=Id,Ti,E) will result in all extended metadata attributes being returned in a *serialized JSON string*</br></br>All attributes contained in the extended metadata are now available as a top-level attribute and can be requested as such (i.e. attributes=Id,Ti,DOI,IA)
+
+> [!IMPORTANT]
+> Support for requesting individual extended attributes by using the "E." scope, i.e. "E.DN" is being deprecated. While this is still technically supported, requesting individual extended attributes using the "E." scope will result in the attribute value being returned in two places in the JSON response, as part of the "E" object and as a top level attribute.
+
+Name | Description | Type | Operations
+--- | --- | --- | ---
+BT | BibTex document type ('a':Journal article, 'b':Book, 'c':Book chapter, 'p':Conference paper) | String | None
+BV | BibTex venue name | String | None
+CC | Citation contexts</br></br>List of referenced paper ID’s and the corresponding context in the paper (e.g. [{123:["brown foxes are known for jumping as referenced in paper 123", "the lazy dogs are a historical misnomer as shown in paper 123"]}) | Custom | None
+DN | Original paper title | String | None
+DOI | Digital Object Identifier | String | None
+FP | First page of paper in publication | String | None
+I | Publication issue | String | None
+IA | Inverted Abstract | [InvertedAbstract](#invertedabstract) | None
+LP | Last page of paper in publication | String | None
+PB | Publisher | String | None
+S | List of source URLs of the paper, sorted by relevance | [Source](#source)[] | None
+V | Publication volume | String | None
+VFN | Full name of the Journal or Conference venue | String | None
+VSN | Short name of the Journal or Conference venue | String | None
+
+## InvertedAbstract
+
+> [!IMPORTANT]
+> InvertedAbstract attributes cannot be directly requested as a return attribute. If you need an individual attribute you must request the top level "IA" attribute, i.e. to get IA.IndexLength request attributes=IA
 
-Name | Description               
---- | ---
-BT | BibTex document type ('a':Journal article, 'b':Book, 'c':Book chapter, 'p':Conference paper)
-BV | BibTex venue name
-CC | Citation Contexts – List of referenced paper ID’s and the corresponding context in the paper (e.g. [{123:["brown foxes are known for jumping as referenced in paper 123", "the lazy dogs are a historical misnomer as shown in paper 123"]})
-DN | Original paper title
-DOI | Digital Object Identifier
-FP | First page of paper in publication
-I | Publication issue
-IA | Inverted Abstract
-IA.IndexLength | Number of items in the index (abstract's word count)
-IA.InvertedIndex | List of abstract words and their corresponding position in the original abstract (e.g. [{"the":[0, 15, 30]}, {"brown":[1]}, {"fox":[2]}])
-LP | Last page of paper in publication
-PB | Publisher
-S | Sources - list of web sources of the paper, sorted by static rank
-S.Ty | Source Type (1:HTML, 2:Text, 3:PDF, 4:DOC, 5:PPT, 6:XLS, 7:PS)
-S.U | Source URL
-V | Publication volume
-VFN | Full name of the Journal or Conference venue
-VSN | Short name of the Journal or Conference venue
+Name | Description | Type | Operations
+--- | --- | --- | ---
+IndexLength | Number of items in the index (abstract's word count) | Int32 | None
+InvertedIndex | List of abstract words and their corresponding position in the original abstract (e.g. [{"the":[0, 15, 30]}, {"brown":[1]}, {"fox":[2]}]) | Custom | None
+
+## Source
+
+> [!IMPORTANT]
+> Source attributes cannot be directly requested as a return attribute. If you need an individual attribute you must request the top level "S" attribute, i.e. to get S.U request attributes=S
+
+Name | Description | Type | Operations
+--- | --- | --- | ---
+Ty | Source URL type (1:HTML, 2:Text, 3:PDF, 4:DOC, 5:PPT, 6:XLS, 7:PS) | String | None
+U | Source URL | String | None