From 95ecacfe2a241a46684a6ad414bf1c759df3ecc0 Mon Sep 17 00:00:00 2001 From: ajay-msft <22244825+ajay-msft@users.noreply.github.com> Date: Wed, 17 Sep 2025 08:46:27 -0700 Subject: [PATCH 1/5] Learn Editor: Update troubleshooting.md --- docs/mirroring/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mirroring/troubleshooting.md b/docs/mirroring/troubleshooting.md index 895f2ccac4..4de516d0ef 100644 --- a/docs/mirroring/troubleshooting.md +++ b/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.
To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused.
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.
To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused.
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 database transaction log usage to grow and hold up log truncation. To minimize impact to the source database, reseed of the database will be initiated to free up log space held up if the log space is close to being full.| | 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). | From 9cfe9cd3e79be865f0f19bcef9c16fa9939513f3 Mon Sep 17 00:00:00 2001 From: ajay-msft <22244825+ajay-msft@users.noreply.github.com> Date: Wed, 17 Sep 2025 08:47:38 -0700 Subject: [PATCH 2/5] Learn Editor: Update troubleshooting.md --- docs/mirroring/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mirroring/troubleshooting.md b/docs/mirroring/troubleshooting.md index 4de516d0ef..1df4f97516 100644 --- a/docs/mirroring/troubleshooting.md +++ b/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.
To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused.
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 database transaction log usage to grow and hold up log truncation. To minimize impact to the source database, reseed of the database will be initiated to free up log space held up if the log space is close to being 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.
To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused.
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 database transaction log usage to grow and hold up log truncation. To minimize impact to the source 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). | From 02b40801dcf5ac4601866586b629be9de395746f Mon Sep 17 00:00:00 2001 From: ajay-msft <22244825+ajay-msft@users.noreply.github.com> Date: Wed, 17 Sep 2025 09:05:45 -0700 Subject: [PATCH 3/5] Learn Editor: Update troubleshooting.md --- docs/mirroring/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mirroring/troubleshooting.md b/docs/mirroring/troubleshooting.md index 1df4f97516..f210608344 100644 --- a/docs/mirroring/troubleshooting.md +++ b/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.
To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused.
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 database transaction log usage to grow and hold up log truncation. To minimize impact to the source 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 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.
To resume mirroring, go to the mirrored database in the Fabric portal, select **Resume replication**. Mirroring continues from where it was paused.
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). | From 0d53a0e77b2bf53e609346e1b983ef27f543843f Mon Sep 17 00:00:00 2001 From: Sreedhar Pelluru <6722422+spelluru@users.noreply.github.com> Date: Wed, 17 Sep 2025 14:03:28 -0400 Subject: [PATCH 4/5] Azure Event Grid Namespace Preview -> GA --- .../includes/mqtt-source-description-prerequisites.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/real-time-intelligence/event-streams/includes/mqtt-source-description-prerequisites.md b/docs/real-time-intelligence/event-streams/includes/mqtt-source-description-prerequisites.md index 3154bd0099..a1eaa0901c 100644 --- a/docs/real-time-intelligence/event-streams/includes/mqtt-source-description-prerequisites.md +++ b/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). \ No newline at end of file +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). From 27584dcb9069edcc10141223fd2e2b0e0c8294a3 Mon Sep 17 00:00:00 2001 From: Jon Burchel Date: Wed, 17 Sep 2025 15:17:10 -0400 Subject: [PATCH 5/5] Updates freshness on several docs that were recently updated but date hadn't been changed. Adds ai-assisted. --- docs/data-science/ai-functions/overview.md | 3 ++- docs/data-science/data-agent-end-to-end-tutorial.md | 3 ++- docs/data-science/data-agent-sharing.md | 3 ++- docs/data-science/how-to-create-data-agent.md | 2 +- 4 files changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/data-science/ai-functions/overview.md b/docs/data-science/ai-functions/overview.md index 88a5f5b222..b3ae741904 100644 --- a/docs/data-science/ai-functions/overview.md +++ b/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) diff --git a/docs/data-science/data-agent-end-to-end-tutorial.md b/docs/data-science/data-agent-end-to-end-tutorial.md index cf9a0122f6..87fcbd4532 100644 --- a/docs/data-science/data-agent-end-to-end-tutorial.md +++ b/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) diff --git a/docs/data-science/data-agent-sharing.md b/docs/data-science/data-agent-sharing.md index e1779c85dc..9efe63284a 100644 --- a/docs/data-science/data-agent-sharing.md +++ b/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) diff --git a/docs/data-science/how-to-create-data-agent.md b/docs/data-science/how-to-create-data-agent.md index 1b098bd4e1..b4eff0dad6 100644 --- a/docs/data-science/how-to-create-data-agent.md +++ b/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