# Maintain contactable tenant-security addresses alongside Azure alert routing

> Review administrative contact addresses used for tenant-level security communications.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-168-maintain-contactable-tenant-security-addresses-alongside-azure-alert-routing/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:32:12+00:00
- Modified: 2026-09-17T16:46:29+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

Review administrative contact addresses used for tenant-level security communications.

## Potentially affected

Use this review for the contact records responsible for receiving tenant-level Azure security information. Identify the people or governed mailboxes represented by those records and the team responsible for maintaining them. Keep this contact review separate from application-specific action groups and workload incident channels.

## DSE recommendation

DSE recommends assigning an owner to periodically reconcile the named contact records with the current response organization.

## Article

## Source facts

Microsoft advises keeping the contactable email addresses for an organization’s Global Admins, Technical Contacts and Security Admins current and correct. The source says those addresses are used for security issues that affect workloads at the tenant level. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/service-health/stay-informed-security).

## Applicability

Use this review for the contact records responsible for receiving tenant-level Azure security information. Identify the people or governed mailboxes represented by those records and the team responsible for maintaining them. Keep this contact review separate from application-specific action groups and workload incident channels.

## DSE recommendation

DSE recommends assigning an owner to periodically reconcile the named contact records with the current response organization. Verify that each address is reachable and monitored through an approved contact test. Include role changes and offboarding in the review triggers. Record the intended escalation route without distributing sensitive tenant administration details unnecessarily.

## Verification

Inspect the actual contact values with an authorized administrator and compare them with the approved roster. Document the outcome of a permitted delivery test and identify who will act on a received security notice. Resolve obsolete or unmonitored addresses through the normal identity process. Keep a dated contact-review record rather than assuming a configured Azure alert proves these separate email paths are maintained.

## Official references

[Microsoft Learn: Security notifications overview](https://learn.microsoft.com/en-us/azure/service-health/stay-informed-security).

## Primary reference

- Name: Security notifications overview - Azure Service Health | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/service-health/stay-informed-security
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Maintain contactable tenant-security addresses alongside Azure alert routing,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-168-maintain-contactable-tenant-security-addresses-alongside-azure-alert-routing/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.