A general guidelines in naming your Azure resources

In the past few years, the work/life paradigm has been blurred. We no longer the work and home separation, go to work, come back home and that is it.

We continue with our post on Azure CLI and JMESPath.

The Azure CLI command outputs a JSON. Even when an output format other than JSON is specified, CLI command results are first treated as JSON to enable queries to be performed, before outputted into the format specified. We can use the –query argument to execute a JMESPath query on the results of commands.

Protecting your infrastructure and data when you work in the cloud cannot be over emphasized. Every system, architecture, and application need to be designed with security in mind.

Follow this procedure to set up your environment to work with Azure functions in Visual Studio Code

Use resource locks to prevent resources from inadvertently being deleted or modified.

In the previous two posts in this series, we examined how resource grouping and tagging can help you organise your resources, but how do you ensure that new resources follow the rules? We can use the Azure Policy. It is a service you use to create, manage and assign policies.

Tags are helpful as you look to improve organization of your Azure resources. Tags allow us to associate custom details about our resource, in addition to the standard Azure properties.

As a financial institution operating many ATMs across the country and across continents, how can you use Office 365 to gain insights into external problems affecting your ATMs. I am not talking about internal issues such as ATMs running low on cash, but environmental problems such as vandalism, broken screens and dirty surroundings.