Merge pull request #308988 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-03 12:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-functions/functions-bindings-azure-sql-trigger.md

@@ -43,6 +43,9 @@ Changes are processed in the order that their changes were made, with the oldest
 2. Changes are "batched" together for a row. If multiple changes are made to a row between each iteration of the loop then only a single change entry exists for that row which will show the difference between the last processed state and the current state
 3. If changes are made to a set of rows, and then another set of changes are made to half of those same rows, then the half of the rows that weren't changed a second time are processed first. This processing logic is due to the above note with the changes being batched - the trigger will only see the "last" change made and use that for the order it processes them in
 
+> [!NOTE]
+> Azure SQL change tracking can detect row-level changes in tables that use encryption technologies such as Always Encrypted or Transparent Data Encryption (TDE). However, the Azure SQL trigger doesn’t decrypt or expose encrypted column values in the change payload. The trigger can detect that a change occurred but can’t access the decrypted data for those columns.
+
 For more information on change tracking and how it's used by applications such as Azure SQL triggers, see [work with change tracking](/sql/relational-databases/track-changes/work-with-change-tracking-sql-server) .
 
 [!INCLUDE [functions-sql-database-authentication-note](../../includes/functions-sql-database-authentication-note.md)]

articles/backup/backup-azure-private-endpoints-configure-manage.md

@@ -3,7 +3,7 @@ title: How to create and manage private endpoints (with v2 experience) for Azure
 description: This article explains how to configure and manage private endpoints for Azure Backup.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 09/09/2025
+ms.date: 12/03/2025
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 # Customer intent: As a cloud administrator, I want to configure private endpoints for Azure Backup, so that I can enhance the security of backup and restore operations within my Virtual Network.
@@ -143,7 +143,7 @@ Once the private endpoints created for the vault in your VNet have been approved
 >Ensure that you've completed all the steps mentioned above in the document successfully before proceeding. To recap, you must have completed the steps in the following checklist:
 >
 >1. Created a (new) Recovery Services vault.
->2. Enabled the vault to use system assigned Managed Identity.
+>2. [Enabled the vault to use system assigned Managed Identity](encryption-at-rest-with-cmk.md?tabs=portal#enable-a-system-assigned-managed-identity-for-the-vault).
 >3. Created a Private Endpoint for your vault.
 >4. Approved the Private Endpoint (if not auto approved).
 >5. Ensured all DNS records are appropriately added (except blob and queue records for custom servers, which will be discussed in the following sections).

articles/backup/manage-monitor-sql-database-backup.md

@@ -2,7 +2,7 @@
 title: Manage and monitor SQL Server DBs on an Azure VM
 description: This article describes how to manage and monitor SQL Server databases that are running on an Azure VM.
 ms.topic: how-to
-ms.date: 08/05/2025
+ms.date: 12/03/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -54,16 +54,11 @@ To monitor database backup alerts, follow these steps:
 
 ## Stop protection for a SQL Server database
 
-You can stop backing up a SQL Server database in a couple of ways:
+Azure Backup provides the following options to stop protection of a SQL Server database:
 
-- Stop all future backup jobs, and delete all recovery points.
-- Stop all future backup jobs, and leave the recovery points intact.
-
-If you choose to leave recovery points, keep these details in mind:
-
-- All recovery points will remain intact forever, and all pruning will stop at stop protection with retain data.
-- You'll be charged for the protected instance and the consumed storage. For more information, see [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup/).
-- If you delete a data source without stopping backups, new backups will fail. Old recovery points will expire according to the policy, but the most recent recovery point will always be kept until you stop the backups and delete the data.
+- **Stop protection and retain backup data (Retain forever)**: Stops all future backup jobs from protecting a SQL Server database and retains the existing backup data in the Recovery Services vault forever. This retention incurs a storage fee as per [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup/). If needed, you can use the backup data to restore the SQL Server database and use the **Resume backup** option to resume protection.
+- **Stop protection and retain backup data (Retain as per policy)**: Stops all future backup jobs from protecting a SQL Server database and retains the existing backup data in the Recovery Services vault as per policy. However, the latest recovery point is retained forever. This retention incurs a storage fee as per [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup/). If needed, you can use the backup data to restore the SQL Server database and use the **Resume backup** option to resume protection.
+- **Stop protection and delete backup data**: Stops future backup jobs for a SQL Server database and deletes all backup data. You can't restore the SQL Server database or use the **Resume backup** option.
 
 To stop protection for a database:
 

articles/container-apps/TOC.yml

@@ -55,6 +55,8 @@ items:
       href: environment.md
     - name: Containers
       href: containers.md
+    - name: Functions
+      href: functions-overview.md
     - name: Revisions
       href: revisions.md
     - name: Application lifecycle management
@@ -81,6 +83,8 @@ items:
       href: tutorial-deploy-from-code.md
     - name: Update a container app deployed from code
       href: tutorial-update-from-code.md
+    - name: Create a functions app deployed from code
+      href: functions-container-apps.md
     - name: Connect to apps & services
       items:
         - name: Communicate between multiple apps
@@ -139,6 +143,8 @@ items:
       items:
         - name: With a job
           href: tutorial-event-driven-jobs.md
+        - name: With Azure Functions
+          href: functions-unified-platform.md
     - name: Workflow
       href: workflows-overview.md
     - name: Troubleshooting