Aadarsh

If you're into tech, let’s connect 🤝

Opened X to check one notification. Somehow I now know everything about AI drama and nothing about the task I was supposed to finish.

☁️ Azure Learning Series | Day 13 of 20 📘 Topic: Azure portal The Azure portal is more than just a place to create Virtual Machines or Storage Accounts. It is a web-based management console for working with your entire Azure environment. Here are some useful areas to understand: 🔹 Home: Access recently used resources, shortcuts and common services. 🔹 Global Search: Quickly find resources, services and documentation. 🔹 All Services: Browse the available Azure services. 🔹 Resource Groups: Open a resource group and manage the resources inside it. 🔹 Dashboards: Build a customized view of important resources and operational information. 🔹 Cloud Shell: Access Azure CLI and PowerShell directly from the portal. One important thing for cloud engineers: Before troubleshooting a missing resource, check your active Microsoft Entra directory and subscription filters. A resource may simply be hidden by the current portal filter, rather than deleted or unavailable. You can also customize Favorites, filters and dashboard views to make daily Azure operations easier. Practical tip: Always verify the active directory, subscription and resource group before making production changes.

AI skills or job security? AI skills, Job security follows my brother.... 😭

🔒 Azure Learning Series | Day 12 of 20 Topic: Azure Resource Locks Imagine someone accidentally deletes your production Storage Account or an important resource group. Azure Resource Locks help prevent these mistakes by adding an extra protection layer to your infrastructure. There are two main types: 🔹 CanNotDelete (Delete lock) Users can view and modify the resource, but cannot delete it until the lock is removed. 🔹 ReadOnly (Read-only lock) Users can view the resource, but cannot modify or delete it. It behaves similarly to the Reader role for management operations. Where can you apply locks? You can apply them at: • Subscription level • Resource group level • Individual resource level Locks are inherited by child resources. The most restrictive lock in the inheritance chain takes precedence. Real-world example: Apply a CanNotDelete lock to rg-prod. Every resource inside that resource group inherits the protection. Even an attempt to delete the entire resource group is blocked while the child lock remains. Important things to remember: Locks override normal user permissions. They protect Azure control-plane operations, not data-plane operations. A ReadOnly lock can affect operational tasks such as starting or restarting a VM. Locks do not replace backups or disaster recovery. Best practice: Use CanNotDelete for important production resources where accidental deletion is a concern. Apply ReadOnly only when you understand its operational impact. Azure Resource Locks are simple to configure, but they can prevent some very costly mistakes.

Some of the best automations are also the least impressive ones. A small PowerShell script, a scheduled report, an alert or a simple runbook that saves you from repeating the same task every day. No big platform. No fancy dashboard. What is one small automation you built that you would never want to do manually again? I want to steal some good ideas.

There is something interesting about farming that reminds me of working in tech. A farmer prepares the land, sows the seeds, takes care of the field and waits for the harvest. In tech, we do something similar. We plan, build, deploy, monitor and improve. Nobody gets results just by planting seeds, and nobody builds a reliable system just by writing code. The real work is in what happens after the beginning. 🌱🚜 Different fields, same lesson.

One prompt can now start a coordinated team of AI agents. Google announced Gemini 4 Carbon and previewed its /swarm feature in Antigravity. Interesting, but here is what matters to me: Can those agents coordinate properly, verify each other's work and explain the final result? Running multiple agents is impressive. Getting reliable work out of them is the real challenge.

IT people, you get one chance to permanently delete ONE thing from your work life. What are you removing? For me, it is meetings that could have been a 3-line message. No more "quick calls" that somehow take 45 minutes. 😭 Your turn. 👇

Hot take: Knowing 15 cloud services is less valuable than knowing how to troubleshoot 3 of them properly. Anyone can follow a tutorial and deploy a resource. But when authentication fails, permissions break, networking stops working or production goes down, real understanding matters. Building is easy to demonstrate. Troubleshooting is where experience shows.

☁️ Azure Learning Series | Day 11 of 20 📘 Topic: Azure Tags Managing hundreds of Azure resources becomes difficult when you cannot identify their ownership, purpose or cost. This is where Azure Tags become useful. What are Azure Tags? Tags are key-value pairs that add business context to your Azure resources. For example, imagine your team manages a production web application. You can assign tags like: 🔹 Environment = Production 🔹 Application = WebPortal 🔹 Owner = DataEngineering 🔹 CostCenter = CC1042 🔹 BusinessUnit = Finance Why do they matter? Tags help Azure teams: • Identify resource ownership and responsibility. • Group and analyze cloud spending. • Separate Dev, Test and Production workloads. • Find resources belonging to old projects. • Support audits and governance. Where can you apply tags? You can apply tags to supported Azure resources, resource groups and subscriptions. One important thing to remember: Tags do not automatically inherit from a resource group or subscription to its child resources. Azure Policy can help enforce tagging standards and add missing tags. Cost Management also offers tag inheritance for cost records, which is different from modifying the actual resource tags. Best practice: Establish a consistent tagging standard across your organization and never store passwords, access keys or secrets in tags. Tags may look like simple labels, but they play an important role in Azure governance and cost management.

hardest part of working in tech is sometimes learning after work. you spend the whole day troubleshooting, attending meetings, fixing issues and switching between tasks. then your learning platform reminds you that you have 4 unfinished courses. even my brain needs a maintenance window. 😭

Good morning from the fields 🌞 🚜🐄🌾