---
schema_version: "1"
id: 0d0db43e9d8b27561cff7b8aaa6e8b12dd9bd20aa832bd91d1956e9d55e9f095
title: Analytics Data Integration
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_bi_integrate_data.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_data.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 48920a40b00e76cb761bdf0f610fcb7138fec8c943c93f3563a23800e5e0bbb7
description: Write and schedule your custom CRM Analytics recipes to output your transformed data directly to Data 360 data lake objects. Securely access your Amazon Redshift data by using a virtual private connection. Take advantage of OAuth functionality in your Microsoft Azure SQL Database connection.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Analytics Data Integration

Write and schedule your custom CRM Analytics recipes to output your transformed data directly to Data 360 data lake objects. Securely access your Amazon Redshift data by using a virtual private connection. Take advantage of OAuth functionality in your Microsoft Azure SQL Database connection.

- **[Use CRM Analytics Datasets in Data 360 (Generally Available)](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_wdc_ga.htm&release=260&type=5)**  
    Take advantage of the latest Data 360 features while retaining the functionality of CRM Analytics recipes. Write and schedule your custom CRM Analytics recipes to output your transformed data directly to Data 360 data lake objects (DLO). Then you can use your CRM Analytics data to create calculated insights, semantic models, and Data 360 reports and dashboards. This feature, now generally available, includes a change since the last release: Users can now select a category on the DLO.
- **[Securely Connect Your Private Redshift Data to CRM Analytics](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_redshift_vpc.htm&release=260&type=5)**  
    Integrate data from your private Amazon Redshift data warehouse into CRM Analytics. Use a virtual private connection (VPC) to make sure that all data transfer happens over an internal network, bypassing the public internet for enhanced security and compliance.
- **[Use OAuth Security with Your Microsoft Azure SQL Database Connection](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_azure_oauth.htm&release=260&type=5)**  
    Increase data security by connecting to Microsoft Azure SQL Database using OAuth 2.0 authentication. You can now provide Azure authentication values directly, eliminating the need for a separate external authentication provider setup.
- **[Upgrade to OAuth Security for Your Salesforce External Connections](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_salesforce_external_oauth.htm&release=260&type=5)**  
    Increase data security by using OAuth 2.0 authentication with your Salesforce external input and output connectors. The SOAP `login()` API isn't supported after v64. To maintain data sync, you must upgrade all existing Salesforce external connections to use OAuth before the Winter ‘27 release.
- **[Control Access to Data Based on a User’s Assigned Territories (Generally Available)](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_territory_hierarchy_security_predicates_ga.htm&release=260&type=5)**  
    Allow users to see data in dashboards and insights only for the territories they’re assigned to in Territory Management 2.0. Reference the territory hierarchy from your dataset security predicates. Previously, you could only reference user data. This feature is now generally available.
- **[Improve Write to Data 360 Output Performance with Optimized Append, Upsert, and Delete Actions (Beta)](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_optimized_wdc_operations_beta.htm&release=260&type=5)**  
    Decrease processing time when writing to Data 360 by overwriting existing Data Lake Objects (DLO) using optimized output operations. Instead of processing all rows of the output data, the optimized append, upsert, and delete actions run incrementally on subsets of the output data, resulting in faster runs.
- **[Accelerate Data Updates in Using Unique IDs for External Objects](https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_user_primary_key_external.htm&release=260&type=5)**  
    Now you can specify an external object field as a unique ID to function as a primary key for that object. Use defined primary keys to update massive datasets in minutes by only processing changed records. For example, a nightly sync for a two-billion-row sales transaction object now processes only the 500,000 new or changed records instead of the entire dataset.