Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr

OwenRichards1 · OwenRichards1 · commit f58f24687719 · 2022-08-31T14:07:17.000+01:00
diff --git a/articles/azure-arc/servers/prerequisites.md b/articles/azure-arc/servers/prerequisites.md
@@ -13,7 +13,7 @@ This topic describes the basic requirements for installing the Connected Machine
 
 Azure Arc-enabled servers support the installation of the Connected Machine agent on physical servers and virtual machines hosted outside of Azure. This includes support for virtual machines running on platforms like:
 
-* VMware
+* VMware (including Azure VMware Solution)
 * Azure Stack HCI
 * Other cloud environments
 
diff --git a/articles/sentinel/whats-new-archive.md b/articles/sentinel/whats-new-archive.md
@@ -25,6 +25,58 @@ Noted features are currently in PREVIEW. The [Azure Preview Supplemental Terms](
 > You can also contribute! Join us in the [Azure Sentinel Threat Hunters GitHub community](https://github.com/Azure/Azure-Sentinel/wiki).
 
 
+## September 2021
+
+- [Data connector health enhancements (Public preview)](#data-connector-health-enhancements-public-preview)
+- [New in docs: scaling data connector documentation](#new-in-docs-scaling-data-connector-documentation)
+- [Azure Storage account connector changes](#azure-storage-account-connector-changes)
+
+### Data connector health enhancements (Public preview)
+
+Azure Sentinel now provides the ability to enhance your data connector health monitoring with a new *SentinelHealth* table. The *SentinelHealth* table is created after you [turn on the Azure Sentinel health feature](monitor-sentinel-health.md) in your Azure Sentinel workspace, at the first success or failure health event generated.
+
+For more information, see [Monitor the health of your data connectors with this Azure Sentinel workbook](monitor-data-connector-health.md).
+
+> [!NOTE]
+> The *SentinelHealth* data table is currently supported only for selected data connectors. For more information, see [Supported data connectors](monitor-data-connector-health.md#supported-data-connectors).
+>
+
+
+### New in docs: scaling data connector documentation
+
+As we continue to add more and more built-in data connectors for Azure Sentinel, we reorganized our data connector documentation to reflect this scaling.
+
+For most data connectors, we replaced full articles that describe an individual connector with a series of generic procedures and a full reference of all currently supported connectors.
+
+Check the [Azure Sentinel data connectors reference](data-connectors-reference.md) for details about your connector, including references to the relevant generic procedure, as well as extra information and configurations required.
+
+For more information, see:
+
+- **Conceptual information**: [Connect data sources](connect-data-sources.md)
+
+- **Generic how-to articles**:
+
+   - [Connect to Azure, Windows, Microsoft, and Amazon services](connect-azure-windows-microsoft-services.md)
+   - [Connect your data source to the Azure Sentinel Data Collector API to ingest data](connect-rest-api-template.md)
+   - [Get CEF-formatted logs from your device or appliance into Azure Sentinel](connect-common-event-format.md)
+   - [Collect data from Linux-based sources using Syslog](connect-syslog.md)
+   - [Collect data in custom log formats to Azure Sentinel with the Log Analytics agent](connect-custom-logs.md)
+   - [Use Azure Functions to connect your data source to Azure Sentinel](connect-azure-functions-template.md)
+   - [Resources for creating Azure Sentinel custom connectors](create-custom-connector.md)
+
+### Azure Storage account connector changes
+
+Due to some changes made within the Azure Storage account resource configuration itself, the connector also needs to be reconfigured.
+The storage account (parent) resource has within it other (child) resources for each type of storage: files, tables, queues, and blobs.
+
+When configuring diagnostics for a storage account, you must select and configure, in turn:
+- The parent account resource, exporting the **Transaction** metric.
+- Each of the child storage-type resources, exporting all the logs and metrics (see the table above).
+
+You'll only see the storage types that you actually have defined resources for.
+
+:::image type="content" source="media/whats-new/storage-diagnostics.png" alt-text="Screenshot of Azure Storage diagnostics configuration.":::
+
 ## August 2021
 
 - [Advanced incident search (Public preview)](#advanced-incident-search-public-preview)
diff --git a/articles/sentinel/whats-new.md b/articles/sentinel/whats-new.md
@@ -702,58 +702,6 @@ For more information, see:
 - [Azure Sentinel DHCP normalization schema reference (Public preview)](dhcp-normalization-schema.md)
 - [Normalization and the Azure Sentinel Information Model (ASIM)](normalization.md)
 
-## September 2021
-
-- [Data connector health enhancements (Public preview)](#data-connector-health-enhancements-public-preview)
-- [New in docs: scaling data connector documentation](#new-in-docs-scaling-data-connector-documentation)
-- [Azure Storage account connector changes](#azure-storage-account-connector-changes)
-
-### Data connector health enhancements (Public preview)
-
-Azure Sentinel now provides the ability to enhance your data connector health monitoring with a new *SentinelHealth* table. The *SentinelHealth* table is created after you [turn on the Azure Sentinel health feature](monitor-sentinel-health.md) in your Azure Sentinel workspace, at the first success or failure health event generated.
-
-For more information, see [Monitor the health of your data connectors with this Azure Sentinel workbook](monitor-data-connector-health.md).
-
-> [!NOTE]
-> The *SentinelHealth* data table is currently supported only for selected data connectors. For more information, see [Supported data connectors](monitor-data-connector-health.md#supported-data-connectors).
->
-
-
-### New in docs: scaling data connector documentation
-
-As we continue to add more and more built-in data connectors for Azure Sentinel, we reorganized our data connector documentation to reflect this scaling.
-
-For most data connectors, we replaced full articles that describe an individual connector with a series of generic procedures and a full reference of all currently supported connectors.
-
-Check the [Azure Sentinel data connectors reference](data-connectors-reference.md) for details about your connector, including references to the relevant generic procedure, as well as extra information and configurations required.
-
-For more information, see:
-
-- **Conceptual information**: [Connect data sources](connect-data-sources.md)
-
-- **Generic how-to articles**:
-
-   - [Connect to Azure, Windows, Microsoft, and Amazon services](connect-azure-windows-microsoft-services.md)
-   - [Connect your data source to the Azure Sentinel Data Collector API to ingest data](connect-rest-api-template.md)
-   - [Get CEF-formatted logs from your device or appliance into Azure Sentinel](connect-common-event-format.md)
-   - [Collect data from Linux-based sources using Syslog](connect-syslog.md)
-   - [Collect data in custom log formats to Azure Sentinel with the Log Analytics agent](connect-custom-logs.md)
-   - [Use Azure Functions to connect your data source to Azure Sentinel](connect-azure-functions-template.md)
-   - [Resources for creating Azure Sentinel custom connectors](create-custom-connector.md)
-
-### Azure Storage account connector changes
-
-Due to some changes made within the Azure Storage account resource configuration itself, the connector also needs to be reconfigured.
-The storage account (parent) resource has within it other (child) resources for each type of storage: files, tables, queues, and blobs.
-
-When configuring diagnostics for a storage account, you must select and configure, in turn:
-- The parent account resource, exporting the **Transaction** metric.
-- Each of the child storage-type resources, exporting all the logs and metrics (see the table above).
-
-You'll only see the storage types that you actually have defined resources for.
-
-:::image type="content" source="media/whats-new/storage-diagnostics.png" alt-text="Screenshot of Azure Storage diagnostics configuration.":::
-
 ## Next steps
 
 > [!div class="nextstepaction"]
diff --git a/articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md b/articles/synapse-analytics/sql/resources-self-help-sql-on-demand.md
@@ -178,7 +178,7 @@ The error "Invalid object name 'table name'" indicates that you're using an obje
 - If you don't see the object, maybe you're trying to query a table from a lake or Spark database. The table might not be available in the serverless SQL pool because:
 
     - The table has some column types that can't be represented in serverless SQL pool.
-    - The table has a format that isn't supported in serverless SQL pool. Examples are Delta or ORC.
+    - The table has a format that isn't supported in serverless SQL pool. Examples are Avro or ORC.
 
 ### Unclosed quotation mark after the character string
 
@@ -854,7 +854,7 @@ There are some limitations and known issues that you might see in Delta Lake sup
 - Make sure that you're referencing the root Delta Lake folder in the [OPENROWSET](./develop-openrowset.md) function or external table location.
   - The root folder must have a subfolder named `_delta_log`. The query fails if there's no `_delta_log` folder. If you don't see that folder, you're referencing plain Parquet files that must be [converted to Delta Lake](../spark/apache-spark-delta-lake-overview.md?pivots=programming-language-python#convert-parquet-to-delta) by using Apache Spark pools.
   - Don't specify wildcards to describe the partition schema. The Delta Lake query automatically identifies the Delta Lake partitions.
-- Delta Lake tables created in the Apache Spark pools aren't automatically available in serverless SQL pool. To query such Delta Lake tables by using the T-SQL language, run the [CREATE EXTERNAL TABLE](./create-use-external-tables.md#delta-lake-external-table) statement and specify Delta as the format.
+- Delta Lake tables created in the Apache Spark pools are automatically available in serverless SQL pool, but the schema is not updated. If you add the columns in hte Delta table using Spark pool, the changes will not be shown in serverless database.
 - External tables don't support partitioning. Use [partitioned views](create-use-views.md#delta-lake-partitioned-views) on the Delta Lake folder to use the partition elimination. See known issues and workarounds later in the article.
 - Serverless SQL pools don't support time travel queries. Use Apache Spark pools in Synapse Analytics to [read historical data](../spark/apache-spark-delta-lake-overview.md?pivots=programming-language-python#read-older-versions-of-data-using-time-travel).
 - Serverless SQL pools don't support updating Delta Lake files. You can use serverless SQL pool to query the latest version of Delta Lake. Use Apache Spark pools in Synapse Analytics to [update Delta Lake](../spark/apache-spark-delta-lake-overview.md?pivots=programming-language-python#update-table-data).
@@ -901,6 +901,12 @@ There are two options available to circumvent this error:
 
 Our engineering team is currently working on a full support for Spark 3.3.
 
+### Delta tables in Lake databases do not have identical schema in Spark and serverless pools
+
+Serverless SQL pools enable you to access Parquet, CSV, and Delta tables that are created in Lake database using Spark or Synapse designer. Accessing the Delta tables is still in public preview, and currently serverless will synchronize a Delta table with Spark at the time of creation but will not update the schema if the columns are added later using the `ALTER TABLE` statement in Spark.
+
+This is a public preview limitation. Drop and re-create the Delta table in Spark (if it is possible) instead of altering tables to resolve this issue.
+
 ## Performance
 
 Serverless SQL pool assigns the resources to the queries based on the size of the dataset and query complexity. You can't change or limit the resources that are provided to the queries. There are some cases where you might experience unexpected query performance degradations and you might have to identify the root causes.
