<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Series on DR.365</title><link>https://blog.dr365.io/series/</link><description>Recent content in Series on DR.365</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Thu, 29 Oct 2026 07:00:00 +0100</lastBuildDate><atom:link href="https://blog.dr365.io/series/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent governance in Microsoft 365</title><link>https://blog.dr365.io/series/agent-governance-in-microsoft-365/</link><pubDate>Thu, 29 Oct 2026 07:00:00 +0100</pubDate><guid>https://blog.dr365.io/series/agent-governance-in-microsoft-365/</guid><description>&lt;p&gt;Agents in Microsoft 365 are built with three tools: Agent Builder, Copilot Studio and Foundry. Microsoft distinguishes three models of who carries the risk: the platform, the administrator or the organization. That distinction runs through all four parts of this series.&lt;/p&gt;
&lt;p&gt;I write from the seat of an operator in regulated environments (critical infrastructure, NIS2), usually with several tenants and an IT service provider. So each part also asks a question Microsoft does not: how is responsibility split between customer and service provider?&lt;/p&gt;
&lt;p&gt;&lt;img alt="The four parts of the series along risk ownership: part 1 introduces the three models, part 2 shows the lifecycle per model, part 3 how responsibility shifts at runtime, part 4 the evidence" class="gallery-image" data-flex-basis="526px" data-flex-grow="219" height="730" loading="lazy" sizes="(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px" src="https://blog.dr365.io/series/agent-governance-in-microsoft-365/series-map-en.png" srcset="https://blog.dr365.io/series/agent-governance-in-microsoft-365/series-map-en_hu_953911deaa907acb.png 800w, https://blog.dr365.io/series/agent-governance-in-microsoft-365/series-map-en.png 1600w" width="1600"&gt;&lt;/p&gt;</description></item></channel></rss>