https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-service-endpoints-overview

One for the finance department, and one for the IT department.
Note: If your organization has many Azure subscriptions, you might need a way to efficiently manage access, policies, and compliance for those subscriptions. Management groups provide a governance scope above subscriptions. When you organize subscriptions into management groups, the governance conditions that you apply cascade by inheritance to all associated subscriptions.
Management groups give you enterprise-grade management at scale, no matter what type of subscriptions you might have. However, all subscriptions within a single management group must trust the same Microsoft Entra tenant.
For example, you can apply a policy to a management group that limits the regions available for virtual machine (VM) creation. This policy would be applied to all nested management groups, subscriptions, and resources to allow VM creation only in authorized regions.
Reference:
https://learn.microsoft.com/en-us/azure/governance/management-groups/overview

Explanation:
Box 1: BloblBlobStorage with Premium performance and Zone-redundant storage (ZRS) replication.
BlockBlobStorage accounts: Storage accounts with premium performance characteristics for block blobs and append blobs. Recommended for scenarios with high transactions rates, or scenarios that use smaller objects or require consistently low storage latency. Premium:
optimized for high transaction rates and single-digit consistent storage latency.
Box 2: General purpose v2 with Standard performance.
General-purpose v2 accounts: Basic storage account type for blobs, files, queues, and tables.
Recommended for most scenarios using Azure Storage.
Reference:
https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy

https://learn.microsoft.com/en-us/azure/databricks/administration-guide/users-groups/service- principals#what-is-a-service-principal A service principal is an identity that you create in Azure Databricks for use with automated tools, jobs, and applications. Service principals give automated tools and scripts API-only access to Azure Databricks resources, providing greater security than using users or groups. It also prevents jobs and automations from failing if a user leaves your organization or a group is modified.

As shown below, for the Azure Logic App, you have to go to the Workflow settings and enable High Throughput.

Reference:
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-limits-and-config