Explanation:
Box 1: Azure Database for PostgreSQL Flexible Server
For horizontal scaling of transactional writes in Azure PostgreSQL using row-based sharding, you should utilize Azure Database for PostgreSQL Flexible Server with Elastic Clusters. This feature leverages the Citus extension for PostgreSQL, enabling you to shard your data across multiple nodes and manage them as a single, distributed database.
Box 2: Distributed tables
Azure Database for PostgreSQL Flexible Server uses distributed tables for scaling through the use of an Elastic cluster, powered by the Citus extension. This allows for scaling out by adding more nodes to the cluster and distributing data across them, rather than just increasing the compute power of a single node.
Reference:
https://techcommunity.microsoft.com/blog/adforpostgresql/postgres-horizontal-scaling-with- elastic-clusters-on-azure-database-for-postgres/4303508

You can schedule a powershell script with Azure Logic Apps.
When you want to run code that performs a specific job in your logic apps, you can create your own function by using Azure Functions. This service helps you create Node.js, C#, and F# functions so you don't have to build a complete app or infrastructure to run code. You can also call logic apps from inside Azure functions.
Reference:
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-azure-functions

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

Explanation:
Box 1: User subscription and low-priority virtual machines
The first job type will consist of short-running tasks for a development environment.
Among the many ways to purchase and consume Azure resources are Azure low priority VMs and Spot VMs.
These virtual machines are compute instances allocated from spare capacity, offered at a highly discounted rate compared to ג €on demandג € VMs.
This means they can be a great option for cost savings ג€" for the right workloads Box 2: Batch service and dedicate virtual machines The second job type will consist of long-running Message Passing Interface (MPI) applications for a production environment that requires timely job completion.
Azure Batch Service is a cloud based job scheduling and compute management platform that enables running large-scale parallel and high performance computing applications efficiently in the cloud. Azure Batch Service provides job scheduling and in automatically scaling and managing virtual machines running those jobs.
Reference:
https://www.parkmycloud.com/blog/azure-low-priority-vms
https://azure.microsoft.com/en-us/pricing/details/batch/

Explanation:
Box 1: An Azure Log Analytics workspace
To be able to create an alert we send the Azure AD logs to An Azure Log Analytics workspace.
Note: You can forward your AAD logs and events to either an Azure Storage Account, an Azure Event Hub, Log Analytics, or a combination of all of these.
Box 2: Log
Ensure Resource Type is an analytics source like Log Analytics or Application Insights and signal type as Log.
Reference:
https://4sysops.com/archives/how-to-create-an-azure-ad-admin-login-alert/
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-log