The diagnostics log outputs tempDB contention details. You can use the information as the starting point for troubleshooting.
You can use the Intelligent Insights performance diagnostics log of Azure SQL Database to troubleshoot performance issues.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/intelligent-insights-troubleshoot- performance#tempdb-contention
https://docs.microsoft.com/en-us/azure/azure-sql/database/intelligent-insights-use-diagnostics-log

To protect your Azure resources, you can use Resource Locks.
To prevent accidental deletion of an Azure database, use the Azure portal to create a "Delete" lock on the database or its parent resources, such as the SQL server or resource group. This lock will prevent any user, including owners, from deleting the database.
Step 1: Navigate to the resource: Go to the Azure portal and locate the Azure SQL database you want to protect. You can do this by searching for "SQL databases" or navigating through your resource groups. [Select db1] Step 2: Open the Locks tab: In the database's overview, locate the "Locks" tab under the
"Settings" section.
Step 3: Add a new lock: Click the "Add" button to create a new lock.
Step 4: Configure the lock:
Lock Name: Give the lock a descriptive name (e.g., "PreventDeleteLock").
Lock Type: Select "Delete".
Level: Set the level to "CanNotDelete".
Notes (Optional): Add any relevant notes about the lock.
Step 5: Apply the lock: Click "OK" to save the lock.
Reference:
https://techcommunity.microsoft.com/blog/adformysql/preventing-and-recovering-from-accidental-deletion-of-an-azure-database-for-mysq/4388503

C: Advanced Data Security (ADS) is a unified package for advanced SQL security capabilities.
ADS is available for Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics. It includes functionality for discovering and classifying sensitive data D: You can apply sensitivity-classification labels persistently to columns by using new metadata attributes that have been added to the SQL Server database engine. This metadata can then be used for advanced, sensitivity-based auditing and protection scenarios.
A: An important aspect of the information-protection paradigm is the ability to monitor access to sensitive data. Azure SQL Auditing has been enhanced to include a new field in the audit log called data_sensitivity_information. This field logs the sensitivity classifications (labels) of the data that was returned by a query. Here's an example:

Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/data-discovery-and-classification-overview

To create an email alert for high CPU percentage utilization in an Azure database within the Azure portal, you'll first need to navigate to your database resource, then to the "Alerts" section.
From there, you'll create a new alert rule, define the CPU percentage threshold, configure an action group for email notifications, and finally, create the alert rule.
Create alerts for Azure SQL Database and Azure Synapse Analytics using the Azure portal Step 1: In the Azure portal, locate the resource you are interested in monitoring and select it.
[Select db1]
Step 2: In the resource menu under Monitoring, select Alerts. The text and icon might vary slightly for different resources.
Step 3: Select the + Create button, then Alert rule.
Step 4: On the Create an alert rule page, the Scope is automatically configured to the individual resource.
Capture activity peaks or sustained resource stress with alerts on the Metrics signal category.
Step 5: On the Condition tab, select See all signals and Select a signal from the list of Metrics.
Step 6: Select the desired metric, for example CPU percentage. Select Apply. [Select CPU percentage] Step 7: After you select a signal, the Alert logic options appear. A preview of recent activity in this resource for that signal is also displayed.
Step 8: Configure a Threshold type to determine when the alert will take action. Choose Aggregation type, Operator, and Threshold value as desired. A typical threshold is: Static, Maximum, Greater than, 80%.
Threshold: [Select 50%]
Operator: [Select Greater than]
Aggregation granularity: [Select 5 minutes]
Select the interval that's used to group the data points by using the aggregation type function.
Choose an Aggregation granularity (period) that's greater than the Frequency of evaluation to reduce the likelihood of missing the first evaluation period of an added time series.
Frequency of evaluation: [Select one minute]
Select how often the alert rule is to be run. Select a frequency that's smaller than the aggregation granularity to generate a sliding window for the evaluation.
Step 9: Under When to evaluate, determine the desired frequency of evaluation. Use the Check every and Lookback period dropdown lists.
Step 10: Optionally, you can add multiple conditions for this alert, choose the Add condition alert if desired.
Step 11: Select Next: Actions >.
Create the new alert rule
Step 12: Use the Use quick actions feature to create a new action group and provide an email or Azure mobile app notification target.
Reference:
https://learn.microsoft.com/en-us/azure/azure-sql/database/alerts-create?

Stage 1: Create the user
Create a user with SSMS (SQL Server Management Studio)
Step 1: In Object Explorer, expand the Databases folder.
Step 2: Expand the database in which to create the new database user. [Here db1] Step 3: Right-click the Security folder, point to New, and select User....
Step 4: In the Database User - New dialog box, on the General page, select one of the following user types from the User type list:
SQL user with login
SQL user with password (when contained database is enabled)
SQL user without login
User mapped to a certificate
User mapped to an asymmetric key
*-> Windows user
Step 4a: Select Windows User
Step 5: When you select an option, the remaining options in the dialog may change. Some options only apply to specific types of database users. Some options can be left blank and will use a default value.
User name
Enter a name for the new user. If you have chosen Windows user from the User type list, you can also select the ellipsis (...) to open the Select User or Group dialog box. [Specify User2-
12345678]
Step 6: Select OK.
Stage 2: Assign permissions
Additional Options
The Database User - New dialog box also offers options on four other pages: Owned Schemas, Membership, Securables, and Extended Properties.
Step 7: Select Securables
The Securables page lists all possible securables and the permissions on those securables that can be granted to the login.
Step 8: Select tables
Step 9: Grant Read Permission
Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/security/authentication-access/create-a-database-user