I think there is a misunderstanding here on how data is ingested into Sentinel. It is very uncommon and difficult to ingest historic data in the manner you are describing. Rather than trying to pull in historic files from blob storage, the best way is to send active logs using one of the provided data connectors. They will ingest data directly from Microsoft solutions, from a monitoring agent (Microsoft or Logstash), from a log forwarder (Syslog/CEF), or from an API [depending on the specific data connector. Your CB logs will likely use Syslog over the forwarder or an API based connection.
If you are interested in alert correlation, Sentinel has analytic rules for generating alerts. Either from customizable templates included with each connector or custom rules. Alerts are not automatically correlated within Sentinel by default. These rules do have some limited alert grouping capabilities if configured. With the new Unified XDR portal, Sentinel now sends all alerts to the Unified XDR portal which automatically correlates all Microsoft and 3rd party alerts into incidents.
In short, ingest your data into Sentinel using a connector, use analytic rules to generate alerts, configure alert grouping at the rule level if needed, though in most cases the Unified XDR portal will perform alert correlation automatically.