When administrators query the Microsoft Graph /v1.0/organization endpoint, they often notice fields like securityComplianceNotificationMails, securityComplianceNotificationPhones, and technicalNotificationMails.
Many users then try to locate these values inside the admin portal but cannot find them. This situation creates confusion about whether the fields are deprecated or simply hidden. This guide explains what these properties mean, where they appear, and how you can access them correctly.
What Data the Microsoft Graph Organization Endpoint Returns
The /organization endpoint in the Microsoft Graph API returns tenant-level configuration information for a Microsoft Entra tenant.
Example request:
GET https://graph.microsoft.com/v1.0/organizationExample response snippet:
{
"value": [
{
"id": "tenant-id",
"displayName": "Contoso Ltd",
"technicalNotificationMails": [
"[email protected]"
],
"securityComplianceNotificationMails": [
"[email protected]"
],
"securityComplianceNotificationPhones": []
}
]
}These properties store contact details used for security or technical notifications related to the tenant.
Meaning of Each Property
Microsoft defines the properties as follows.
| Property | Purpose |
|---|---|
| technicalNotificationMails | Email addresses that receive technical notifications about the tenant |
| securityComplianceNotificationMails | Email addresses used for security or compliance notifications |
| securityComplianceNotificationPhones | Phone numbers used for security notifications |
These fields belong to the organization object, which represents the tenant in Microsoft Graph.
Where These Fields Appear in the Admin Portal
Some administrators expect to see these values directly inside the admin interface. However, Microsoft does not consistently expose them in the UI.
The email fields may appear in tenant contact settings in the Microsoft Entra admin center depending on tenant configuration.
Typical navigation path:
Microsoft Entra admin center
→ Identity
→ Overview
→ PropertiesThis page contains tenant information and may display contact email fields used for notifications.
However, Microsoft documentation does not guarantee that these Graph properties always map directly to visible UI fields.
Field That Does Not Appear in the UI
The property below generally does not appear anywhere in the portal interface.
securityComplianceNotificationPhonesAdministrators usually access or configure this value only through:
- Microsoft Graph API
- PowerShell automation
Because of this limitation, many tenants show this property as empty or null.
How to Retrieve These Fields Using Graph API
You can retrieve the values with a simple request.
GET https://graph.microsoft.com/v1.0/organizationYou must include a valid access token.
Example header:
Authorization: Bearer ACCESS_TOKENYou can test the request easily using the Microsoft Graph Explorer.
Required Permissions
Your account or application must have one of the following permissions.
| Permission | Purpose |
|---|---|
| Organization.Read.All | Allows reading tenant organization information |
| Directory.Read.All | Allows reading directory data |
Without these permissions, Microsoft Graph will reject the request.
Are These Fields Deprecated?
These properties are not officially deprecated. Microsoft Graph still returns them in the organization resource.
However:
- Microsoft rarely references them in modern admin workflows.
- They may not appear clearly in the admin UI.
- Most administrators interact with them through automation or API queries.
Because of this behavior, some users assume they are deprecated even though they still exist in the Graph schema.
Microsoft Graph Organization Properties: Quick Summary
| Property | Visible in UI | Access Method |
|---|---|---|
| technicalNotificationMails | Sometimes visible | Graph API or admin portal |
| securityComplianceNotificationMails | Sometimes visible | Graph API or admin portal |
| securityComplianceNotificationPhones | No | Graph API or PowerShell |
The Microsoft Graph /v1.0/organization endpoint exposes several tenant-level notification fields that are not always visible in the admin interface. Administrators often access these values through the API when auditing tenant configuration or building automation scripts.
If you work with tenant automation, querying the organization resource can help you verify notification contacts and maintain accurate security alert settings.
