{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "slug": "dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles", "url": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/" }, "title": "Create separate Jamf Android app configurations for distinct activation profiles", "summary": "How should Intune app-configuration policies map to multiple Jamf Trust activation profiles?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-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:31:52+00:00", "modified_at": "2026-09-17T16:46:29+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 201, "potentially_affected": "Use this review when provisioning Jamf Trust through Intune for Android Enterprise and iOS. Inventory the intended activation profiles and the device groups that should receive each configuration.", "dse_recommendation": "DSE recommends maintaining a profile-to-policy map for the Android deployment.", "primary_source": { "name": "Add and assign MTD apps to Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-security/mobile-threat-defense/assign-apps", "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": "

Source facts

\n

Microsoft requires a unique Android Enterprise app-configuration policy for each Jamf Activation Profile; one policy can serve all target devices when only one profile is needed. For iOS, Microsoft documents that one configuration policy can cover all devices being provisioned with Jamf. For Jamf device synchronization through UEM Connect, the activation profile must select Microsoft Entra ID under Associated User. Microsoft Learn.

\n

Applicability

\n

Use this review when provisioning Jamf Trust through Intune for Android Enterprise and iOS. Inventory the intended activation profiles and the device groups that should receive each configuration.

\n

DSE recommendation

\n

DSE recommends maintaining a profile-to-policy map for the Android deployment. Give each policy an identifiable target population and record its activation-profile URL under the organization’s credential-handling controls. Review the iOS configuration independently rather than copying the Android policy layout without checking the documented platform workflow.

\n

Verification

\n

Assign configurations to an approved test group first. Confirm that representative Android devices activate under their intended profile and that the expected device association synchronizes. Validate the iOS provisioning path separately, then retain the configuration mapping and observed profile membership before expanding assignments.

\n

Official references

\n

Microsoft Learn: Add and assign Mobile Threat Defense (MTD) apps with Intune. Source reviewed September 17, 2026.

", "content_text": "Source facts\nMicrosoft requires a unique Android Enterprise app-configuration policy for each Jamf Activation Profile; one policy can serve all target devices when only one profile is needed. For iOS, Microsoft documents that one configuration policy can cover all devices being provisioned with Jamf. For Jamf device synchronization through UEM Connect, the activation profile must select Microsoft Entra ID under Associated User. Microsoft Learn.\nApplicability\nUse this review when provisioning Jamf Trust through Intune for Android Enterprise and iOS. Inventory the intended activation profiles and the device groups that should receive each configuration.\nDSE recommendation\nDSE recommends maintaining a profile-to-policy map for the Android deployment. Give each policy an identifiable target population and record its activation-profile URL under the organization’s credential-handling controls. Review the iOS configuration independently rather than copying the Android policy layout without checking the documented platform workflow.\nVerification\nAssign configurations to an approved test group first. Confirm that representative Android devices activate under their intended profile and that the expected device association synchronizes. Validate the iOS provisioning path separately, then retain the configuration mapping and observed profile membership before expanding assignments.\nOfficial references\nMicrosoft Learn: Add and assign Mobile Threat Defense (MTD) apps with Intune. Source reviewed September 17, 2026.", "content_markdown": "## Source facts\n\nMicrosoft requires a unique Android Enterprise app-configuration policy for each Jamf Activation Profile; one policy can serve all target devices when only one profile is needed. For iOS, Microsoft documents that one configuration policy can cover all devices being provisioned with Jamf. For Jamf device synchronization through UEM Connect, the activation profile must select Microsoft Entra ID under Associated User. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-security/mobile-threat-defense/assign-apps).\n\n## Applicability\n\nUse this review when provisioning Jamf Trust through Intune for Android Enterprise and iOS. Inventory the intended activation profiles and the device groups that should receive each configuration.\n\n## DSE recommendation\n\nDSE recommends maintaining a profile-to-policy map for the Android deployment. Give each policy an identifiable target population and record its activation-profile URL under the organization’s credential-handling controls. Review the iOS configuration independently rather than copying the Android policy layout without checking the documented platform workflow.\n\n## Verification\n\nAssign configurations to an approved test group first. Confirm that representative Android devices activate under their intended profile and that the expected device association synchronizes. Validate the iOS provisioning path separately, then retain the configuration mapping and observed profile membership before expanding assignments.\n\n## Official references\n\n[Microsoft Learn: Add and assign Mobile Threat Defense (MTD) apps with Intune](https://learn.microsoft.com/en-us/intune/device-security/mobile-threat-defense/assign-apps). 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-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "url": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Create separate Jamf Android app configurations for distinct activation profiles", "item": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "url": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/", "headline": "Create separate Jamf Android app configurations for distinct activation profiles", "description": "How should Intune app-configuration policies map to multiple Jamf Trust activation profiles?", "abstract": "How should Intune app-configuration policies map to multiple Jamf Trust activation profiles?", "articleBody": "Source facts\nMicrosoft requires a unique Android Enterprise app-configuration policy for each Jamf Activation Profile; one policy can serve all target devices when only one profile is needed. For iOS, Microsoft documents that one configuration policy can cover all devices being provisioned with Jamf. For Jamf device synchronization through UEM Connect, the activation profile must select Microsoft Entra ID under Associated User. Microsoft Learn.\nApplicability\nUse this review when provisioning Jamf Trust through Intune for Android Enterprise and iOS. Inventory the intended activation profiles and the device groups that should receive each configuration.\nDSE recommendation\nDSE recommends maintaining a profile-to-policy map for the Android deployment. Give each policy an identifiable target population and record its activation-profile URL under the organization’s credential-handling controls. Review the iOS configuration independently rather than copying the Android policy layout without checking the documented platform workflow.\nVerification\nAssign configurations to an approved test group first. Confirm that representative Android devices activate under their intended profile and that the expected device association synchronizes. Validate the iOS provisioning path separately, then retain the configuration mapping and observed profile membership before expanding assignments.\nOfficial references\nMicrosoft Learn: Add and assign Mobile Threat Defense (MTD) apps with Intune. Source reviewed September 17, 2026.", "datePublished": "2026-09-17T16:31:52+00:00", "dateModified": "2026-09-17T16:46:29+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/" }, "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-188-create-separate-jamf-android-app-configurations-for-distinct-activation-profiles/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Create separate Jamf Android app configurations for distinct activation profiles" }, "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": 201, "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": "Add and assign MTD apps to Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-security/mobile-threat-defense/assign-apps" } } ] } }