<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>BYOD on Phillip Büchler</title><link>https://fime.ch/tags/byod/</link><description>Recent content in BYOD on Phillip Büchler</description><generator>Hugo</generator><language>en</language><copyright>&amp;copy; Est. 1979 · Retention policy: digital eternity · &lt;a href="https://fime.ch/"&gt;Fime&lt;/a&gt;</copyright><lastBuildDate>Fri, 20 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://fime.ch/tags/byod/index.xml" rel="self" type="application/rss+xml"/><item><title>BYOD on iOS and Android with Intune</title><link>https://fime.ch/architecture/byod-mobile-intune/</link><pubDate>Fri, 20 Nov 2026 00:00:00 +0000</pubDate><guid>https://fime.ch/architecture/byod-mobile-intune/</guid><description>&lt;p&gt;Two solution views of the same goal: employees use work apps on their own phones, work data stays in managed apps, and only compliant devices get access. One view shows iOS with account-driven User Enrolment, the other Android with the personally owned work profile. Both use Microsoft Intune and Entra ID.&lt;/p&gt;
&lt;p&gt;From the business layer up, the two views are the same. They only differ below that, and most of the differences are about who you depend on, not which settings you have. On iOS, enrolment needs a service discovery file on the domain your users sign in to, so whoever runs that web server is part of your device management.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; On Android, Intune is moving the work profile to Google&amp;rsquo;s Android Management API, so every policy passes through Google before a hidden Android Device Policy app enforces it on the phone.&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description></item></channel></rss>