For the last ten years, one of the most popular Integrations in the market has been for organisations that have deployed Microsoft System Center to manage their infrastructure, who also use ServiceNow as their corporate Service Desk. The need to integrate Microsoft System Center was originally driven by the need to automate the generation of ServiceNow tickets from events in System Center Operations Manager.
As Microsoft Azure continues to be developed and more automation options become available; Azure Automation, Logic Apps, ARM (Azure Resource Manager) and Azure Function Apps to name a few. The question is quickly turning from ‘how do I automate with Azure?’ to ‘what automation type do I use in Azure?’. Across our next few blogs, we will seek to delve into the options available and look to define how they stack up against Azure Automation.
Automation and it’s use of the term Runbooks can be confusing and difficult to understand, especially when first starting out. We’ve put together some frequently asked questions and answers to help beginners get started.
Most automation approaches start in the same place; coding. For years, IT professionals have relied on scripts or series of scripts to perform tasks and then link them to provide an ‘automation. No-code or low-code reduces complexity and resource overhead, allowing both non-technical and technical users to automate processes through graphical user interfaces (GUI). In most cases, this involves drag-and-drop boxes that imitate a user’s interactions in a process.
Kelverion have put together this Azure Automation Best Practices Guide to support the creation of automation process in Azure Automation. Our consultants work with Azure Automation every day and have substantial experience with Azure Automation and IT automation built using other tools. It’s important to recognize that these are recommendations rather than hard and fast rules.
Kelverion have released a new version of our Integration Pack for Microsoft Azure Active Directory. This new release is a complete rewrite of our Integration Pack because Microsoft have depreciated the underlying API we have been using. This means this release is a breaking update, any Runbooks built against an earlier version of the Integration Pack may cease to operate when you upgrade to this new version.
Kelverion Runbook Studio V5.0 makes it even easier for organizations to automate IT service desk requests and reduce IT burden. In its fifth iteration, The Runbook Studio has undergone a significant design overhaul. The Studio’s technical capabilities have always been exceptional and now it has a user interface to match. On top of that, this version takes Kelverion’s low code/no-code design environment to the next level.
Microsoft announced the release of System Center 2022 on 1st April. The updated Microsoft System Center Orchestrator product information can be found here. The release brings significant improvements to the System Center suite, including an important update to Orchestrator, which is now a 64-bit application. This new functionality enables Orchestrator to work seamlessly with 64-bit PowerShell within code activities, a revision that has been sort-after by the user base.
All too often, the Kelverion team hear that businesses are trying to deliver more services with less resource, all whilst meeting tight Service Level Agreements. There are many automation use cases to relieve this pressure, and this article explores the six use case examples driving automation adoption within service management.
The planning of an IT automation project is crucial to success, this article takes a deep dive into areas which should be considered and addressed before embarking on an automation journey. Securing executive sponsorship and establishing governance Having the support and guidance from a senior leader within your organisation will undoubtedly benefit the delivery of your project. Implementing automation is change, and as with any change; has the potential for resistance.
