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

Author: Karthigasree

articles/active-directory/develop/index-spa.yml

@@ -9,7 +9,7 @@ metadata:
   author: Dickson-Mwendia
   manager: CelesteDG
   ms.author: dmwendia
-  ms.date: 04/01/2022
+  ms.date: 09/21/2023
   ms.service: active-directory
   ms.subservice: develop
   ms.topic: landing-page

articles/active-directory/develop/index-web-app.yml

@@ -8,7 +8,7 @@ summary: >
 metadata:
   author: Dickson-Mwendia
   ms.author: dmwendia
-  ms.date: 04/28/2022
+  ms.date: 09/21/2023
   ms.service: active-directory
   ms.subservice: develop
   ms.topic: landing-page

articles/app-service/overview-local-cache.md

@@ -33,7 +33,7 @@ The Azure App Service Local Cache feature provides a web role view of your conte
 * They have fewer app restarts due to storage share changes.
 
 > [!NOTE]
-> If you are using Java (Java SE, Tomcat, or JBoss EAP), then by default the Java artifacts--.jar, .war, and .ear files--are copied locally to the worker. If your Java application depends on read-only access to other files as well, set `JAVA_COPY_ALL` to `true` for those files to also be copied. If Local Cache is enabled, it takes precendnce over this Java-specific enhancement.
+> If you are using Java (Java SE, Tomcat, or JBoss EAP), then by default the Java artifacts--.jar, .war, and .ear files--are copied locally to the worker. If your Java application depends on read-only access to other files as well, set `JAVA_COPY_ALL` to `true` for those files to also be copied. If Local Cache is enabled, it takes precedence over this Java-specific enhancement.
 
 ## How the local cache changes the behavior of App Service
 * _D:\home_ points to the local cache, which is created on the VM instance when the app starts up. _D:\local_ continues to point to the temporary VM-specific storage.

articles/defender-for-cloud/TOC.yml

@@ -636,6 +636,9 @@
       - name: Enable Defender for SQL servers on machines
         href: defender-for-sql-usage.md
         displayName: hybrid, arc, Azure Defender
+      - name: Migrate to SQL server-targeted Azure Monitoring Agent's autoprovisioning process
+        href: defender-for-sql-autoprovisioning.md
+        displayName: defender for sql, autoprovisioning, auto provisioning, auto-provisioning
       - name: Scan your SQL resources for vulnerabilities
         href: defender-for-sql-on-machines-vulnerability-assessment.md
         displayName: hybrid, arc, Azure Defender, VA, registry, vulnerabilities

articles/defender-for-cloud/defender-for-sql-autoprovisioning.md

@@ -0,0 +1,71 @@
+---
+title: Migrate to SQL server-targeted Azure Monitoring Agent's autoprovisioning process
+description: Learn how to enable SQL server-targeted Azure Monitoring Agent's autoprovisioning process for Defender for SQL.
+ms.topic: install-set-up-deploy
+ms.author: dacurwin
+author: dcurwin
+ms.date: 09/21/2023
+---
+
+# Migrate to SQL server-targeted Azure Monitoring Agent's (AMA) autoprovisioning process (Preview)
+
+Microsoft Monitoring Agent (MMA) is being deprecated in August 2024. As a result, a new SQL server-targeted Azure Monitoring Agent (AMA) autoprovisioning process is being released in preview. You can learn more about the [Defender for SQL Server on machines Log Analytics Agent's deprecation plan](upcoming-changes.md#defender-for-sql-server-on-machines).
+
+During the preview, customers who are using the current autoprovisioning process with Azure Monitor Agent (Preview) option,  should migrate to the new Azure Monitoring Agent for SQL server on machines (Preview) autoprovisioning process. The migration process is seamless and provides continuous protection for all machines.
+
+## Migrate to the SQL server-targeted AMA autoprovisioning process
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+
+1. Search for and select **Microsoft Defender for Cloud**.
+
+1. In the Defender for Cloud menu, select **Environment settings**.
+
+1. Select the relevant subscription.
+
+1. Under the Databases plan, select **Action required**.
+
+    :::image type="content" source="media/defender-sql-autoprovisioning/action-required.png" alt-text="Screenshot that shows where the option to select action required is on the Defender plans page." lightbox="media/defender-sql-autoprovisioning/action-required.png":::
+
+    > [!NOTE]
+    > If you do not see the action required button, under the Databases plan select **Settings** and then toggle the Azure Monitoring Agent for SQL server on machines (Preview) option to **On**. Then select **Continue** > **Save**.
+
+1. In the pop-up window, select **Enable**.
+
+    :::image type="content" source="media/defender-sql-autoprovisioning/update-sql.png" alt-text="Screenshot that shows you where to select the Azure Monitor Agent on the screen." lightbox="media/defender-sql-autoprovisioning/update-sql.png":::
+
+1. Select **Save**.
+
+Once the SQL server-targeted AMA autoprovisioning process has been enabled, you should disable the Log Analytics agent/Azure Monitor agent autoprovisioning process.
+
+> [!NOTE]
+> If you have the Defender for Server plan enabled, you will need to [review the Defender for Servers Log Analytics deprecation plan](upcoming-changes.md#defender-for-servers) for Log Analytics agent/Azure Monitor agent dependency before disabling the process. 
+
+## Disable the Log Analytics agent/Azure Monitor agent
+
+1. Sign in to the [Azure portal](https://portal.azure.com).
+
+1. Search for and select **Microsoft Defender for Cloud**.
+
+1. In the Defender for Cloud menu, select **Environment settings**.
+
+1. Select the relevant subscription.
+
+1. Under the Database plan, select **Settings**.
+
+1. Toggle the Log Analytics agent/Azure Monitor agent to **Off**.
+
+    :::image type="content" source="media/defender-sql-autoprovisioning/toggle-to-off.png" alt-text="Screenshot that shows where the toggle is for the log analytics agent and the Azure monitor agent toggled to off." lightbox="media/defender-sql-autoprovisioning/toggle-to-off.png":::
+
+1. Select **Continue**.
+
+1. Select **Save**.
+
+## Next steps
+
+For related information, see these resources:
+- [How Microsoft Defender for Azure SQL can protect SQL servers anywhere](https://www.youtube.com/watch?v=V7RdB6RSVpc).
+- [Security alerts for SQL Database and Azure Synapse Analytics](alerts-reference.md#alerts-sql-db-and-warehouse)
+- [Set up email notifications for security alerts](configure-email-notifications.md)
+- [Learn more about Microsoft Sentinel](../sentinel/index.yml)
+- Check out [common questions](faq-defender-for-databases.yml) about Defender for Databases.