{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
        "slug": "dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/"
        },
        "title": "Verify an AOSP factory reset after a Delete action removes its Intune record",
        "summary": "When does an Android AOSP factory reset occur relative to its removal from the Intune device list?",
        "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": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "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-17T16:32:24+00:00",
        "modified_at": "2026-09-17T16:46:28+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 1,
        "word_count": 210,
        "potentially_affected": "Apply this distinction to Intune corporate-owned, user-associated Android AOSP devices being reassigned or retired. Identify the exact device and the approved remote action before interpreting its management status.",
        "dse_recommendation": "DSE recommends writing the expected sequence into the handoff record before the authorized destructive action.",
        "primary_source": {
            "name": "Set up Android (AOSP) device management in Intune for corporate-owned user-associated devices - Microsoft Intune | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/intune/device-enrollment/android/setup-aosp-corporate-user-associated",
            "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>Microsoft states that a wiped Android AOSP device remains Pending until its factory reset completes, after which Intune removes it from the device list. Delete follows a different sequence: the record disappears immediately without a pending status, and the factory reset occurs at the device&#8217;s next check-in. <a href=\"https://learn.microsoft.com/en-us/intune/device-enrollment/android/setup-aosp-corporate-user-associated\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Apply this distinction to Intune corporate-owned, user-associated Android AOSP devices being reassigned or retired. Identify the exact device and the approved remote action before interpreting its management status.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends writing the expected sequence into the handoff record before the authorized destructive action. Preserve the device identifier, action time and required data-preservation evidence. For Delete, keep a separate open item for reset verification after the record disappears, and assign it to the person who can inspect the device before reissue.</p>\n<h2>Verification</h2>\n<p>Rehearse the approved procedure on a spare device containing only test data. Compare the device-list status with the actual device state and check-in sequence. Confirm the intended factory-reset result on the device before accepting it for reassignment. Retain that observation separately from the portal action receipt, particularly when the device was offline at the time of the request.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/intune/device-enrollment/android/setup-aosp-corporate-user-associated\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Set up Intune enrollment for Android (AOSP) corporate-owned user-associated devices</a>. Source reviewed September 17, 2026.</p>",
        "content_text": "Source facts\nMicrosoft states that a wiped Android AOSP device remains Pending until its factory reset completes, after which Intune removes it from the device list. Delete follows a different sequence: the record disappears immediately without a pending status, and the factory reset occurs at the device’s next check-in. Microsoft Learn.\nApplicability\nApply this distinction to Intune corporate-owned, user-associated Android AOSP devices being reassigned or retired. Identify the exact device and the approved remote action before interpreting its management status.\nDSE recommendation\nDSE recommends writing the expected sequence into the handoff record before the authorized destructive action. Preserve the device identifier, action time and required data-preservation evidence. For Delete, keep a separate open item for reset verification after the record disappears, and assign it to the person who can inspect the device before reissue.\nVerification\nRehearse the approved procedure on a spare device containing only test data. Compare the device-list status with the actual device state and check-in sequence. Confirm the intended factory-reset result on the device before accepting it for reassignment. Retain that observation separately from the portal action receipt, particularly when the device was offline at the time of the request.\nOfficial references\nMicrosoft Learn: Set up Intune enrollment for Android (AOSP) corporate-owned user-associated devices. Source reviewed September 17, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft states that a wiped Android AOSP device remains Pending until its factory reset completes, after which Intune removes it from the device list. Delete follows a different sequence: the record disappears immediately without a pending status, and the factory reset occurs at the device’s next check-in. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-enrollment/android/setup-aosp-corporate-user-associated).\n\n## Applicability\n\nApply this distinction to Intune corporate-owned, user-associated Android AOSP devices being reassigned or retired. Identify the exact device and the approved remote action before interpreting its management status.\n\n## DSE recommendation\n\nDSE recommends writing the expected sequence into the handoff record before the authorized destructive action. Preserve the device identifier, action time and required data-preservation evidence. For Delete, keep a separate open item for reset verification after the record disappears, and assign it to the person who can inspect the device before reissue.\n\n## Verification\n\nRehearse the approved procedure on a spare device containing only test data. Compare the device-list status with the actual device state and check-in sequence. Confirm the intended factory-reset result on the device before accepting it for reassignment. Retain that observation separately from the portal action receipt, particularly when the device was offline at the time of the request.\n\n## Official references\n\n[Microsoft Learn: Set up Intune enrollment for Android (AOSP) corporate-owned user-associated devices](https://learn.microsoft.com/en-us/intune/device-enrollment/android/setup-aosp-corporate-user-associated). Source reviewed September 17, 2026."
    },
    "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-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Verify an AOSP factory reset after a Delete action removes its Intune record",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/",
                "headline": "Verify an AOSP factory reset after a Delete action removes its Intune record",
                "description": "When does an Android AOSP factory reset occur relative to its removal from the Intune device list?",
                "abstract": "When does an Android AOSP factory reset occur relative to its removal from the Intune device list?",
                "articleBody": "Source facts\nMicrosoft states that a wiped Android AOSP device remains Pending until its factory reset completes, after which Intune removes it from the device list. Delete follows a different sequence: the record disappears immediately without a pending status, and the factory reset occurs at the device’s next check-in. Microsoft Learn.\nApplicability\nApply this distinction to Intune corporate-owned, user-associated Android AOSP devices being reassigned or retired. Identify the exact device and the approved remote action before interpreting its management status.\nDSE recommendation\nDSE recommends writing the expected sequence into the handoff record before the authorized destructive action. Preserve the device identifier, action time and required data-preservation evidence. For Delete, keep a separate open item for reset verification after the record disappears, and assign it to the person who can inspect the device before reissue.\nVerification\nRehearse the approved procedure on a spare device containing only test data. Compare the device-list status with the actual device state and check-in sequence. Confirm the intended factory-reset result on the device before accepting it for reassignment. Retain that observation separately from the portal action receipt, particularly when the device was offline at the time of the request.\nOfficial references\nMicrosoft Learn: Set up Intune enrollment for Android (AOSP) corporate-owned user-associated devices. Source reviewed September 17, 2026.",
                "datePublished": "2026-09-17T16:32:24+00:00",
                "dateModified": "2026-09-17T16:46:28+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/"
                },
                "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-20260917-156-verify-an-aosp-factory-reset-after-a-delete-action-removes-its-intune-record/#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": "Verify an AOSP factory reset after a Delete action removes its Intune record"
                },
                "articleSection": [
                    "Cybersecurity",
                    "IT"
                ],
                "keywords": [
                    "Cybersecurity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 210,
                "timeRequired": "PT1M",
                "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": "Set up Android (AOSP) device management in Intune for corporate-owned user-associated devices - Microsoft Intune | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/intune/device-enrollment/android/setup-aosp-corporate-user-associated"
                }
            }
        ]
    }
}