<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Governance on Thomy Gölles</title><link>https://thomygoelles.com/tags/governance/</link><description>Recent content in Governance on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Feb 2026 10:30:00 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Between Frontier Ambition and Reality: What 'Agent Ready' Really Means</title><link>https://thomygoelles.com/agent-ready-really-means/</link><pubDate>Tue, 17 Feb 2026 10:30:00 +0000</pubDate><guid>https://thomygoelles.com/agent-ready-really-means/</guid><description>&lt;p&gt;Microsoft defined six pillars that a company needs to deal with AI Agents a few weeks ago. Governance, Scaling, Adoption and so on.&lt;/p&gt;
&lt;p&gt;What I find exciting is that Microsoft itself says most companies are only at the beginning. Not because they&amp;rsquo;re lagging behind, but because &amp;ldquo;Agent Ready&amp;rdquo; means more than just starting an agent.&lt;/p&gt;
&lt;h2 id="the-responsibility-question"&gt;The Responsibility Question&lt;/h2&gt;
&lt;p&gt;What occupies me most is not (only) the technology, but who in the company actually bears the responsibility for it.&lt;/p&gt;</description></item><item><title>Zwischen Frontier-Ambition und Realität: Was 'Agent Ready' wirklich bedeutet</title><link>https://thomygoelles.com/deutsch/agent-ready-wirklich-bedeuten/</link><pubDate>Tue, 17 Feb 2026 10:30:00 +0000</pubDate><guid>https://thomygoelles.com/deutsch/agent-ready-wirklich-bedeuten/</guid><description>&lt;p&gt;Microsoft hat vor ein paar Wochen sechs Säulen definiert, die ein Unternehmen braucht, um mit AI Agents umzugehen. Governance, Skalierung, Adoption und so weiter.&lt;/p&gt;
&lt;p&gt;Was ich spannend finde ist, dass Microsoft selbst sagt, die meisten Unternehmen stehen erst am Anfang. Nicht weil sie hinterherhinken, sondern weil &amp;ldquo;Agent Ready&amp;rdquo; halt mehr bedeutet als einfach mal einen Agent zu starten.&lt;/p&gt;
&lt;h2 id="die-verantwortungsfrage"&gt;Die Verantwortungsfrage&lt;/h2&gt;
&lt;p&gt;Was mich dabei am meisten beschäftigt ist gar nicht (nur) die Technik, sondern wer im Unternehmen eigentlich die Verantwortung dafür trägt.&lt;/p&gt;</description></item><item><title>List app usage in Microsoft Teams</title><link>https://thomygoelles.com/list-teams-app-usage/</link><pubDate>Sat, 06 Jun 2020 09:51:29 +0000</pubDate><guid>https://thomygoelles.com/list-teams-app-usage/</guid><description>&lt;p&gt;A couple of weeks ago I saw a thread in the interwebs where someone asked about information on Teams app usage. The question was what apps are used in which teams. I knew from experience with the &lt;a href="https://pnp.github.io/office365-cli/" target="_blank" rel="noopener"&gt;Office365 CLI&lt;/a&gt; and the Teams commands there, that this should be possible to accomplish with the existing commands. So here we go.&lt;/p&gt;
&lt;h2 id="listallteamsappsps1"&gt;ListAllTeamsApps.ps1&lt;/h2&gt;
&lt;p&gt;The first tiny script just iterates through all your teams and lists all apps in each team. Remember: the command will list only those teams you have access to. You can start this with your personal account, but to get all teams you will need an admin account to run those lines.&lt;/p&gt;</description></item><item><title>Microsoft Forms and Flow for Teams channel governance</title><link>https://thomygoelles.com/microsoft-forms-and-flow-for-teams-channel-governance/</link><pubDate>Sat, 08 Dec 2018 22:27:46 +0000</pubDate><guid>https://thomygoelles.com/microsoft-forms-and-flow-for-teams-channel-governance/</guid><description>&lt;p&gt;Inspired by a tweet from fellow MVP Melissa Hubbard (&lt;a href="https://melihubb.com/" target="_blank" rel="noopener"&gt;https://melihubb.com/&lt;/a&gt;) this blog post introduces the idea of a Mircosoft Forms form combined with a flow to govern channel creation in Teams. Governance in Microsoft Teams is important for adoption and ease of use.&lt;a href="https://melihubb.com/2018/04/04/microsoft-teams-governance-how-to-create-a-channel-request-solution-using-flow/" target="_blank" rel="noopener"&gt;Melissa&amp;rsquo;s approach&lt;/a&gt; to the same problem is to use a SharePoint list for storing the information but I wanted to try it just with Microsoft Forms.&lt;/p&gt;
&lt;h4 id="why-should-we-use-governance"&gt;Why should we use governance?&lt;/h4&gt;
&lt;p&gt;The overall idea is to turn off self-service channel creation in Teams. Teams can get messy if there are too many channels. That&amp;rsquo;s why for some teams it&amp;rsquo;s better only to allow the owners of the team to create new channels. In your Teams settings, you have the option to define what members are allowed to do. In our scenario, we disallow the creation of new channels.&lt;/p&gt;</description></item></channel></rss>