Merge pull request #2960 from MicrosoftDocs/main639130358763543891sync_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-engineering/copilot-notebooks-overview.md

@@ -137,19 +137,6 @@ Use the table below to identify the cause and take appropriate action.
 > [!TIP]
 > If you're unsure which setting is causing the issue, start by contacting your tenant administrator, as most Copilot requirements are controlled at the organization level.
 
-## Known issues
-
-### Copilot might not use the latest cell error output when troubleshooting
-
-In some cases, Copilot might not fully incorporate the most recent error output from a notebook cell when diagnosing issues. This can lead to incomplete or less relevant troubleshooting guidance.
-
-**Workaround:**
-
-To improve response quality, explicitly reference or include the latest error message in your prompt when asking Copilot for help.
-
-> [!NOTE]
-> These are known issues that may occur in production environments. A fix is in progress and will be rolled out in an upcoming update.
-
 ## Related content
 
 - [How to use the Copilot chat pane](./copilot-notebooks-chat-pane.md)

docs/data-science/data-agent-purview-governance.md

@@ -0,0 +1,100 @@
+---
+title: Auditing data agent interactions in Microsoft Purview (preview)
+description: Learn how to use DSPM for AI to govern AI interactions in Data Agent.
+ms.reviewer: mayurjain
+ms.topic: how-to
+ms.date: 04/28/2026
+---
+
+# Audit Logging for Fabric Data Agent with Microsoft Purview (Preview)
+
+Microsoft Purview Data Security Posture Management (DSPM) for AI enables organizations to **monitor, audit, and investigate AI interactions** across Fabric Data Agents and Copilot experiences.
+
+With audit logging enabled, **user prompts, AI responses, and interaction metadata** are captured and stored in Microsoft Purview through the Microsoft 365 audit pipeline.
+
+[!INCLUDE [feature-preview](../includes/feature-preview-note.md)]
+---
+
+## Prerequisites
+
+Ensure the following configurations are enabled before using audit logging:
+
+### 1. Enable Purview Audit
+- From DSPM for AI (classic) > Overview, in the Get Started section, look to see if auditing is on for your tenant. If not, select Activate Microsoft Purview Audit.
+
+### 2. Enable DSPM for AI Policy
+- In Microsoft Purview:
+  - Enable the policy:
+    **DSPM for AI – Capture interactions for Copilot experiences**
+For more information about one-click policies, see [Considerations for DSPM for AI](https://learn.microsoft.com/purview/dspm-for-ai-considerations#one-click-policies-from-data-security-posture-management-for-ai)
+
+### 3. Enable Fabric Tenant Setting
+- In the Fabric Admin Portal:
+  - Turn on:
+    **Allow Microsoft Purview to secure AI interactions** 
+
+For more information about this option, see [Tenant settings index](https://learn.microsoft.com/fabric/admin/tenant-settings-index#information-protection).
+
+---
+
+## Viewing Data Agent Audit Logs
+
+When a user interacts with a Fabric Data Agent, a Copilot Interaction audit record is created for the request as well as the response. 
+
+Each audit record includes:
+
+- Timestamp
+- User identity
+- Application and agent details
+- Associated resources and metadata
+- User prompt or AI response
+
+All records are stored in the **Microsoft 365 unified audit log**.
+
+To review audit logs:
+
+1. Go to **Microsoft Purview Portal**
+2. Navigate to **DSPM for AI**
+3. Open **Activity Explorer**
+4. Look for records labeled **Copilot Interaction**
+
+:::image type="content" source="./media/data-agent-governance/purview-activity-explorer.png" alt-text="Screenshot showing Activity Explorer in Purview DSPM for AI." lightbox="./media/data-agent-governance/purview-activity-explorer.png":::
+
+Each record represents a single interaction between a user and the Data Agent.
+
+Use Activity Explorer filters to locate specific interactions:
+
+- **Timestamp**  
+  Narrow results to a specific time window
+
+- **Activity Type**  
+  Filter by `Copilot Interaction`
+
+- **User**  
+  Identify activity by specific users
+
+- **Application**  
+  Isolate interactions from:
+  - Fabric Data Agent
+  - Other AI apps
+
+### User Prompt 
+For each interaction, Microsoft Purview captures and logs the full text of the user’s prompt.
+
+:::image type="content" source="./media/data-agent-governance/purview-da-prompt.png" alt-text="Screenshot showing user prompt in Fabric data agent." lightbox="./media/data-agent-governance/purview-da-prompt.png":::
+
+### Data Agent Response
+For each interaction, the response returned by the Data Agent including the natural language answer and structured outputs such as generated queries or code are logged.
+
+
+:::image type="content" source="./media/data-agent-governance/purview-da-response.png" alt-text="Screenshot showing Data Agent response from M365." lightbox="./media/data-agent-governance/purview-da-response.png":::
+
+
+---
+
+## Licensing and Costs
+
+Microsoft Purview now offers a combination of entitlement-based (per-user-per-month) and Pay-As-You-Go (PAYG) pricing models. The PAYG model applies to a broader set of Purview capabilities—including Insider Risk Management, Communication Compliance, eDiscovery, and other data security and governance solutions—based on copilot for Power BI usage volume or complexity. Purview Audit logging of Copilot for Power BI activity remains included at no additional cost as part of Microsoft 365 E5 licensing. This flexible pricing structure ensures that organizations only pay for what they use as data flows through AI models, networks, and applications. 
+
+---
+

docs/data-science/media/data-agent-governance/purview-activity-explorer.png

@@ -155,6 +155,8 @@ items:
   items:
   - name: Lineage for models and experiments
     href: data-science-lineage.md
+  - name: Audit data agent interactions with Purview
+    href: data-agent-purview-governance.md
 - name: Preparing data 
   items:
   - name: Read and write data with Pandas

docs/data-science/media/data-agent-governance/purview-da-prompt.png

@@ -98,8 +98,11 @@ You can use Dataflow gen2 to get data, transform data, and publish dataflow via
 
 When you connect to Pipeline via private link, you can use the pipeline to load data from any data source with public endpoints into a private-link-enabled Microsoft Fabric lakehouse. Customers can also author and operationalize pipelines with activities, including Notebook and Dataflow activities, using the private link. However, copying data from and into a Data Warehouse isn't currently possible when Fabric's private link is enabled.
 
-### ML Model, Experiment, and Data agent
-ML Model, Experiment, and Data agent supports private link. 
+### Data agent
+Data agents can connect to lakehouse, warehouse, and SQL data sources within a workspace that has workspace-level private links enabled (public access disabled). Cross-workspace access is supported when network connectivity is explicitly established (for example, using a managed private endpoint) and subject to region and token constraints.
+
+Current limitations: Kusto, semantic models, and mirrored data sources are not supported in private link scenarios. These limitations are inherent to the artifact types themselves, and not a limitation of Data Agents.
+Cross-region private-link access for SQL sources is also not supported.
 
 ### Power BI