Azure Insights: Data workflows; Resource locks; Azure Monitor for Containers; Active Directory security events; ADFS

July 8 2019

Azure pros share their thoughts on working with data workflows, the power of resource locks, managing Azure Monitor for Containers and more.

Looking into data workflows

Karim Vaes discussed how to work with data workflows in Azure. Data is first ingested with a REST API or AzCopy, from an offline source such as Azure DataBox or from an online DataBox Edge Gateway. It is staged and processed before passing on to other systems. Azure Data Factory's strength is its ability to do no or low-code modelling, while Azure Functions links business logic into workflows. Cosmos DB stores metadata while data encryption is enabled with Azure Key Vault. Other valuable elements of the Azure offering for data workflows include DevOps, Batch, Data Bricks, Log Analytics and Application Insights. Vaes shared an in-depth overview of how to go through the entire process.

Using Azure resource locks

Gregor Suttie, writing on Azure Greg, indicated that Azure resource locks play an important role in production resources from being deleted. "Azure resource locks will at some point save your bacon…trust me," he wrote.  Although widely known, resource locks tend to be rarely used. Users can apply them at the level of resource groups down to the more granular level of individual resources. Locks are easy to apply by clicking on the locks option listed for a resource.

Locks take two forms. Read-only allows users to access a resource but not delete or change it, while delete lets users edit a resource but not delete it. All resources within the same scope inherit locks from a parent. Suttie wrote:

The most restrictive lock in the inheritance takes precedence. Unlike role-based access control, you use management locks to apply a restriction across all users and roles.

Changing Azure Monitor for Containers data collection

About MSDW Editorial Team

More about MSDW Editorial Team