Merge pull request #2215 from MicrosoftDocs/main638937442615075895sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

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

docs/data-science/ai-functions/overview.md

@@ -6,8 +6,9 @@ author: jonburchel
 ms.reviewer: erenorbey
 reviewer: orbey
 ms.topic: how-to
-ms.date: 05/18/2025
+ms.date: 09/17/2025
 ms.search.form: AI functions
+ai-usage: ai-assisted
 ---
 
 # Transform and enrich data with AI functions (preview)

docs/data-science/data-agent-end-to-end-tutorial.md

@@ -8,9 +8,10 @@ reviewer: amjafari
 ms.service: fabric
 ms.subservice: data-science
 ms.topic: concept-article #Don't change; maybe should change to "how-to".
-ms.date: 03/25/2025
+ms.date: 09/17/2025
 ms.update-cycle: 180-days
 ms.collection: ce-skilling-ai-copilot
+ai-usage: ai-assisted
 ---
 
 # Fabric data agent example with the AdventureWorks dataset (preview)

docs/data-science/data-agent-sharing.md

@@ -5,10 +5,11 @@ author: jonburchel
 ms.author: jburchel
 ms.reviewer: amjafari
 ms.topic: concept-article
-ms.date: 03/25/2025
+ms.date: 09/17/2025
 ms.update-cycle: 180-days
 ms.collection: ce-skilling-ai-copilot
 reviewer: s-polly
+ai-usage: ai-assisted
 ---
 
 # Fabric data agent sharing and permission management (preview)

docs/data-science/how-to-create-data-agent.md

@@ -8,7 +8,7 @@ reviewer: midesa
 ms.service: fabric
 ms.subservice: data-science
 ms.topic: how-to #Don't change
-ms.date: 08/27/2025
+ms.date: 09/17/2025
 ms.update-cycle: 180-days
 ms.collection: ce-skilling-ai-copilot
 ai.usage: ai-assisted

docs/mirroring/troubleshooting.md

@@ -43,7 +43,7 @@ Review limitations documentation for each data source:
 | Scenario                      | Description                                                  |
 | ----------------------------- | ------------------------------------------------------------ |
 | Fabric capacity paused        | Mirroring is stopped and you can't list or access the mirrored database item. Resume or reassign the capacity to your workspace. |
-| Fabric capacity resumed       | When capacity is resumed from a paused state, the mirrored database status appears as **Paused**. As a result, changes made in the source aren't replicated to OneLake.<br>To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused. <br>Note if the capacity remains paused for a long time, mirroring may not resume from its stopping point and will reseed data from the beginning. This situation may arise, for example, if the database transaction log becomes full. |
+| Fabric capacity resumed       |When capacity is resumed from a paused state, the mirrored database status appears as **Paused**. As a result, changes made in the source aren't replicated to OneLake.<br>To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused. <br>Note if the capacity remains paused for a long time, mirroring may not resume from its stopping point and will reseed data from the beginning. This is because pausing mirroring for a long time can cause the source database transaction log usage to grow and hold up log truncation. To minimize impact to the database, if the log space used is close to being full, when mirroring is resumed a reseed of the database will be initiated to release the held up log space.|
 | Fabric capacity scaling       | Mirroring continues. If you scale down the capacity, be aware that the OneLake storage for the mirrored data is free up to a limit based on the capacity size, thus scaling down the capacity may incur additional storage charge. Learn more from [Cost of mirroring](overview.md#cost-of-mirroring). |
 | Fabric capacity throttled     | Wait until the overload state is over or update your capacity. Mirroring will continue once the capacity is restored. Learn more from [Actions you can take to recover from overload situations](../enterprise/throttling.md#how-to-stop-throttling-when-it-occurs). |
 | Fabric trial capacity expired | Mirroring is stopped. To retain your mirrored database, purchase Fabric capacity. Learn more from [Fabric trial capacity expires](../fundamentals/fabric-trial.md#the-trial-expires). |

docs/real-time-intelligence/event-streams/includes/mqtt-source-description-prerequisites.md

@@ -22,6 +22,6 @@ Before you start, you must complete the following prerequisites:
 - Gather Username and password to connect to the MQTT broker.  
 - Ensure that the MQTT broker is publicly accessible and not restricted by a firewall or a virtual network. 
 
-To learn how to configure this setup and stream your MQTT data through **Azure Event Grid**, see [Add Azure Event Grid Namespace as a source to an eventstream (preview)](../add-source-azure-event-grid.md). 
+To learn how to configure this setup and stream your MQTT data through **Azure Event Grid**, see [Add Azure Event Grid Namespace as a source to an eventstream](../add-source-azure-event-grid.md). 
 
-To learn how to stream MQTT data from **Azure IoT Operations** by configuring a data flow endpoint that targets an eventstream custom endpoint, see [Configure data flow endpoints for Microsoft Fabric Real-Time Intelligence](/azure/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence).
+To learn how to stream MQTT data from **Azure IoT Operations** by configuring a data flow endpoint that targets an eventstream custom endpoint, see [Configure data flow endpoints for Microsoft Fabric Real-Time Intelligence](/azure/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence).