You can form a partition key by concatenating multiple property values into a single artificial partitionKey property. These keys are referred to as synthetic keys.
Another possible strategy to distribute the workload more evenly is to append a random number at the end of the partition key value. When you distribute items in this way, you can perform parallel write operations across partitions.
Note: It's the best practice to have a partition key with many distinct values, such as hundreds or thousands. The goal is to distribute your data and workload evenly across the items associated with these partition key values. If such a property doesn't exist in your data, you can construct a synthetic partition key.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/synthetic-partition-keys

Explanation:
You can restrict access to your Azure App Service app by enabling various types of authentication for the app. One way to set up authentication is to request a client certificate when the client request is sent by using Transport Layer Security (TLS) / Secure Sockets Layer (SSL) and to validate the certificate. This mechanism is called mutual authentication or client certificate authentication.
Step 1: Upgrade the pricing tier of the App Service Plan.
Prepare your web app
If you want to create custom TLS/SSL bindings or to enable client certificates for your App Service app, your App Service plan must be in the Basic, Standard, Premium, or Isolated tiers.
Make sure that your web app is in a supported pricing tier.
Changing from a D1 (Shared) tier to a Basic tier on Azure App Service is an upgrade. While both tiers are for web apps, the Basic tier provides dedicated resources and more features compared to the shared environment of the D1 tier.
Step 2: Modify the client certificate mode of the Configuration settings of App1.
Enable client certificates
When you enable client certificates for your app, you should select your choice of client certificate mode. The mode defines how your app handles incoming client certificates.
Step 3: Modify the certificate exclusion path of the Configuration settings of App1.
Exclude paths from requiring authentication
When you enable mutual authentication for your application, all paths under the root of your app require a client certificate for access. To remove this requirement for certain paths, define exclusion paths as part of your application configuration.
Reference:
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-configure-tls-mutual-auth

Explanation:
https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency?tabs=portal%2Cdotnetv2%2Capi-async#override-the-default-consistency-level

Event Hub would be a solution here NOT Notification Hub.
Azure Notification Hub is for only to push data to the client devices but not to receive data from client devices.
Reference:
https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services

Explanation:
https://learn.microsoft.com/en-us/azure/container-apps/traffic-splitting?pivots=azure-cli