Posts

Terraform Variables

Image
Terraform variables act as placeholders to parameterize your infrastructure configurations, allowing you to use the same codebase across different environments (development, staging, production) without hardcoding values. They are essential for creating flexible, reusable, and maintainable Infrastructure as Code (IaC).  Declaring Variables Variables are declared using a variable block in a .tf file (conventionally in a separate variables.tf file). type: Specifies the type of data (e.g., string, number, bool, list, map, object, set, tuple). default: Makes the variable optional; this value is used if no other value is provided. description: Documents the purpose of the variable for users of the module. validation: Enforces custom rules on the variable's value, returning a custom error message if the condition is not met. sensitive: Marks the value as sensitive, preventing it from being shown in CLI output (though it is still stored in the state file). nullable : Controls whether ...

Understanding App Registration vs. Enterprise Application in Microsoft Entra ID

  In Microsoft Entra ID (formerly Azure Active Directory (AAD)) , both App registration and Enterprise application registration are essential components for configuring applications that interact with Azure services or other applications. They serve distinct purposes within the application setup process. App registration: Creates a globally unique application object, also known as an app registration. This object defines the core details of your application, such as its name and what it does. It also generates an application (client) ID used for identification. Think of it as the blueprint for your application. You perform app registration in the Azure portal under " App registrations ". Enterprise application registration (Service principal): Represents a specific instance of an application (created via app registration) within a particular  Microsoft Entra ID (formerly Azure Active Directory (AAD))  tenant (your organization's tenant). This creates a service p...

High Availability vs. Disaster Recovery in Cloud: Key Differences Explained

Image
What is the difference between HA & DR in Cloud?   Both High Availability (HA) and Disaster Recovery (DR) are important concepts in cloud computing that aim to keep your systems and data up and running. However, they address different scenarios and have distinct approaches. High Availability (HA) focuses on preventing downtime caused by isolated failures within the cloud system itself. This could include hardware malfunctions, software glitches, or network disruptions. HA achieves this by designing systems with redundancies, meaning there are backups in place to take over if a primary component fails. This can involve: Redundant servers: Having multiple servers running the same application, so if one fails, the others can pick up the load. Clustering: Grouping multiple servers so they act as a single unit. This allows for automatic failover to a healthy server if one goes down. Load balancing: Distributing traffic across multiple servers to prevent overloading any single se...

Extend the Life of Windows Server 2012/2012 R2 with Azure Arc and SCCM Integration

  Challenge: Maintaining security for Windows Server 2012/2012 R2 after end-of-support by deploying Extended Security Updates (ESUs). Leveraging existing SCCM infrastructure for update deployment while simplifying ESU management. Solution: This approach combines the strengths of SCCM and Azure Arc to achieve a streamlined ESU deployment process for on-premises Windows servers. SCCM: Trusted Patch Management: SCCM remains your familiar tool for deploying updates, including ESUs, to your Windows servers. SCCM integrates well with WSUS for efficient update distribution. Azure Arc: Centralized ESU Management: Onboard eligible Windows servers (2012 & 2012 R2) to Azure Arc. Important: Update Azure Arc agent to version 1.34 or later for ESU support. Purchase and manage ESU licenses directly through Azure Arc (optional, simplifies licensing). Assign ESU licenses to your Azure Arc-enabled servers for simplified tracking. Workflow: Azure Arc manages ESU licensing and assignment. SCCM...

Demystifying Azure Storage – Understanding Blobs, Queues, Tables, and Files

Image
The Azure Storage platform includes the following data services: Table – A NoSQL store for schema-less storage of structured data. Blob – A massively scalable object store for text and binary data. Queue – An asynchronous message queueing between application components. Files – Managed file shares for cloud or on-premises deployments. Azure Table Storage Azure Table Storage is a scalable, NoSQL, key-value data storage system that can be used to store large amounts of data in the cloud. This storage offering has a schema-less design, and each table has rows that are composed of key-value pairs. You can use Table storage to store and query huge sets of structured, non-relational data, and your tables will scale as demand increases. Azure Blob Storage Blob Storage is Microsoft Azure’s service for storing binary large objects or blobs which are typically composed of unstructured data such as text, images, and videos, along with their metadata. Blobs are stored in directo...