<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft365 on Nicola Suter</title><link>https://nicolasuter.ch/tags/microsoft365/</link><description>Recent content in Microsoft365 on Nicola Suter</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Nicola Suter</copyright><lastBuildDate>Mon, 10 Aug 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://nicolasuter.ch/tags/microsoft365/rss.xml" rel="self" type="application/rss+xml"/><item><title>Playing around with the Office 365 Service Communications API</title><link>https://nicolasuter.ch/microsoft365-service-status/</link><pubDate>Mon, 10 Aug 2020 00:00:00 +0000</pubDate><guid>https://nicolasuter.ch/microsoft365-service-status/</guid><description>&lt;p&gt;The Office 365 Service Communications API provides information about Microsoft 365 service status for your tenant including service messages. I built a little PowerShell module to access the API with PowerShell cmdlets. In this post I want to show you some examples which help you to use the API.&lt;/p&gt;

&lt;h2 class="relative group"&gt;PowerShell Module
 &lt;div id="powershell-module" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#powershell-module" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;I built a PowerShell module to access Microsoft 365 service status details natively with PowerShell. The PowerShell module and documentation is available on the &lt;a href="https://www.powershellgallery.com/packages/Microsoft365ServiceStatus" target="_blank" rel="noreferrer"&gt;PowerShell Gallery&lt;/a&gt; and on &lt;a href="https://github.com/nicolonsky/Microsoft365ServiceStatus" target="_blank" rel="noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Before using the module an app registration is required. Setup instructions are also provided on GitHub.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://user-images.githubusercontent.com/32899754/89341042-fe6eb100-d6a0-11ea-80a7-e7357f9717c5.gif" target="_blank" rel="noreferrer"&gt;&lt;figure&gt;&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 alt="Module"
 src="https://user-images.githubusercontent.com/32899754/89341042-fe6eb100-d6a0-11ea-80a7-e7357f9717c5.gif"
 &gt;&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;

&lt;h3 class="relative group"&gt;CI/CD
 &lt;div id="cicd" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#cicd" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h3&gt;
&lt;p&gt;By leveraging Azure DevOps I created a build and release pipeline which automatically builds the PowerShell module with Plaster.&lt;/p&gt;
&lt;p&gt;Builds are only created if the commit on GitHub includes a version tag. This version tag gets automatically populated to the module manifest.&lt;/p&gt;
&lt;p&gt;The build artifact gets then automatically published to the PowerShell Gallery as a new version. Furthermore, a new GitHub release including the module artifact is added to the project.&lt;/p&gt;
&lt;p&gt;This process fully automates the publishing and build process for the module. For local development and maintenance, the module can also be built with &lt;a href="https://github.com/nightroman/Invoke-Build" target="_blank" rel="noreferrer"&gt;&lt;code&gt;Invoke-Build&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>