<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft365DSC on Thomy Gölles</title><link>https://thomygoelles.com/tags/microsoft365dsc/</link><description>Recent content in Microsoft365DSC on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 11 May 2020 15:29:37 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/microsoft365dsc/index.xml" rel="self" type="application/rss+xml"/><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>