final tables

Author: craigg-msft

docs/sql-server/data-classification.md

@@ -20,6 +20,11 @@ ms.workload: "Active"
 ---
 # SQL Server Documentation
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+This topic summarizes the behavior of different data objects used within SQL Server and how the objects are used to pass information of a personal or confidential manner. The data classification in this topic only applies to versions of the SQL Server on-premises product. It does not apply to the following: 
+- Azure SQL Database
+- SQL Server Management Studio (SSMS)
+- SQL Server Data Tools (SSDT) 
+- SQL Operations Studio
 
 ## Access Control
 Credential-related information used to secure logins, users, or accounts within a SQL Server installation.
@@ -31,8 +36,8 @@ Credential-related information used to secure logins, users, or accounts within
 
 |Scenario  |Access Restrictions  |Retention Requirements |
 |---------|---------|---------|
-|These credentials never leave the user machine via Usage Feedback.     |NA         |NA         |
-|Crash Dumps may contain Access Control Data.     |NA         |Crash Dumps: Maximum 30 days.         |
+|These credentials never leave the user machine via Usage Feedback.     |-         |-         |
+|Crash Dumps may contain Access Control Data.     |-         |Crash Dumps: Maximum 30 days.         |
 |These credentials never leave the user machine via User Feedback unless Customer injects it manually    |Limit to MSFT internal with no third party access.         |User Feedback: Max 1 year         |
  |
 ## Customer Content
@@ -46,8 +51,8 @@ Data stored within user tables, directly or indirectly, including statistics or
 ### Permitted Usage Scenarios
 |Scenario  |Access Restrictions  |Retention Requirements |
 |---------|---------|---------|
-|This data does not leave the user machine via Usage Feedback. |N/A |N/A |
-|Crash Dumps may contain Customer Content and be emitted to Microsoft. |N/A |Crash Dumps: Max 30 days. |
+|This data does not leave the user machine via Usage Feedback. |- |- |
+|Crash Dumps may contain Customer Content and be emitted to Microsoft. |- |Crash Dumps: Max 30 days. |
 |Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
 
 ## End-User Identifiable Information (EUII)
@@ -67,8 +72,8 @@ Data received from a user, or generated from their use of the product.
 
 |Scenario  |Access Restrictions  |Retention Requirements|
 |---------|---------|---------|
-|This data does not leave the user machine via Usage Feedback. |N/A |N/A |
-|Crash Dumps may contain EUII and be emitted to Microsoft. |N/A |Crash Dumps: Max 30 days |
+|This data does not leave the user machine via Usage Feedback. |- |- |
+|Crash Dumps may contain EUII and be emitted to Microsoft. |- |Crash Dumps: Max 30 days |
 |Customer Identification ID may be emitted to Microsoft to deliver new hybrid and cloud features that the users have subscribed to. |N/A |Currently no such hybrid or cloud features exist.|
 |Customers with their consent can send User Feedback that contain Customer Content to Microsoft.|Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
 
@@ -82,10 +87,11 @@ Data needed to provide Internet-based services per the SQL Server EULA.
 - Language Code
 - Partial IP Address
 - Map Data
- 
+
+### Permitted Usage Scenarios 
 |Scenario  |Access Restrictions  |Retention Requirements|
 |---------|---------|---------| 
-|May be used by Microsoft to improve features and/or fix bugs in current features. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer (dashboards, etc.) |Min 90 days | Max 3 years |
+|May be used by Microsoft to improve features and/or fix bugs in current features. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer (dashboards, etc.) |Min 90 days - Max 3 years |
 |Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |Limit to MSFT internal with no third party access. |Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |
 |Power View and SQL Reporting Services Map Item(s) may send data for use of Bing Maps. |Limit to session data |- |
 
@@ -106,6 +112,7 @@ The following are System Metadata when devoid of Customer Content/Access Control
 - Table, Column, Statistics Names
 - Event Names and Error Codes
 
+### Permitted Usage Scenarios
 |Scenario  |Access Restrictions  |Retention Requirements|
 |---------|---------|---------| 
 |May be used by Microsoft to improve features and/or fix bugs in current features.|Limit to MSFT internal with no third party access. |Min 90 days - Max 3 years |
@@ -114,4 +121,13 @@ May be used by Microsoft for future product planning. |Microsoft may share this
 |May be used by Microsoft to provide cloud-based services based on emitted Usage Feedback (Example: a customer dashboard showing feature usage across all SQL Server installations in an organization) |Microsoft can expose the data to the original customer (dashboards, etc.) |Min 90 days - Max 3 years |
 |Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
 
-[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]
+#Object Metadata
+Data that describes or is used to configure servers, databases, tables, and other resources.  Object metadata includes database table and column names but not the contents of database rows or other Customer Content.
+
+### Examples
+- SQL Server database names
+
+### Permitted Usage Scenarios
+None
+
+[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]