Skip to content
LambogeniusDocs

Integration Migration Tool

Safeguards

How source facts, generated changes, and deployment authority are kept separate.

Current compatibility routeBizTalk → Azure Integration ServicesThese docs describe the current buildable implementation.

Keep source facts, generated changes, and deployment authority separate

Evidence before inference

Deterministic parsers establish source facts; AI explanations and recommendations cannot replace them.

Read-only source boundaries

Keep source, starter, and reference repositories read-only; generate each candidate inside an explicit output boundary.

Path allowlists

Restrict generated output to approved project paths such as workflows, Functions, infrastructure, and tests.

Visible gaps

Unknown or unsupported behavior is reported explicitly instead of becoming plausible-looking generated output.

Safe resume

Content hashes and checkpoints prevent modified generated files from being silently accepted during resume.

Separate deployment approval

Generation does not imply deployment; queuing an Azure pipeline requires an enabled and complete deployment configuration.