Real world business tracks leading towards Azure Services
Join me for the final article in the min-series on Enhancing Microsoft Sentinel. Today, we review ongoing optimizations and how to stay ahead of emerging threats.
Join me for Part 2 of 3 where we review advanced customizations in Microsoft Sentinel. We review some of the steps to advance your threat hunting and better protect your environment.
Join me for Part 1 of 3 where we review Building a Stronger Foundation in Microsoft Sentinel. We review the steps to help review and build a stronger SIEM solution together.
Today, we will explore some enhancements to your Microsoft Sentinel environment. I look at optimizing the ticket queue and working to prevent ticket overload. Join me to explore Automation Rules.
Today, we explore creating custom Automation Rules in Microsoft Sentinel to help us auto-close low value incidents. Let’s look at how we can automatically close & impact incidents and make it all work using PowerShell!
Today, we expand on and explore rapid Microsoft Sentinel deployment using PowerShell. This model of repeatable, consistent, and fast deployments is a great way to help build our own skills up, and build a resilient and robust deployment method we can count on.
Last time we looked at some different ways of getting started with managing your Azure resources. Today I’d like to introduce you a little bit to Azure Automation – this time for saving money in shutting down unused resources – and also starting them on a schedule. Last article we created a demo resource group called…
Let’s take a look at adding Runbook to our Azure Automation account that we created in our last article together. Today, we’ll add a simple script as a runbook and see how to get it running in a simple way.
Today we’re going to get ready to create some automation in Azure together. The end goal is to get ready to set some PowerShell scripting to follow a schedule and run entirely in Azure. We’ll start with the basics first and go from there. Let’s dive right in and get things started to run with an Azure Automation account first.
If you are running Azure infrastructure and have multiple providers that reach into your tenant, you know how difficult it is to log, audit, and monitor what your providers are actually changing inside your subscriptions. From the opposite view, if you’re a solution provider and you have to reach into multiple clients Azure subscriptions to complete your work, you know how challenging it is to keep everything segregated and organized. Never-mind if you need to pull auditing logs to show what changes you completed inside a specific subscription.Azure Lighthouse provides…
