A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
For Azure email notifications tied to role-based alerting, first verify how the email action is configured.
- Check whether the notification uses Email Azure Resource Manager Role. This action only uses Azure Resource Manager role assignments at the subscription scope and only for assignments of type User or Group. If the role was assigned at the resource or resource group scope, the email notification isn't sent by this mechanism.
- Check whether the email was suppressed by an alert processing rule. In Azure portal, open the fired alert and review the History tab for suppressed action groups.
- Verify that the recipient mailbox can accept the notification.
Allow these sender addresses in mail filtering or spam protection:
-
azure-noreply@microsoft.com -
azureemail-noreply@microsoft.com -
******@mail.windowsazure.com
-
- Test with a direct user mailbox instead of a distribution list or mailing list. Internal mailing lists and distribution lists often block external senders.
- Check inbox rules, spam, quarantine, and mail security filtering.
Review:
- client spam settings
- mailbox inbox rules
- Exchange or Microsoft 365 quarantine or sender filtering
- any email security appliance rules
If the expectation was that adding a developer to Access Control (IAM) would automatically send an email, the supported guidance in this context is only for alert email delivery. In that case, confirm that an alert or action group is configured to send the notification, and that it uses the correct role-based email action and scope.