Other Articles
- SQL Database – Enable Database Encryption
- SQL Server – Enable SQL Defender
- SQL Database – Monitor CPU Utilization
- SQL Database – Monitor IO Utilization
- SQL Database – Monitor Memory Utilization
- SQL Database – Protect From Direct Internet Traffic
- Storage Account – Enable Storage Encryption
- Storage Account – Disable Blob Public Access
- Storage Account – Disable Cross-Tenant Replication
- Storage Account – Disable Public Network Access
- Storage Account – Enable Microsoft Defender
- Storage Account – Enable Secure Transfer
- Storage Account – Enforce Minimum TLS Version
- Storage Account – Enforce Network Access Rule
- Storage Account – Enforce Private Endpoint Access
- User – Enable Azure MFA
- App Service – Disable Remote Debugging
- App Service – Enable Defender
- App Service – Enable Entra ID Registration
- App Service – Enable HTTP2
- App Service – Enforce Latest TLS Version
- App Service – Enforce Secure FTPS State
- App Service – Monitor Server Errors
- App Service – Redirect HTTP to HTTPS
- Cosmos DB – Enable Backup
- Cosmos DB – Enable Microsoft Defender
- Cosmos DB – Monitor Latency
- Cosmos DB – Ensure Private Connectivity
- Cosmos DB for PostgreSQL – Monitor CPU Utilization
- Cosmos DB for PostgreSQL – Monitor IO Utilization
- Cosmos DB for PostgreSQL – Monitor Memory Utilization
- Cosmos DB for PostgreSQL – Protect From Direct Internet Traffic
- Cosmos DB – Protect From Direct Internet Traffic
- Cosmos DB – Restrict Firewall Network Access
- Virtual Machine – Enable Defender
- Virtual Machine – Protect From Direct Internet Traffic
- Key Vault – Enable Defender
- Key Vault – Ensure Vault Recoverable
- Key Vault – Require Private Endpoint Access
- MySQL Flexible Server – Enable Audit Log Events Connection
- MySQL Flexible Server – Enable Audit Logs
- MySQL Flexible Server – Enforce Minimum TLS Version
- PostgreSQL Flexible Server – Configure Log File Retention
- PostgreSQL Flexible Server – Enable Connection Logging
- PostgreSQL Flexible Server – Enable Connection Throttling
- PostgreSQL Flexible Server – Enable Disconnection Logging
- PostgreSQL Flexible Server – Enable Log Checkpoints
- Network Security Group – Ensure Flow Logs Captured
- General – Enable Auto Provisioning Log Analytics
- General – Enable Security Notifications
General – Set Additional Email Address
This check ensures that additional email addresses are configured for security contacts in Microsoft Defender for Cloud. Configuring multiple contact addresses helps ensure that important security alerts and incident notifications are received promptly by the appropriate personnel.
Check Details
- Resource: Microsoft Defender for Cloud
- Check: Ensure Additional Email Address Is Configured
- Risk: If additional security contact email addresses are not configured, critical security alerts may not reach all responsible stakeholders, potentially delaying incident response and remediation efforts.
Remediation via Azure Portal
-
Log in to the Azure Portal.
-
Navigate to Microsoft Defender for Cloud.
-
In the left-hand menu, select Environment settings.
-
Select the relevant Subscription.
-
Under Settings, select Email notifications.
-
In the Additional email addresses field, enter one or more valid organizational email addresses
separated by commas.
- Click Save to apply the configuration.
Remediation via Azure CLI
-
Open Azure Cloud Shell or a local terminal with Azure CLI installed.
-
Check the current security contact configuration:
az security contact list
-
Configure additional email addresses for security alerts:
az security contact create \ --name default \ --email "primary@example.com" \ --alert-notifications On \ --alerts-admins On \ --additional-emails "security@example.com,ops@example.com"
-
Verify that additional email addresses are configured:
az security contact show \ --name default \ --query additionalEmails
Replace the example email addresses with valid organizational email accounts. Ensure that security and operational teams are included to maintain effective incident communication.