# Do not treat Intune custom notifications as confirmed urgent delivery

> What communication can safely rely on an Intune custom notification?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:23:44+00:00
- Modified: 2026-09-10T02:08:05+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What communication can safely rely on an Intune custom notification?

## Potentially affected

Confirm the target platform, enrollment, required app, and notification permissions. Treat this as an optional communication channel for ordinary operational reminders, not the sole route for an emergency or confidential instruction.

## DSE recommendation

Approve the message and audience outside the send operation.

## Article

## Source facts

Intune custom notifications have no delivery guarantee and are unsuitable for urgent communication. Group targeting addresses users, not device members. Intune neither retains sent message text nor tracks receipt. Microsoft warns against sensitive content because other apps may access it. Supported platforms on this page are Android Enterprise personal work profiles and iOS/iPadOS. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification).

## Applicability

Confirm the target platform, enrollment, required app, and notification permissions. Treat this as an optional communication channel for ordinary operational reminders, not the sole route for an emergency or confidential instruction.

## DSE recommendation

Approve the message and audience outside the send operation. Keep a controlled copy of the wording and intended recipients for the communication record. Review group membership as a user audience and avoid putting credentials, personal case details, or sensitive incident information in the message. Provide a separate, approved support contact and use the organization’s established urgent channel whenever timing matters.

## Verification

Test delivery with consenting users on representative supported devices and ask them to report what appeared. Record observation separately from the portal’s submission confirmation. If acknowledgement is required, collect it through a channel designed for that purpose. Do not count a successful send action as proof that every recipient saw the message or that anyone completed the requested task.

## Official references

[Microsoft Learn: Device Action: Send Custom Notification](https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification).

## Primary reference

- Name: Device Action: Send Custom Notification - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Do not treat Intune custom notifications as confirmed urgent delivery,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/
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.