Update azure-web-apps.md

Update the section on .NET collection levels to present the capability differences in a tabular form for more clarity.

Author: novenera

articles/azure-monitor/app/azure-web-apps.md

@@ -51,15 +51,16 @@ There are two ways to enable application monitoring for Azure App Services hoste
 2. After specifying which resource to use, you can choose how you want application insights to collect data per platform for your application. ASP.NET app monitoring is on-by-default with two different levels of collection.
 
     ![Choose options per platform](./media/azure-web-apps/choose-options-new.png)
-
-   * .NET **Basic collection** level offers essential single-instance APM capabilities.
-
-   * .NET **Recommended collection** level:
-       * Adds CPU, memory, and I/O usage trends.
-       * Correlates micro-services across request/dependency boundaries.
-       * Collects usage trends, and enables correlation from availability results to transactions.
-       * Collects exceptions unhandled by the host process.
-       * Improves APM metrics accuracy under load, when sampling is used.
+ 
+ Below is a summary of data collected for each route:
+        
+|  | .NET Basic Collection | .NET Recommended collection |
+| --- | --- | --- |
+| Adds CPU, memory, and I/O usage trends |Yes |Yes |
+| Collects usage trends, and enables correlation from availability results to transactions | Yes |Yes |
+| Collects exceptions unhandled by the host process | Yes |Yes |
+| Improves APM metrics accuracy under load, when sampling is used | Yes |Yes |
+| Correlates micro-services across request/dependency boundaries | No (single-instance APM capabilities only) |Yes |
 
 3. To configure settings like sampling, which you could previously control via the applicationinsights.config file you can now interact with those same settings via Application settings with a corresponding prefix.