<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ArchiMate on Phillip Büchler</title><link>https://fime.ch/tags/archimate/</link><description>Recent content in ArchiMate 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>Sat, 21 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://fime.ch/tags/archimate/index.xml" rel="self" type="application/rss+xml"/><item><title>Third-party patching: who holds the connector credential</title><link>https://fime.ch/architecture/patching-trust-chain/</link><pubDate>Sat, 21 Nov 2026 00:00:00 +0000</pubDate><guid>https://fime.ch/architecture/patching-trust-chain/</guid><description>&lt;p&gt;A patching tool that publishes Win32 apps to Intune can run code as SYSTEM on every managed device. That makes its connector a tier-0 asset. This view shows the two ways the connector can reach your tenant, and which of your controls reach each one.&lt;/p&gt;
&lt;p&gt;Both paths end at the same Graph permission, &lt;code&gt;DeviceManagementApps.ReadWrite.All&lt;/code&gt;, so they look identical on a permission list. The difference is who holds the credential. A vendor&amp;rsquo;s multi-tenant app keeps it in the vendor&amp;rsquo;s cloud. A self-hosted publisher with your own app registration keeps it on a server you run. Only the second can be fenced with Conditional Access for workload identities.&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;&lt;/p&gt;</description></item><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><item><title>Microsoft 365 Copilot governance: capability map</title><link>https://fime.ch/architecture/copilot-governance/</link><pubDate>Fri, 20 Nov 2026 00:00:00 +0000</pubDate><guid>https://fime.ch/architecture/copilot-governance/</guid><description>&lt;p&gt;Copilot runs in the user&amp;rsquo;s security context. It creates no new access, it removes the friction that used to hide oversharing. So every control in this view narrows what permissions already allow, and none of it repairs broken permissions. That&amp;rsquo;s why oversharing control comes first.&lt;/p&gt;
&lt;p&gt;The view groups what Copilot governance needs into four capability groups: oversharing control, information protection, Copilot and agent control, and AI oversight and compliance. Each capability is realised by a Microsoft product, mostly Purview, plus SharePoint Advanced Management, the Microsoft 365 admin center, Agent 365, the Power Platform admin center and Entra ID.&lt;/p&gt;</description></item><item><title>Purview DLP for Microsoft 365 Copilot: what it enforces</title><link>https://fime.ch/architecture/copilot-dlp/</link><pubDate>Fri, 20 Nov 2026 00:00:00 +0000</pubDate><guid>https://fime.ch/architecture/copilot-dlp/</guid><description>&lt;p&gt;DLP for Copilot is the last-mile control. It stops Copilot from using certain content, but it only works on top of permissions that are already right. Most of the governance work sits elsewhere, see the &lt;a href="https://fime.ch/architecture/copilot-governance/"&gt;capability map&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This view shows the one policy location for Microsoft 365 Copilot, Copilot Chat and Cowork, what it enforces, and where it stops. It&amp;rsquo;s a product view as of November 2026, and two of its four actions are in preview, so it will go out of date quickly.&lt;/p&gt;</description></item></channel></rss>