⏱︎
Read time:
Introduction: When teams build secure document-sharing solutions on Azure, they often need to balance strong internal authentication with simple external access. Internal users should sign in with Microsoft Entra ID, but external recipients may only need a time-limited link to…
⏱︎
Read time:
Introduction: Modern cloud architecture should minimize secret management while preserving strong authorization boundaries. In this implementation, we evolved Entra-ID-FunctionApp and EntraID-FunctionApp-Client from a delegated-token mindset toward a managed identity + app role model for service-to-service access.The result is a secretless pattern: the client signs in users…
⏱︎
Read time:
Introduction: Hybrid identity remains one of the most common deployment models for organizations migrating to Microsoft Entra ID while continuing to use Active Directory Domain Services (AD DS). Instead of maintaining separate identities in both environments, organizations synchronize their on-premises…
⏱︎
Read time:
Introduction: When building enterprise-grade serverless applications with Microsoft Azure Functions, it is common to secure APIs with Microsoft Azure Application Gateway rather than exposing the Function App endpoint directly to the internet. Using Application Gateway provides several advantages: One common…
⏱︎
Read time:
Introduction: In a .NET 8 server-side MVC application integrated with Microsoft Entra ID, a common requirement is to force the user session to time out after 60 minutes. At first glance, this looks simple: configure the local application cookie to…