Overview

The Microsoft Fabric OneLake Connector provides seamless and secure integration with Microsoft Fabric OneLake, enabling data to be read from and written to the platform. It supports a variety of file formats, including flat files and complex structured files such as Avro, JSON, ORC, Parquet, and PDF files within CDI-Advanced mappings.

Pre-Requisites
Self-Service Resources
Goals
  • Securely read data from or write to Microsoft Fabric OneLake 
  • Read and write flat files and flat structured complex file 
  • Enhance analytics by utilizing Microsoft Fabric OneLake as a data lake destination. 
  • Compatibility with CDI-Advanced mappings, enabling custom transformations and metadata profiling. 
  • Read PDF files in CDI-Advanced mode 
Outcome
  • Seamlessly integrate their data into Fabric OneLake for further processing. 
  • Efficiently read, write and process the data of several file formats residing on Fabric OneLake. 
Required Roles/Personas
Required Roles/Personas
  • Integration Developer: Configures and manages mappings with the connector. 
  • Cloud Architect: Sets up runtime environments and ensures compatibility. 
  • System Admin: Manages permissions in Azure Active Directory and Power BI settings. 
Additional Information
Additional Information
  • Unsupported cases such as the workspace name containing invalid characters like spaces or file naming without a proper path delimiter are resolved through step-by-step troubleshooting guides. 
  • The connector relies on Azure Data Lake Storage Gen2 APIs for open access to Fabric OneLake resources, ensuring compatibility with industry standards. 
Actions
Add to Favorites
Engagement Details
Catalog Type

Ask An Expert

Engagement Category

Feature Clarity

Products

Cloud Data Integration

Engagement Type

Ask An Expert

Adoption Stage

Configure

Implement

Focus Area

Adoption - Technical

Functional

Engagement ID

AAE-CDI-033

Disclaimer

  • All the topics covered in the Success Accelerators/Ask An Expert sessions are intended for guidance and advisory only. This is implicit and it will not be called out under the scope of each engagement.
  • Customers need to include their relevant technical/business team members highlighted in each engagement topic to derive the best out of each engagement.
  • Customers need to perform any hands-on work by themselves leveraging the guidance from these engagements.
  • Customers need to work with Informatica Global Customer Support for any product bugs/issues and troubleshooting.

Success

Link Copied to Clipboard