Azure Managed Identities

Overview Azure Storage automatically encrypts all data at rest using Storage Service Encryption (SSE). When you specify a customer-managed key (CMK), that key is not used to encrypt the data, it is used to protect and control access to the key that encrypts the data.

Hi everyone! Today, in this blog post, we’ll explore how to deploy Azure Chaos Studio using Terraform. As you may know, Azure Chaos Studio is a powerful service that lets us safely test our infrastructure by simulating real-world failures.

In my previous article, we explored how to set up server-level Transparent Data Encryption (TDE) in Azure SQL. This method uses a single encryption key to secure multiple databases on a server or managed instance, providing consistent protection across all databases.

In Azure SQL, server-level Transparent Data Encryption (TDE) provides centralized encryption across multiple databases within a server or managed instance. By default, Azure SQL uses a Service Managed Key (SMK) for TDE, but we can also choose to deploy a Customer Managed Key (CMK) for better control.

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.

Today I want to show you how you can improve the security of your Linux virtual machines in Azure by integrating with Azure Active Directory (Azure AD) authentication. In this post, I’ll show you how to set up a Linux virtual machine and log in with Azure AD using openSSH certificate-based authentication.

Hi, In a previous post, I showed you how to enable system-assigned managed identity on an Azure virtual machine. Today, I want to show you how to assign a managed identity to access an Azure resource securely.

Hi, Jorge is back. In this post, I want to show you How to enable the system-assigned managed identity on an Azure VM using Powershell and Azure CLI. When you enable a system-assigned managed identity, Azure creates an identity associated with the instance and stores it to the Azure AD tenant associated with the subscription where you created the service instance.