<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Service Manager - Tag - GoToGuy Blog</title><link>https://gotoguy.blog/tags/service-manager/</link><description>Service Manager - Tag - GoToGuy Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 08 Dec 2015 00:03:31 +0000</lastBuildDate><atom:link href="https://gotoguy.blog/tags/service-manager/" rel="self" type="application/rss+xml"/><item><title>Creating SCSM Incidents from OMS Alerts using Azure Automation – Part 1</title><link>https://gotoguy.blog/2015/12/08/creating-scsm-incidents-from-oms-alerts-using-azure-automation-part-1/</link><pubDate>Tue, 08 Dec 2015 00:03:31 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2015/12/08/creating-scsm-incidents-from-oms-alerts-using-azure-automation-part-1/</guid><description>There has been some great announcements recently for OMS Alerts in Public Preview (http://blogs.technet.com/b/momteam/archive/2015/12/02/announcing-the-oms-alerting-public-preview.aspx ) and Webhooks support for Hybrid Worker Runbooks (https://azure.microsoft.com/en-us/updates/hybrid-worker-runbooks-support-webhooks/ ). This opens up for some scenarios I have been thinking about. This 2-part blog will show how you can create a new Service Manager Incident from an Azure Automation Runbook using a Hybrid Worker Group, and with OMS Alerts search for a condition and generate an alert which triggers this Azure Automation Runbook for creating an Incident in Service Manager via a Webhook and some contextual data for the Alert.</description></item></channel></rss>