ADF - REST API Copy Data Activity - Best Practices

Your sequential design protects franchise context, but the shared “switch franchise” state is the bottleneck. Parallel execution is safe only when each iteration has isolated state. Use a child pipeline receiving the franchise identifier, report, page, and unique Blob path as parameters; avoid shared variables or a common filename. If Vonigo permits independent sessions or explicit franchise identifiers, run the outer ForEach in parallel with a conservative batchCount below its rate limit. Otherwise keep franchises sequential and parallelize only independent reports within the selected franchise. Use REST connector pagination rules when the response exposes a next link, header, or page parameter. Do not stop on bytes read: compression, headers, and schema changes make it an unreliable record sentinel. End on the documented empty result, missing next token, or parsed record count. Add retry with backoff, log franchise/page/output together, and validate counts before promoting files to the silver layer.