Since the beginning of the year Microsoft has been making numerous changes to updates both before and after patch Tuesday. With all of the changes to patches its hard to know when those changes are made unless you are watching the results from WSUS. In the past we had RSS feeds from Microsoft in easy locations to find we could subscribe to and learn when Microsoft made a change to patches. All of that changed when we made the shift to cumulative updates.
After the most recent debacle where a servicing stack update was released out of band I decided I needed to do some research on how I could get information in a faster and more consumable modern manner. I also wanted to do this using some of the new tools available for modern automation and management. In order to accomplish what I did you’ll need a little patience, and appropriate licensing for Teams and Flow.
The first step is to generate your own RSS feed for the products you are interested in. In my case, I did Windows 10 and Server 2016 as they seem to change the most. You can generate them using the link below to select your Product ID.
You then select your product ID and generate a new RSS feed link. You’ll need this for building the flow.
Next you’ll need to log into your O365 portal and select ‘Flow’
This will take you into the ‘Flow’ workspace if you’ve never used Flow before it can be a little intimidating with how many options and possibilities there are but we can keep it pretty simple for what we need to accomplish. For what we are going to do we are going to select ‘Create from Blank’ – note you can create this from teh RSS -> Teams template card as well however that won’t give you the opportunity to learn to add new steps in the process.
Flow will then ask if you want to ‘Create flow from blank’ or if you want start with one of these popular triggers. Nine times out of ten the trigger ‘When a feed item is published’ is available if its not that’s OK we can just click ‘Create from blank’ anyways and find the trigger ourselves.
For this example go ahead and click ‘Create from blank’ and int he search bar type ‘RSS’ this will bring up the available trigger action ‘RSS – When a feed item is published’.
Notice next to the ‘Triggers’ section there is also an ‘Actions’ section. There is only one ‘action’ for the RSS connector however other connectors have more actions such as Teams, Sharepoint and more. Once you select the trigger for your flow, you’ll have an option to paste the RSS feed URL into a box and add a new step.
In this case we just want an action not a condition. This will open up the search pannel for options with all of the available connectors. A simple search using the keyword ‘Teams’ will return all of the available options for the teams connector we want to choose the option ‘Microsoft Teams – Post Message’ this will then allow us to start filling in the information that we want to be sent into the teams message for our example we want something like the following.
You need to select the team you want to send the message to, you obviously have to have rights to message with that team all teams you are a member of should dynamically be in the drop down list. You’ll then want to select the ‘Channel ID’ you want to send the message this will also auto-populate once you select the ‘Team Id’. You’ll then be able to fill in the message body. From this you’ll want to use the ‘Dynamic content’ option and you can put in some information as shown above and using the search box select the options that I’ve put in the box here you don’t have to use those ones but I suggest at least ‘Feed Title’, ‘Feed Summary’ and ‘Primary Feed Link’.
Once this is completed you’re done! Just hit save and you’ll be all set! The next time Microsoft releases an update to anything in the Windows 10 space even if its just a simple meta date update you’ll get a message in teams and a link to the support article that explains what they changed.
Jordan has been working in the Industry since 2009. Since starting he’s worked with Active Directory, Group Policy, SCCM, SCOM and PowerShell. Jordan currently works in the healthcare industry as an SCCM Infrastructure Team lead supporting over 150,000 endpoints. Most recently his focus has been in SQL Reporting for SCCM, creation of PowerShell scripts to automate tasks and PowerBI.