Many of my customers have started utilizing the new capabilities of Visual Studio Online: Visual Studio Team Services to manage and deploy production Azure Resources. I have been recently tasked with deploying and maintaining PowerShell based Azure Functions in such an environment.
After some research on integrating Azure Functions with VSTS (and having a limited background in Azure App Services) I wasn’t finding any short and simple explanations/documentation on this process. I needed a mature automated (One Click) way to deploy Azure Functions from a VSTS Code Repository. I did not / could not, by project requirement resort to using “custom code” / manual processes, so I wanted to outline the steps I took to help speed up the process for those new to Azure Functions.
This example will take a handful of files and folders in a VSO:VSTS Git Repository and deploy an entire App Service / Function App with 3 Azure Functions using Out Of Box Build Activities. I am NOT focusing on the STEP BY STEP process, this merely functions as a solution example. There are MANY ways to accomplish this task, but I consider this a fully-functional and easy implementation of this process.
Recently I have been developing a number of “Hobby” IoT Solutions, and for me a quick start to this development was to use OMS as a Temporary Storage and Alerting Mechanism. Through this process (and suggestion by the great Tao Yang) I have taken the time to experiment with Azure functions to Retrieve Data from OMS, and to Inject Data into OMS.
For Readers, please know that following blog posts on Azure Functions from THE GREATS are required reading for this topic, and will get you up to speed with Azure Functions (Especially PowerShell + Azure Functions)
This blog post here skips some of the details and instead focuses on implementation and some of the results, this post mainly serves as an example of how awesome Azure Functions are and to highlight some of their capabilities.
I have recently been experimenting with some of the latest and greatest cloud / tech offerings from Amazon, and have recently put together two separate videos with some of my tests / proof of concepts / experiments.
One is specific to Alexa (Echo Dot) and the other is the Amazon Dash / AWS IoT Button. Both relate to Service Management with ServiceNow in their own way, enjoy!
I had a situation where I was having trouble REMOVING my Azure Automation Hybrid Runbook Worker. I could not successfully run the “Remove-HybridRunbookWorker” command as I did not the URL / Key Information.
I my instance, I had deleted my Azure Automation Account in Azure, even though I had a Hybrid Runbook Worker registered to that Account, I did not remove the hybrid runbook worker before I removed the Automation account.
This post will provide an option for resolving this situation:
Just a quick post for those of you who would like to remove the Sample SMA Runbooks.
When you stand up SMA you may have about 25+ Sample SMA runbooks present and they tend to clutter up the Windows Azure Pack Automation website. These samples are great, especially when you are getting started! But you may want to remove them just to clean up the interface once you have done some learning and testing.