Posts

OAuth 2.0 Explained (Useful for SC-300, AZ-400 ,AZ-500)

Image
(Open image in a new tab for clarity) Welcome to our deep dive into the world of OAuth and secure user authentication! Today, we're unpacking the process step-by-step, using the popular travel planning platform TravelBuddy and its integration with Google's authentication services as our example. What is OAuth? OAuth is an open-standard authorization protocol or framework that describes how unrelated servers and services can safely allow authenticated access to their assets without actually sharing the initial, related, single logon credential. In simpler terms, it lets you use one service's login for other services without handing out your password. The TravelBuddy-Google OAuth Flow Our journey begins when you decide to use your Google credentials to log into TravelBuddy. But what does that process actually look like? Here’s a visual guide. One-Time Setup Process Before anything else, TravelBuddy needs to set up a one-time communication channel

A mind map for azure virtual machine (helpful for AZ-104 , AZ-305)

Image
Mind Map shows various features of azure virtual machine and their relationship.(please download image for more clarity)

OSI Model

Image
Networking Layers Understanding Networking Layers Layer 1: Physical Layer Metaphor: The Roads Role: Provides the physical path (like roads or pathways) for the delivery vans to travel. Layer 2: Data Link Layer Metaphor: Local Delivery Van Role: Like a local delivery van that carries the message within the sender's town using the local routes (using MAC addresses). Layer 3: Network Layer Metaphor: Long-Distance Courier System Role: Determines the overall best path (using IP addresses) to get the message from the sender’s town to the recipient’s town, like a long-distance courier system. Layer 4: Transport Layer Metaphor: Message Integrity Checker Role: Ensures all the parts of the message arrive intact and in order, l

Virtual network peering (Vnet Peering)

Image
Virtual network peering enables you to seamlessly connect two or more Virtual Networks in Azure.  Why vnet peering is needed Virtual networks within different :- Regions. Subscriptions. Azure AD Tenants. cant communicate directly with each other. What is Vnet Peering Virtual network peering enables you to seamlessly connect two or more Virtual Networks in Azure. Vnet peering is of 2 types :- Virtual network peering: Connect virtual networks within the same Azure region. Global virtual network peering: Connecting virtual networks across Azure regions. Benefits of Vnet Peering Low-latency, high-bandwidth connection between resources in different virtual networks. Traffic between peered virtual networks is private. No public Internet, gateways, or encryption is required.

A mind map for azure storage(helpful for AZ-303)

Image
  Mind Map shows various features of azure storage and their relationship.(please download image for more clarity) 

Azure Triggered WebJob VS Continues WebJobs what to prefer.

When you deploy webjobs in a App Service Plan  they share the common CPU and RAM. An ASP is just like a VM given to you for PaaS services but is maintained  by Microsoft. If you deploy webjobs in continues mode and if the RAM or CPU utilization is high then your webjob will be killed automatically and you wont get notification. Once killed there is complex process to revive them  and that is not quick. What i prefer is deploy webjobs in triggered mode which is backed by a resilient windows service which at any cost will run your webjobs even if they crashed or killed .