{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
        "slug": "dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/"
        },
        "title": "Do not treat Intune custom notifications as confirmed urgent delivery",
        "summary": "What communication can safely rely on an Intune custom notification?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "identity-cloud",
            "label": "Identity & cloud",
            "alt": "Governed cloud identity system with connected service and lifecycle nodes.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-10T00:23:44+00:00",
        "modified_at": "2026-09-10T02:08:05+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 223,
        "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.",
        "primary_source": {
            "name": "Device Action: Send Custom Notification - Microsoft Intune | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Device Action: Send Custom Notification</a>.</p>",
        "content_text": "Source facts\nIntune 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.\nApplicability\nConfirm 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.\nDSE recommendation\nApprove 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.\nVerification\nTest 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.\nOfficial references\nMicrosoft Learn: Device Action: Send Custom Notification.",
        "content_markdown": "## Source facts\n\nIntune 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).\n\n## Applicability\n\nConfirm 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.\n\n## DSE recommendation\n\nApprove 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.\n\n## Verification\n\nTest 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.\n\n## Official references\n\n[Microsoft Learn: Device Action: Send Custom Notification](https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification)."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Do not treat Intune custom notifications as confirmed urgent delivery",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/",
                "headline": "Do not treat Intune custom notifications as confirmed urgent delivery",
                "description": "What communication can safely rely on an Intune custom notification?",
                "abstract": "What communication can safely rely on an Intune custom notification?",
                "articleBody": "Source facts\nIntune 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.\nApplicability\nConfirm 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.\nDSE recommendation\nApprove 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.\nVerification\nTest 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.\nOfficial references\nMicrosoft Learn: Device Action: Send Custom Notification.",
                "datePublished": "2026-09-10T00:23:44+00:00",
                "dateModified": "2026-09-10T02:08:05+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-492-do-not-treat-intune-custom-notifications-as-confirmed-urgent-delivery/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Do not treat Intune custom notifications as confirmed urgent delivery"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 223,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Device Action: Send Custom Notification - Microsoft Intune | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/intune/device-management/actions/send-custom-notification"
                }
            }
        ]
    }
}