<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft Forms on Thomy Gölles</title><link>https://thomygoelles.com/tags/microsoft-forms/</link><description>Recent content in Microsoft Forms on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 08 Dec 2018 22:27:46 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/microsoft-forms/index.xml" rel="self" type="application/rss+xml"/><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>