Posts

Hi! Today, I’d like to share a helpful tip on how you can efficiently manage your Azure resources and services while keeping your cloud spending in check. With Azure Budgets, you can easily set budget thresholds and receive alerts to monitor your costs proactively.

The use of Infrastructure as Code (IaC) has become vital in achieving successful and scalable implementations. Azure Bicep allows us to provision and manage resources in Azure with reliability and conciseness.

Hey, did you know that Azure Monitor has these cool things called action groups? They help you manage alerts by connecting them to different actions. You can receive notifications by email or text message, run Azure Functions, or even start a webhook with an HTTP call.

Hi all! Today I want to talk to you about “Policy as Code” Just as “Infrastructure as Code” changed how we handle infrastructure deployment, “Policy as Code” gives us consistency, traceability, and rapid implementation in policy management.

Hi everyone! Today I want to share how I use Terraform to implement your private DNS zones in Azure. Also, I’ll show you how to create ‘A’ records in these zones.

Managing your resources and services costs is crucial to your Azure subscriptions’ governance. That’s where Azure Budgets comes in. Azure Budgets helps us manage our cloud costs by setting spending limits.

In this blog post, I want to show you how to implement a hub-spoke network architecture on Azure using Terraform, one of my favorite infrastructure as code (IaC) tools. The hub-spoke model is a widely adopted networking strategy that allows you to simplify management, increase scalability, and improve the security of your Azure resources.

Azure Storage is a core foundational PaaS (Platform as a Service) offering within Microsoft Azure, providing a versatile and scalable solution for storing files, blobs (binary large objects), and other data types.

When you start using Terraform to manage your cloud infrastructure, a key consideration is where to store the state file that Terraform generates to track changes to your infrastructure. While storing this file locally on your machine is possible, a more scalable and secure approach is to store it in a centralized location that your entire team can access.

As administrators of an Azure subscription, we are always interested in monitoring what is happening in our environment. To do this, Azure gives us a way to do this through activity logs, which record the actions that are performed on our subscription.

We continue with the series of articles on private endpoints. Today I want to show you how to create a private endpoint to privately and securely connect to an Azure file share using Azure PowerShell.

I recently migrated an Azure subscription to a new tenant, and in the key vault resources, I had to perform a few additional steps that I want to show you. So In this week’s article, we’ll look at updating the tenant ID and removing previous access policies and role assignments to the key vault resource once it’s moved to the new subscription.

If you need to perform a quick ad-hoc backup of your virtual machine before maintenance that allows you to take consistent snapshots of all managed disks attached to your virtual machine, you should try Azure restore points.

Hi everyone, and happy new year. In the first post of the year, I want to continue talking about Private Endpoints. In this post, I want to show you how to create a private endpoint to connect securely to an Azure Key Vault, and I’ll also show you how to use two features that Microsoft recently enabled support for Private Endpoint Static IP Configurations and support for customizing the name of the network interface assigned to the private Endpoint.

I think that Private Endpoint is one of the trends that we should focus on and learn more about. For this reason, in the coming months I will publish more content about this simple but powerful technology.

Microsoft last month announced the general availability of a new experience for managing Azure Log Analytics table metadata from the Azure portal. So I think it’s an excellent time to see how to view and edit table properties in Log Analytics workspaces using the Azure CLI and check how these changes are reflected in the Azure portal.

Following the thread of my last post, I want to show you how to take advantage of this functionality by configuring a data lifecycle management policy in your Azure storage account using Azure PowerShell.

In my last article, I showed you how to enable access time tracking on the Azure Storage Blob service. Today I want to show you how to take advantage of this functionality by setting up a data lifecycle management policy in your Azure storage account using Azure CLI.

To manage storage costs, it can help to organize your data based on how often it will be accessed. Azure offers us different levels of access to store blob data most cost-effectively, depending on how we use it.

Blob storage now supports SSH File Transfer Protocol (SFTP). This allows us to use SFTP for file access, transfer, and management. In this post, I will show you how to enable an SFTP endpoint for your blob storage account and configure local user identities to authenticate and connect your storage account with SFTP over port 22.