Prerequisites

Implementation should not begin until the following prerequisites are available.

Business Prerequisites

The implementation team must receive:

• Source XML samples
• Target table requirements
• Business keys and incremental keys
• Field-level mapping rules
• Transformation rules
• List of required filters
• Analytical view mappings if reporting views are in scope
• Scenario and book-of-business rules if the API flow is in scope

Technical Prerequisites

The implementation environment must have:

• Microsoft Fabric workspace
• Fabric Lakehouse
• Lakehouse SQL Analytics Endpoint available
• Spark runtime available for notebook execution
• SQL Server access for metadata and control tables
• Storage location or shortcut path for XML files if XML source mode is required
• Target Lakehouse table naming standards
• Final workspace and Lakehouse naming conventions
• Target workspace for semantic model and report deployment
• Power BI or Fabric report consumption environment if embedded analytics is in scope

Security and Access

The implementation team requires:

• Service principal or managed identity strategy
• Access to SQL Server
• Access to Key Vault or an equivalent secret store
• Access to the rating API endpoint
• Network connectivity between Fabric and source and target systems
• Permissions to create and alter Delta tables
• Permissions to create and alter Lakehouse SQL views
• Semantic model deployment permissions in the target workspace
• XMLA read-write access if semantic model schema auto-update is required
• Fabric REST access for semantic model refresh automation
• Power BI Pro licensing for end users if User Owns Data embedding is retained

Data Contracts

Before configuration begins, the following data contracts must be agreed upon:

• Source table names
• Target table names
• Audit column definitions
• Merge key definitions
• Success and failure status handling
• Branch behavior for current premium and proposed premium
• XML namespace handling rules