Merge pull request #1871 from MicrosoftDocs/main638846713719462598sync_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-factory/data-source-management.md

@@ -2,10 +2,10 @@
 title: Data source management
 description: Learn how to add and remove data sources, and how to manage users.
 ms.reviewer: whhender
-ms.author: mideboer
-author: miquelladeboer
+ms.author: abnarain
+author: abnarain
 ms.topic: how-to
-ms.date: 12/18/2024
+ms.date: 6/4/2025
 ms.custom: connectors
 ---
 
@@ -49,6 +49,17 @@ ms.custom: connectors
 
 You can now use this data source to include data from Azure SQL in the supported [!INCLUDE [product-name](../includes/product-name.md)] items.
 
+### Allow cloud connection usage on gateway
+
+At the bottom of the connection creation dialog a new setting with the label **This connection can be used with on-premise data gateways and VNet data gateways** is present. Checking the box for this setting enables you 
+
+**When the setting is left unchecked** for the evaluation of a Fabric item that uses a gateway, the evaluation fails as the shareable cloud connection doesn't have the permissions to be used in the context of a gateway evaluation.
+In contrast, **when the setting is checked** the shareable cloud connection can be used by gateway based evaluations.
+
+>[!CAUTION]
+>The *allow connection usage on gateway* setting is present when creating cloud connections through Dataflow Gen2, but not currently enforced. This means that all shareable cloud connections will be used through a gateway if a gateway is present.
+>We're aware of this behavior and are working on a fix to only allow the usage of this connection on a gateway when this setting is checked. 
+
 ## Remove a data source
 
 You can remove a data source if you no longer use it. If you remove a data source, any items that rely on that data source no longer work.
@@ -164,16 +175,16 @@ By default, any user in Fabric can share their connections if they have the foll
 
 Sharing a connection in Fabric is sometimes needed for collaboration within the same workload or when sharing the workload with others. Connection sharing in Fabric makes this easy by providing a secure way to share connections with others for collaboration, but without exposing the secrets at any time. These connections can only be used within the Fabric environment.
 
-If your organization does not allow for connection sharing or wants to limit the sharing of connections, a tenant admin can restrict sharing as a tenant policy. The policy allows you to block sharing within the entire tenant.
+If your organization doesn't allow for connection sharing or wants to limit the sharing of connections, a tenant admin can restrict sharing as a tenant policy. The policy allows you to block sharing within the entire tenant.
 
 > [!NOTE]
 > This restriction can result in limitations of multiple users being unable to collaborate within the same workloads.
-> Disabling connection sharing does not impact connections that have already been shared.
+> Disabling connection sharing doesn't impact connections that have already been shared.
 
 How to enable the setting
 1.	You must have sufficient privileges from the Power BI Service Administrator role.
 3.	In Power BI or Fabric go to settings and the manage connections and gateways page.
-4.	In the top right, turn on the toggle for tenant administation.
+4.	In the top right, turn on the toggle for tenant administration.
 
 :::image type="content" source="media/data-source-management/tenant-administration.png" alt-text="Screenshot showing the tenant administration toggle in the Manage connections and gateways page.":::
 
@@ -185,6 +196,7 @@ How to enable the setting
 
 :::image type="content" source="media/data-source-management/manage-cloud-connection-sharing-on.png" alt-text="Screenshot showing the manage cloud connection sharing feature toggled on.":::
 
+
 ## Related content
 
 - [Connectors overview](connector-overview.md)

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

@@ -113,7 +113,7 @@ To make the Fabric data agent tool available to your Azure AI agent, use a conne
 
 ```python
 # The Fabric connection ID can be found in the Azure AI Foundry project as a property of the Fabric tool
-# Your connection ID is in the format /subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group>/providers/Microsoft.MachineLearningServices/workspaces/<your-project-name>/connections/<your-fabric-connection-name>
+# Your connection ID is in the format /subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group>/providers/Microsoft.CognitiveServices/accounts/<ai-foundry-resource-name>/projects/<your-project-name>/connections/<your-fabric-connection-name>
 conn_id = "your-connection-id"
 
 # Initialize agent Fabric tool and add the connection ID
@@ -171,4 +171,4 @@ print(f"Messages: {messages}")
 ## Related content
 
 - [Data agent concept](concept-data-agent.md)
-- [Data agent scenario](data-agent-scenario.md)
+- [Data agent scenario](data-agent-scenario.md)

docs/data-science/tutorial-data-science-explore-notebook.md

@@ -165,6 +165,7 @@ Show the distribution of exited versus nonexited customers across the categorica
 
 ```python
 attr_list = ['Geography', 'Gender', 'HasCrCard', 'IsActiveMember', 'NumOfProducts', 'Tenure']
+df_clean['Exited'] = df_clean['Exited'].astype(str)
 fig, axarr = plt.subplots(2, 3, figsize=(15, 4))
 for ind, item in enumerate (attr_list):
     sns.countplot(x = item, hue = 'Exited', data = df_clean, ax = axarr[ind%2][ind//2])
@@ -198,6 +199,7 @@ plt.show()
 Perform feature engineering to generate new attributes based on current attributes:
 
 ```python
+df_clean['Tenure'] = df_clean['Tenure'].astype(int)
 df_clean["NewTenure"] = df_clean["Tenure"]/df_clean["Age"]
 df_clean["NewCreditsScore"] = pd.qcut(df_clean['CreditScore'], 6, labels = [1, 2, 3, 4, 5, 6])
 df_clean["NewAgeScore"] = pd.qcut(df_clean['Age'], 8, labels = [1, 2, 3, 4, 5, 6, 7, 8])