<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Admin on Thomy Gölles</title><link>https://thomygoelles.com/tags/admin/</link><description>Recent content in Admin on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 06 Jun 2020 09:51:29 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/admin/index.xml" rel="self" type="application/rss+xml"/><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>Microsoft365DSC remote name could not be resolved lyncdiscover</title><link>https://thomygoelles.com/microsoft365dsc-remote-name-could-not-be-resolved-lyncdiscover/</link><pubDate>Mon, 11 May 2020 15:29:37 +0000</pubDate><guid>https://thomygoelles.com/microsoft365dsc-remote-name-could-not-be-resolved-lyncdiscover/</guid><description>&lt;p&gt;A couple of days ago I stumbled upon a LinkedIn post/article by &lt;a href="https://twitter.com/NikCharlebois" target="_blank" rel="noopener"&gt;Nik Charlebois&lt;/a&gt; about the &lt;a href="http://microsoft365dsc.com/" target="_blank" rel="noopener"&gt;Microsoft365DSC&lt;/a&gt; project. The first sentence on Github already sold the idea to me &amp;ldquo;This module allows organizations to automate the deployment, configuration, and monitoring of Microsoft 365 Tenants via PowerShell Desired State Configuration.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;After starting to playing with it a little I came across a nasty error that took me some time to resolve. To prevent others from also losing valuable time I thought it might be a good idea to document the steps.&lt;/p&gt;</description></item></channel></rss>