cloud platform security
24 TopicsModernizing Terraform Pipelines on Azure: OIDC Federation for GitHub Actions and Azure DevOps
The secret nobody wants to rotate Most Terraform-on-Azure pipelines we see still authenticate the same way they did three years ago. A long-lived ARM_CLIENT_SECRET sitting in GitHub Actions or Azure DevOps, set once, copied around, and rotated only when something breaks. It's the most ignored credential in the cloud, and statistically the most likely one to leak. A developer screenshots a variable group. A pipeline log echoes a value. A fork inherits a secret. Or the secret simply expires on a Friday evening and takes production deployments with it. Workload Identity Federation (WIF) makes this whole class of problem go away. The pipeline mints a short-lived token at runtime, exchanges it for an Azure access token via Microsoft Entra, and never touches a secret. GitHub Actions has supported it since 2021. Azure DevOps service connections went GA with WIF in February 2024. The azurerm Terraform provider has supported it since v3.7. This post walks through the pattern end-to-end, for both GitHub Actions and Azure DevOps, the way I've rolled it out across multiple customer estates. How the exchange actually works Before any YAML, it helps to picture what's happening: The CI system (GitHub or ADO) signs a short-lived JWT describing exactly what's running- which repo, which branch, which environment, which service connection. The pipeline sends that JWT to Microsoft Entra ID. Entra checks it against a federated identity credential you've configured on a managed identity or app registration. The iss, sub, and aud claims must match case-sensitively. If it matches, Entra returns an Azure access token valid for the duration of the job. Terraform uses it. The job ends. The token expires. Nothing persists. The token is bound to a specific subject like repo:contoso/platform:environment:prod or sc://contoso/platform/azure-prod. It can't be reused from another repo, branch, or pipeline. Recommended Architecture A few choices that usually hold up in production: Decision Choice Identity type User-assigned managed identity (UAMI), not app registration Identity granularity One UAMI per environment (not per pipeline) Trust scope Pinned to the environment claim, not the branch RBAC scope Resource group, not subscription Remote state OIDC + use_azuread_auth = true, shared key access disabled Why UAMIs? They live in your subscription, don't need Application Administrator rights to manage, and follow the lifecycle of the resource group they belong to. Why one per environment? Pipeline-per-identity explodes into hundreds of identities. Environment-per-identity maps cleanly to deployment scopes. Part 1 - GitHub Actions Step 1: Create the identity and federate it Two commands per environment. That's it. az identity create -g rg-platform-identity -n id-tf-prod -l eastus az identity federated-credential create \ --name github-prod \ --identity-name id-tf-prod \ --resource-group rg-platform-identity \ --issuer https://token.actions.githubusercontent.com \ --subject repo:contoso/platform:environment:prod \ --audiences api://AzureADTokenExchange Repeat for nonprod. No secret is created anywhere. Step 2: Wire it up in GitHub In repo Settings → Environments, create nonprod and prod. On prod, add required reviewers and a branch rule restricting deployments to main. Then add three environment variables (not secrets - these aren't sensitive): AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_SUBSCRIPTION_ID. The workflow itself stays small: permissions: id-token: write contents: read jobs: apply: runs-on: ubuntu-latest environment: prod env: ARM_USE_OIDC: "true" ARM_CLIENT_ID: ${{ vars.AZURE_CLIENT_ID }} ARM_TENANT_ID: ${{ vars.AZURE_TENANT_ID }} ARM_SUBSCRIPTION_ID: ${{ vars.AZURE_SUBSCRIPTION_ID }} steps: - uses: actions/checkout@v4 - uses: hashicorp/setup-terraform@v3 - run: terraform init && terraform apply -auto-approve Three things make this secure: id-token: write is the only elevated permission, and it doesn't grant write access to anything in GitHub, it just lets the runner mint a JWT. The environment: line picks the right AZURE_CLIENT_ID and drives the sub claim. The federation refuses anything else. No azure/login step is needed for Terraform. The azurerm provider reads GitHub's OIDC environment variables automatically. Part 2 - Azure DevOps The model is identical. The mechanics are different. ADO offers two creation paths for a WIF service connection: automatic (it creates an app registration for you) and manual (you bring your own UAMI). For platform teams, manual + UAMI is almost always the better choice to ensure identity lives where governance lives. The flow is a small dance between the two portals: In Azure DevOps, create a new ARM service connection → choose Workload Identity Federation (manual) → fill in your UAMI's client ID, tenant ID, and subscription. Save as draft. ADO shows you an issuer URL and a subject identifier. In Azure, on the UAMI, add a federated credential using the values ADO showed you. The subject looks like sc://contoso/platform/azure-prod. Back in ADO, click Verify and save. In the pipeline, the service connection only "activates" if a task in the job loads it. The simplest way is the AzureCLI@2 task: - task: AzureCLI@2 inputs: azureSubscription: azure-prod # the WIF service connection scriptType: bash scriptLocation: inlineScript inlineScript: | terraform init && terraform apply -auto-approve env: ARM_USE_OIDC: "true" ARM_CLIENT_ID: $(AZURE_CLIENT_ID) ARM_TENANT_ID: $(AZURE_TENANT_ID) ARM_SUBSCRIPTION_ID: $(AZURE_SUBSCRIPTION_ID) ARM_ADO_PIPELINE_SERVICE_CONNECTION_ID: $(SERVICE_CONNECTION_ID) SYSTEM_ACCESSTOKEN: $(System.AccessToken) SYSTEM_OIDCREQUESTURI: $(System.OidcRequestUri) For teams converting dozens of legacy connections, the Azure DevOps team published a PowerShell helper that walks every ARM service connection in a project and converts them in place. There's a 7-day rollback window on each connection, which makes the migration genuinely low-risk. Don't forget the state file The Terraform state is your real blast radius. With OIDC, it's almost free to lock it down too. The same UAMI can read and write blob data without the storage account key: backend "azurerm" { resource_group_name = "rg-tfstate" storage_account_name = "sttfstateprodeastus" container_name = "platform-prod" key = "platform.tfstate" use_oidc = true use_azuread_auth = true } Grant the UAMI Storage Blob Data Contributor on the container (not the account), disable shared key access on the storage account, and you've removed the last secret in the pipeline. RBAC and break-glass Federation removes a credential, not a privilege. A few habits worth keeping: Scope role assignments to resource groups, not subscriptions. The whole point of federation is that scoping is now trivially easy. Use Role Based Access Control Administrator instead of User Access Administrator if your Terraform creates role assignments. It's a more recent, narrower role. Have a documented break-glass. If GitHub or ADO has a token-service incident, you still need a path to ship a hotfix. A single hardware-key-protected emergency app registration in a separate identity boundary works well, audited monthly. Monitor sign-ins. Every federated exchange shows up in Entra sign-in logs as a service principal sign-in. Pipe these to Sentinel and alert on anomalies like sign-ins outside expected hours, or from IPs outside GitHub's published ranges. The errors you will hit (and what they really mean) Symptom What it actually is AADSTS70021: No matching federated identity record found Case-sensitive mismatch in iss, sub, or aud. Almost always a trailing slash or a capitalised character AADSTS700016: Application not found in directory Wrong client ID or tenant. Not a federation problem 403 on a resource even though token exchange worked Federation is fine. Your RBAC isn't. Check the exact scope Unable to determine OIDC token (ADO) No task in the job loaded the service connection. Add an AzureCLI@2 step Works on main, fails on tags You pinned sub to a branch ref. Add a second federated credential for tags, or move to environment-based scoping Migrating without a maintenance window You almost never get to do this on a greenfield repo. The order that has worked for me on legacy estates: Create the new UAMI alongside the old service principal, with the same role assignments. Federate one canary pipeline. Verify it deploys equivalently. Cut over pipelines in waves, lowest-risk environment first. Once a full release cycle passes cleanly, disable the old SP's secret. Wait another cycle. Then delete the SP entirely. Add a CI gate that fails any new pipeline introducing ARM_CLIENT_SECRET. The old and new auth methods coexist on the same subscription throughout. There's no hard cutover and no maintenance window, just a steady drift toward zero secrets. Wrapping up If you do nothing else after reading this, do one thing: search your CI variable groups for ARM_CLIENT_SECRET. Every result is an outage or a breach waiting to happen. Federation is one of those rare changes that's both more secure and less work to operate. Once you've set it up, you stop thinking about credential rotation, secret expiry, and quarterly access reviews for service principals. The pipeline simply runs, and the audit trail is in Entra where it belongs. That's a good trade.2.2KViews17likes11CommentsDefending the cloud: Azure neutralized a record-breaking 15 Tbps DDoS attack
On October 24, 2025, Azure DDOS Protection automatically detected and mitigated a multi-vector DDoS attack measuring 15.72 Tbps and nearly 3.64 billion packets per second (pps). This was the largest DDoS attack ever observed in the cloud and it targeted a single endpoint in Australia. By utilizing Azure’s globally distributed DDoS Protection infrastructure and continuous detection capabilities, mitigation measures were initiated. Malicious traffic was effectively filtered and redirected, maintaining uninterrupted service availability for customer workloads. The attack originated from Aisuru botnet. Aisuru is a Turbo Mirai-class IoT botnet that frequently causes record-breaking DDoS attacks by exploiting compromised home routers and cameras, mainly in residential ISPs in the United States and other countries. The attack involved extremely high-rate UDP floods targeting a specific public IP address, launched from over 500,000 source IPs across various regions. These sudden UDP bursts had minimal source spoofing and used random source ports, which helped simplify traceback and facilitated provider enforcement. Attackers are scaling with the internet itself. As fiber-to-the-home speeds rise and IoT devices get more powerful, the baseline for attack size keeps climbing. As we approach the upcoming holiday season, it is essential to confirm that all internet-facing applications and workloads are adequately protected against DDOS attacks. Additionally, do not wait for an actual attack to assess your defensive capabilities or operational readiness—conduct regular simulations to identify and address potential issues proactively. Learn more about Azure DDOS Protection at Azure DDoS Protection Overview | Microsoft Learn51KViews7likes3CommentsBuilding Azure Right: A Practical Checklist for Infrastructure Landing Zones
When the Gaps Start Showing A few months ago, we walked into a high-priority Azure environment review for a customer dealing with inconsistent deployments and rising costs. After a few discovery sessions, the root cause became clear: while they had resources running, there was no consistent foundation behind them. No standard tagging. No security baseline. No network segmentation strategy. In short—no structured Landing Zone. That situation isn't uncommon. Many organizations sprint into Azure workloads without first planning the right groundwork. That’s why having a clear, structured implementation checklist for your Landing Zone is so essential. What This Checklist Will Help You Do This implementation checklist isn’t just a formality. It’s meant to help teams: Align cloud implementation with business goals Avoid compliance and security oversights Improve visibility, governance, and operational readiness Build a scalable and secure foundation for workloads Let’s break it down, step by step. 🎯 Define Business Priorities Before Touching the Portal Before provisioning anything, work with stakeholders to understand: What outcomes matter most – Scalability? Faster go-to-market? Cost optimization? What constraints exist – Regulatory standards, data sovereignty, security controls What must not break – Legacy integrations, authentication flows, SLAs This helps prioritize cloud decisions based on value rather than assumption. 🔍 Get a Clear Picture of the Current Environment Your approach will differ depending on whether it’s a: Greenfield setup (fresh, no legacy baggage) Brownfield deployment (existing workloads to assess and uplift) For brownfield, audit gaps in areas like scalability, identity, and compliance before any new provisioning. 📜 Lock Down Governance Early Set standards from day one: Role-Based Access Control (RBAC): Granular, least-privilege access Resource Tagging: Consistent metadata for tracking, automation, and cost management Security Baselines: Predefined policies aligned with your compliance model (NIST, CIS, etc.) This ensures everything downstream is both discoverable and manageable. 🧭 Design a Network That Supports Security and Scale Network configuration should not be an afterthought: Define NSG Rules and enforce segmentation Use Routing Rules to control flow between tiers Consider Private Endpoints to keep services off the public internet This stage sets your network up to scale securely and avoid rework later. 🧰 Choose a Deployment Approach That Fits Your Team You don’t need to reinvent the wheel. Choose from: Predefined ARM/Bicep templates Infrastructure as Code (IaC) using tools like Terraform Custom Provisioning for unique enterprise requirements Standardizing this step makes every future deployment faster, safer, and reviewable. 🔐 Set Up Identity and Access Controls the Right Way No shared accounts. No “Owner” access to everyone. Use: Azure Active Directory (AAD) for identity management RBAC to ensure users only have access to what they need, where they need it This is a critical security layer—set it up with intent. 📈 Bake in Monitoring and Diagnostics from Day One Cloud environments must be observable. Implement: Log Analytics Workspace (LAW) to centralize logs Diagnostic Settings to capture platform-level signals Application Insights to monitor app health and performance These tools reduce time to resolution and help enforce SLAs. 🛡️ Review and Close on Security Posture Before allowing workloads to go live, conduct a security baseline check: Enable data encryption at rest and in transit Review and apply Azure Security Center recommendations Ensure ACC (Azure Confidential Computing) compliance if applicable Security is not a phase. It’s baked in throughout—but reviewed intentionally before go-live. 🚦 Validate Before You Launch Never skip a readiness review: Deploy in a test environment to validate templates and policies Get sign-off from architecture, security, and compliance stakeholders Track checklist completion before promoting anything to production This keeps surprises out of your production pipeline. In Closing: It’s Not Just a Checklist, It’s Your Blueprint When implemented well, this checklist becomes much more than a to-do list. It’s a blueprint for scalable, secure, and standardized cloud adoption. It helps teams stay on the same page, reduces firefighting, and accelerates real business value from Azure. Whether you're managing a new enterprise rollout or stabilizing an existing environment, this checklist keeps your foundation strong. Tags - Infrastructure Landing Zone Governance and Security Best Practices for Azure Infrastructure Landing Zones Automating Azure Landing Zone Setup with IaC Templates Checklist to Validate Azure Readiness Before Production Rollout Monitoring, Access Control, and Network Planning in Azure Landing Zones Azure Readiness Checklist for Production6.6KViews6likes3CommentsInfrastructure Landing Zone - Implementation Decision-Making:
🚀 Struggling to choose the right Infrastructure Landing Zone for your Azure deployment? This guide breaks down each option—speed, flexibility, security, and automation—so you can make the smartest decision for your cloud journey. Don’t risk costly mistakes—read now and build with confidence! 🔥4.7KViews4likes7CommentsMicrosoft Azure Cloud HSM is now generally available
Microsoft Azure Cloud HSM is now generally available. Azure Cloud HSM is a highly available, FIPS 140-3 Level 3 validated single-tenant hardware security module (HSM) service designed to meet the highest security and compliance standards. With full administrative control over their HSM, customers can securely manage cryptographic keys and perform cryptographic operations within their own dedicated Cloud HSM cluster. In today’s digital landscape, organizations face an unprecedented volume of cyber threats, data breaches, and regulatory pressures. At the heart of securing sensitive information lies a robust key management and encryption strategy, which ensures that data remains confidential, tamper-proof, and accessible only to authorized users. However, encryption alone is not enough. How cryptographic keys are managed determines the true strength of security. Every interaction in the digital world from processing financial transactions, securing applications like PKI, database encryption, document signing to securing cloud workloads and authenticating users relies on cryptographic keys. A poorly managed key is a security risk waiting to happen. Without a clear key management strategy, organizations face challenges such as data exposure, regulatory non-compliance and operational complexity. An HSM is a cornerstone of a strong key management strategy, providing physical and logical security to safeguard cryptographic keys. HSMs are purpose-built devices designed to generate, store, and manage encryption keys in a tamper-resistant environment, ensuring that even in the event of a data breach, protected data remains unreadable. As cyber threats evolve, organizations must take a proactive approach to securing data with enterprise-grade encryption and key management solutions. Microsoft Azure Cloud HSM empowers businesses to meet these challenges head-on, ensuring that security, compliance, and trust remain non-negotiable priorities in the digital age. Key Features of Azure Cloud HSM Azure Cloud HSM ensures high availability and redundancy by automatically clustering multiple HSMs and synchronizing cryptographic data across three instances, eliminating the need for complex configurations. It optimizes performance through load balancing of cryptographic operations, reducing latency. Periodic backups enhance security by safeguarding cryptographic assets and enabling seamless recovery. Designed to meet FIPS 140-3 Level 3, it provides robust security for enterprise applications. Ideal use cases for Azure Cloud HSM Azure Cloud HSM is ideal for organizations migrating security-sensitive applications from on-premises to Azure Virtual Machines or transitioning from Azure Dedicated HSM or AWS Cloud HSM to a fully managed Azure-native solution. It supports applications requiring PKCS#11, OpenSSL, and JCE for seamless cryptographic integration and enables running shrink-wrapped software like Apache/Nginx SSL Offload, Microsoft SQL Server/Oracle TDE, and ADCS on Azure VMs. Additionally, it supports tools and applications that require document and code signing. Get started with Azure Cloud HSM Ready to deploy Azure Cloud HSM? Learn more and start building today: Get Started Deploying Azure Cloud HSM Customers can download the Azure Cloud HSM SDK and Client Tools from GitHub: Microsoft Azure Cloud HSM SDK Stay tuned for further updates as we continue to enhance Microsoft Azure Cloud HSM to support your most demanding security and compliance needs.7.5KViews3likes2CommentsDesigning GitHub Actions Runners on Private AKS with a Secured Azure Virtual WAN Hub
Self-hosted GitHub Actions runners can execute workflows close to private deployment targets without making those targets publicly reachable. That network access also makes the runner environment part of the security boundary. A workflow can use the connectivity and credentials available to its runner, so private connectivity needs to be considered alongside outbound access, repository permissions, and workload isolation. A private Azure Kubernetes Service (AKS) cluster protects access to the Kubernetes API through private networking. It does not, by itself, restrict all traffic leaving the nodes or runner pods. In this single-region design, the AKS virtual network connects to a secured Azure Virtual WAN hub. Azure Firewall applies destination-based policies to Internet-bound connections, while authorized administrators reach the private API from a management host with the required network access. Actions Runner Controller (ARC) manages ephemeral runners as Kubernetes pods and adjusts runner capacity to the jobs assigned by GitHub Actions. A dedicated user node pool separates runner execution from the pool selected for the controller and listener. Runner-pod scaling and AKS node scaling remain different mechanisms, with separate capacity and operational considerations. The design brings together private API access, controlled GitHub egress, runner authentication, and firewall logging. Network-isolated AKS with a managed bootstrap cache and GitHub App authentication are selected options, not universal requirements for every private runner deployment. The sections below explain those choices and link their commands and configuration settings to official Microsoft and GitHub sources. Overall connectivity The four numbered paths show how the environment is managed, reaches GitHub, retrieves bootstrap artifacts, and records firewall activity: Administrators reach the management VM through Azure Bastion or approved private access, then manage AKS through its private Kubernetes API. The ARC controller, listener, and runner pods initiate outbound HTTPS connections to GitHub through the secured hub and Azure Firewall. No inbound GitHub job webhook is configured. AKS nodes retrieve bootstrap artifacts through the private ACR endpoint. This cache does not replace GitHub Container Registry access for runner images. Azure Firewall sends diagnostic logs to Log Analytics so operators can investigate allowed and denied connections. The private API and bootstrap-cache paths do not traverse the hub firewall. Management-tool Internet access and connections to deployment targets are not shown. Architecture scope and validation The architecture and configuration examples cover: Private Kubernetes API access from an authorized management host, without a public API endpoint Internet-bound spoke traffic routed through the secured hub and GitHub-specific firewall application rules ARC configuration and a manually triggered workflow targeting a dedicated runner node pool Firewall evidence for allowed GitHub connections and controlled denied connections Ephemeral runner lifecycle and its distinction from AKS node autoscaling The baseline uses GitHub.com, Azure public cloud, Linux nodes, organization-scoped runner registration, and shell-only workflow steps. It does not configure container builds, production deployment credentials, or hostile multi-tenant isolation. The command blocks explain configuration rather than direct deployment. A documented command or setting does not establish that the complete combination has been validated in a particular subscription, region, or security environment. Expected results below are validation criteria, not results from an executed deployment. The command blocks explain configuration rather than direct deployment. A documented command or setting does not establish that the complete combination has been validated in a particular subscription, region, or security environment. Expected results below are validation criteria, not results from an executed deployment. Prerequisites and assumptions The configuration examples assume: An Azure subscription with the permissions required for the network, firewall, AKS cluster, managed identity, and scoped role assignments Sufficient regional VM quota and an approved budget for Azure Firewall, Virtual WAN, AKS nodes, the private bootstrap registry, monitoring, and management services A GitHub organization and private repository, with a plan that supports creating the additional restricted runner group used here, such as GitHub Team or GitHub Enterprise Permission to configure an approved ARC authentication method; the example chooses an organization-owned GitHub App An approved Linux management host with private access to the AKS spoke, Azure CLI 2.73.0 or later, Helm 3, a compatible kubectl, kubelogin, and Bash Outbound access from that management host to Azure sign-in and management services and GitHub's OCI chart distribution endpoints The host can be a VM in the spoke's management subnet, accessed through Azure Bastion or an existing approved private connection. A public SSH endpoint is not part of this design. A default, unconnected Cloud Shell session does not provide private cluster access. See private AKS connectivity guidance, Azure Bastion connectivity, and runner-group availability and access. Command blocks illustrate configuration from that Bash host. They are not intended for direct execution without environment-specific review. Private keys and tokens do not belong in repositories, terminal history, or published screenshots. [!WARNING] Setting runner capacity to zero does not stop firewall, hub, registry, monitoring, or system-node charges. These services have independent pricing and capacity requirements. Step 1: Network and AKS egress model Azure CNI Overlay separates node addressing from pod addressing. Nodes receive IP addresses from their VNet subnets, while pods use a separate CIDR range. Each additional runner pod therefore does not consume another VNet subnet address. This conserves spoke address space as runner capacity grows. See Microsoft's Overlay subnet-sizing guidance. The address plan separates the hub, node pools, management access, pod network, and Kubernetes services: Secured virtual hub: 10.60.x.x/22, for Virtual WAN hub services and Azure Firewall AKS spoke VNet: 10.61.x.x/16, for nodes and private management System node subnet: 10.61.x.x/24, for AKS services and the selected ARC controller and listener placement Runner node subnet: 10.61.x.x/23, for the dedicated Linux user node pool Management subnet: 10.61.x.x/24, for the approved private administration host AzureBastionSubnet, if used: 10.61.x.x/26, separate from the management subnet Overlay pod address space: 10.62.x.x/16 Kubernetes service range: 10.63.x.x/24, with a DNS service IP represented as 10.63.x.x Size each node subnet for that pool's maximum node count, additional nodes used during surge upgrades, and any other resources consuming addresses from the subnet. Azure reserves five addresses in each subnet, leaving 251 usable addresses in a /24 before resources are allocated. Sizing only for the initial nodes can leave insufficient addresses for scaling or upgrades. See Overlay node-subnet planning and AKS upgrade and scaling considerations. Size the pod CIDR for nodes across both the system and runner pools, including temporary surge nodes. Overlay allocates a fixed /24 pod block to every node; lowering maxPods does not shrink that block. The networking model supports up to 250 pods per node, but that is not a recommendation to place 250 CI runners on one node. An ARC runner-pod limit does not replace node-level address planning. See Overlay pod allocation. Choose a supported RFC 1918 or RFC 6598 pod range that does not overlap node subnets or connected networks. An overlap with a destination network can make that destination unreachable from pods even when the firewall allows it. Keep the Kubernetes service CIDR separate from the pod, node, and connected-network ranges. The DNS service IP must be inside the service CIDR and must not use its first service address. See Overlay address-planning requirements and AKS reserved-range restrictions. Network-isolated AKS with outbound type none The example selects a private, network-isolated AKS cluster with an AKS-managed bootstrap artifact cache and outboundType: none. Network isolation is an additional choice beyond a private API endpoint, not a prerequisite imposed by ARC or Virtual WAN. Microsoft documents that none does not create an AKS egress path or require a default route during validation, and supports bring-your-own VNets. Required egress is supplied explicitly through a firewall, proxy, gateway, or other network component. Here, that component is the secured Virtual WAN hub. The private cache supplies AKS bootstrap images; GitHub traffic still needs the firewall path described below. This is a different AKS outbound model from userDefinedRouting, not a claim that a vWAN-propagated default satisfies UDR validation. The userDefinedRouting model has its own node-subnet route-table requirements and is not an interchangeable option in the example. See AKS outbound types, network-isolated AKS, and the managed-cache creation guide. A conventional private AKS cluster can instead use another documented outbound model and permit its required AKS dependencies through the chosen egress controls. Changing to that model requires a different configuration and endpoint review; removing the cache flags from this example is not an equivalent substitution. Step 2: Secured hub and spoke connectivity The example separates networking into rg-arc-network and the cluster and identity into rg-arc-aks. The resources use the same selected region. The configuration consists of: A Standard Virtual WAN with a secured virtual hub and Azure Firewall Standard. Azure Firewall Manager exposes the secured-hub creation flow. The /22 address-space choice accommodates Microsoft's documented Azure Firewall scaling requirement in virtual hub address-space settings. VPN and ExpressRoute gateways are separate requirements when the management design uses them. An associated Firewall Policy with default-deny behavior, rather than an unrestricted outbound allow. A spoke named vnet-arc-spoke, with system subnet snet-aks-system, runner subnet snet-aks-runners, and management subnet snet-management. The AKS node subnets are not delegated to another service. A Virtual WAN > Virtual network connections connection between the hub and spoke. This is not VNet peering to a customer-managed hub VNet. Azure-provided DNS for the baseline, with the management host in the same VNet as the AKS nodes. Intra-cluster connectivity consistent with Azure CNI Overlay requirements. NSGs must account for required communication between the system and runner subnets. The official secured cloud network tutorial documents the portal creation flow. Resource names and some blade labels can vary as the portal evolves. Step 3: GitHub egress policy and logging The associated Firewall Policy > Rule collection groups contains an Application rule collection with action Allow, for example at priority 200. The rules use HTTPS:443 and target FQDNs. Rule sources are the system and runner subnet CIDRs, represented here as 10.61.x.x/24 and 10.61.x.x/23. The controller and listener need GitHub connectivity as well as the runner pods. With Azure CNI Overlay, traffic leaving the cluster is translated to node addresses, rather than using the overlay pod CIDR as the firewall source for these flows. The following destinations are a subset of GitHub's documented domains, grouped by function. Essential service traffic and the chart and image pulls used here need their corresponding rules. Action, artifact, package, and release functions need the relevant destinations when those functions are used; the table is not a claim that every job needs every row. Rule purpose GitHub-documented target FQDNs Actions service and API github.com, api.github.com, *.actions.githubusercontent.com Action downloads codeload.github.com Logs, artifacts, cache results-receiver.actions.githubusercontent.com, *.blob.core.windows.net Runner updates objects.githubusercontent.com, objects-origin.githubusercontent.com, github-releases.githubusercontent.com, github-registry-files.githubusercontent.com GitHub container assets ghcr.io, *.pkg.github.com, pkg-containers.githubusercontent.com Release downloads release-assets.githubusercontent.com GitHub lists the required domains by function in its accessible-domain reference. Its documentation notes that some firewalls require recursive rules for CNAME records, whose targets can change while the listed domains remain constant. Workflows may also require access to other network resources. Git LFS and Dependabot have additional domain entries in that reference and are outside this baseline. The public Blob wildcard is broad. It is a documented GitHub dependency, not an exfiltration-prevention guarantee. It also does not replace private-endpoint DNS or storage authorization. Management-host rules are separately scoped to approved Azure and GitHub tooling needs. Management-host sign-in is not a reason to broaden node permissions. Adding a private endpoint's public hostname to an Internet allow rule does not establish private endpoint reachability. For this network-isolated baseline, public AKS bootstrap exceptions from a conventional firewall tutorial are not automatically applicable. Additional services and add-ons have their own network-isolated feature dependencies and AKS outbound requirements. Rule evaluation and inspection depth Azure Firewall evaluates network rules before application rules. An Any destination / TCP 443 network allow can therefore bypass the intended application FQDN restriction. Inherited policies also affect evaluation. See rule processing. Standard performs SNI-based HTTPS destination filtering. It does not decrypt HTTPS payloads. Premium TLS inspection is a separate design, including certificate trust in nodes, controller, listener, runners, and tools that make inspected connections. See features by SKU. Diagnostic configuration Diagnostic settings belong to the Azure Firewall resource, not only the policy. The configuration includes: Application-rule and network-rule logs sent to an approved Log Analytics workspace Resource specific destination tables for the query example below DNS-proxy logs when DNS proxy is enabled Appropriate retention and access controls for network and workflow-related evidence Resource logs are not retained for query until a diagnostic destination is configured. See Azure Firewall monitoring. Step 4: Routing intent and the default path The routing configuration includes: Internet Traffic routing intent with the hub's Azure Firewall as next hop The applicable Internet security / default-route propagation setting enabled on the spoke connection Private Traffic left unconfigured in this baseline; supported inter-spoke or hybrid private inspection is a separate policy decision Gateway-route propagation enabled on any relevant spoke subnet route table Effective routes showing the spoke's Internet default toward the virtual hub and the hub's Internet policy selecting Azure Firewall The NIC next-hop display need not show the firewall's private IP directly. The spoke-to-hub and hub-to-firewall parts need to be considered together. An unexplained manual default route to the secured-hub firewall is not part of this example. See routing intent configuration and troubleshooting and NIC effective routes. The evidence described in Step 10 includes matching firewall records. A configured policy or a successful HTTPS request alone does not prove that the request traversed the firewall. Step 5: Private AKS and the managed bootstrap cache The managed bootstrap cache is not mandatory for every private AKS cluster. It is the selected bootstrap option for the network-isolated Cache plus none model used here. Microsoft also documents a bring-your-own private ACR option. ARC itself requires a suitable Kubernetes cluster, not an AKS bootstrap cache. See Microsoft's network-isolated cluster options and GitHub's ARC prerequisites. An existing suitable cluster does not need to be recreated for ARC. The creation example below applies only when provisioning the selected cluster model; it is not a migration procedure for an existing cluster. The Bash examples adapt Microsoft's documented commands to the resource names and choices in this design. The resource groups, VNet, subnets, hub connection, and firewall configuration are assumed to exist. CIDRs and the DNS service IP remain placeholders. The combined sequence is not ready-to-run deployment instructions. The following block uses Azure sign-in, subscription selection, VNet lookup, and Microsoft's private-subnet configuration example. The variable names and grouping are adaptations. export SUBSCRIPTION_ID="<subscription-id>" export LOCATION="<azure-region>" export NETWORK_RG="rg-arc-network" export WORKLOAD_RG="rg-arc-aks" export VNET_NAME="vnet-arc-spoke" export AKS_NAME="aks-arc" export POD_CIDR="<pod-cidr>" export SERVICE_CIDR="<service-cidr>" export DNS_SERVICE_IP="<dns-service-ip>" az login az account set --subscription "$SUBSCRIPTION_ID" VNET_ID=$(az network vnet show \ --resource-group "$NETWORK_RG" --name "$VNET_NAME" \ --query id --output tsv) SYSTEM_SUBNET_ID="${VNET_ID}/subnets/snet-aks-system" RUNNER_SUBNET_ID="${VNET_ID}/subnets/snet-aks-runners" az network vnet subnet update \ --resource-group "$NETWORK_RG" --vnet-name "$VNET_NAME" \ --name snet-aks-system --default-outbound false az network vnet subnet update \ --resource-group "$NETWORK_RG" --vnet-name "$VNET_NAME" \ --name snet-aks-runners --default-outbound false The private-subnet setting removes reliance on implicit default outbound access. It does not block explicit firewall egress and is separate from making the AKS API private. This example sets it before creating nodes. For existing VMs, Microsoft documents that a stop and deallocation is required for subnet changes to take effect on their interfaces; this is not guidance to modify AKS-managed VM instances directly. See default outbound access guidance. Control-plane identity The user-assigned control-plane identity has Network Contributor on the example VNet. The VNet scope also supports the private DNS VNet-link operation; this is not a subscription-wide grant. Role-assignment and identity-use permissions are separate deployment prerequisites. The commands adapt user-assigned managed identity creation, AKS VNet permissions, role-assignment syntax, and regional Kubernetes version lookup. AKS_IDENTITY_ID=$(az identity create \ --resource-group "$WORKLOAD_RG" --name id-aks-arc \ --location "$LOCATION" \ --query id --output tsv) AKS_IDENTITY_PRINCIPAL_ID=$(az identity show \ --ids "$AKS_IDENTITY_ID" --query principalId --output tsv) az role assignment create \ --assignee-object-id "$AKS_IDENTITY_PRINCIPAL_ID" \ --assignee-principal-type ServicePrincipal \ --role "Network Contributor" --scope "$VNET_ID" az aks get-versions --location "$LOCATION" --output table export KUBERNETES_VERSION="<supported-regional-kubernetes-version>" Role assignments have propagation delays. The Kubernetes version also needs to be a currently supported regional release, not an obsolete release merely because it exceeds the network-isolated minimum. See AKS managed identities. Cluster configuration example Microsoft's AKS-managed ACR creation example explicitly includes --bootstrap-artifact-source Cache, --outbound-type none, and --enable-private-cluster. The longer command below combines that example with documented private DNS and public-FQDN options, Overlay options, and Microsoft Entra authorization. All remaining switches are described in the official az aks create reference. The selected node name, VM size, count, disk type, and maximum pods are example choices, not a Microsoft-prescribed ARC configuration. az aks create \ --resource-group "$WORKLOAD_RG" \ --name "$AKS_NAME" \ --location "$LOCATION" \ --kubernetes-version "$KUBERNETES_VERSION" \ --assign-identity "$AKS_IDENTITY_ID" \ --enable-private-cluster \ --disable-public-fqdn \ --private-dns-zone system \ --bootstrap-artifact-source Cache \ --outbound-type none \ --network-plugin azure \ --network-plugin-mode overlay \ --pod-cidr "$POD_CIDR" \ --service-cidr "$SERVICE_CIDR" \ --dns-service-ip "$DNS_SERVICE_IP" \ --vnet-subnet-id "$SYSTEM_SUBNET_ID" \ --vm-set-type VirtualMachineScaleSets \ --load-balancer-sku standard \ --nodepool-name systempool \ --node-count 2 \ --node-vm-size Standard_D4s_v5 \ --node-osdisk-type Managed \ --os-sku Ubuntu \ --max-pods 30 \ --node-os-upgrade-channel NodeImage \ --enable-aad \ --enable-azure-rbac \ --disable-local-accounts \ --generate-ssh-keys Omitting a bootstrap registry resource ID selects the documented AKS-managed cache path. AKS manages its bootstrap registry, cache rules, and private connectivity. The default cache supplies Microsoft bootstrap images; it does not automatically mirror the GHCR controller and runner images. Those pulls need the GitHub egress rules from Step 3. The two-node system pool is an illustrative minimum, not a production availability recommendation. Capacity needs to account for AKS services, the ARC controller, and the listener. Microsoft recommends three system nodes for production. See system-pool requirements, the network-isolated creation guide, and the CLI parameter reference. Installer access and private DNS The authorization and connectivity requirements are separate: Azure Kubernetes Service RBAC Cluster Admin, scoped to the cluster, is one broad built-in role that permits the approved installer to install ARC CRDs and cluster-scoped RBAC. It is not a requirement to give every operator permanent cluster-admin access. Cluster-user credential retrieval requires the corresponding management permission, such as Azure Kubernetes Service Cluster User Role when not already covered. Assignment propagation affects access availability. These installer permissions are not workflow permissions. The management host needs private API resolution and network reachability independently of its credentials. The credential and connection commands adapt private-cluster connectivity checks and kubelogin's Azure CLI authentication example. The DNS lookup uses the documented nslookup check. The expected state is private API resolution and nodes marked Ready. With Azure-provided DNS, AKS's default API private-zone link to the node VNet supplies API resolution. Registry resolution is a separate check: inspect the AKS-created bootstrap registry, its private endpoint, and the relevant private DNS records and VNet links. Both registry login and data-endpoint names must resolve to the intended private endpoints. Do not assume successful API resolution also verifies registry DNS. Private API or bootstrap-image failures are distinct from ARC installation failures. Relevant references are private-cluster DNS, network-isolated troubleshooting, and Microsoft Entra authorization for AKS. Step 6: Dedicated runner user pool The configuration separates runner execution from the pool selected for the controller and listener. The runner pool is a Linux User pool on its own subnet, with a taint and Cluster Autoscaler bounds. This pool separation is a design choice, not an ARC installation requirement. The command combines documented dedicated-subnet Overlay configuration, taints and tolerations, and node-pool parameters. The node count, VM size, taint value, and autoscaler bounds are illustrative. The Helm values in Step 8 combine a runner-pool selector with the matching toleration. A toleration alone permits placement; it does not require that placement. ARC scales runner pods. Cluster Autoscaler supplies node capacity for unschedulable pods. Their limits are independent, and neither is a hard spending cap. See AKS Cluster Autoscaler and node-pool commands. Step 7: GitHub authentication and repository access A GitHub App is recommended, not mandatory, for repository- or organization-scoped ARC registration. GitHub also documents personal access token authentication, including classic and fine-grained tokens. Enterprise-level runner registration does not support GitHub App authentication; GitHub's ARC quickstart specifies a personal access token (classic) for that scope. See ARC authentication methods and the ARC quickstart. This example retains the recommended organization-owned GitHub App option. Its configuration includes: Organization permissions > Self-hosted runners: Read and write and Repository permissions > Metadata: Read-only. The documented repository Administration: Read and write permission applies to repository-scoped registration, not the organization-scoped configuration used here. An App installation in the organization, with its App ID, installation ID, and private key held securely outside the repository. A runner group named arc-private, restricted to the intended private repository. App installation scope is not a substitute for runner-group access control. GitHub credentials held in a Kubernetes Secret in the runner scale-set namespace. ARC scale-set job delivery uses outbound HTTPS long polling. A public inbound job webhook is not required by this mechanism; a separate integration can have different requirements. This flow is described in GitHub's ARC architecture. The Secret command adapts GitHub's documented file-based private-key example. The names and variable substitutions are the changes; the Secret keys follow the documented format. The example reads key contents from a file instead of putting the private key in a shell argument or Helm values. The file, Kubernetes Secret, Secret-reading permissions, and key rotation remain security responsibilities. See ARC authentication and runner-group access controls. If an approved personal access token is used instead, the Secret uses the documented github_token key and the permissions required for the chosen registration scope. That is an alternative authentication configuration, not an additional credential required alongside the GitHub App. This credential authenticates ARC to GitHub. It does not authorize an Azure deployment. Deployment jobs need a separate, least-privilege identity relationship, such as GitHub-to-Azure OIDC, rather than general access through the installer, cluster, or kubelet identity. Step 8: ARC controller and runner scale-set configuration The examples use released OCI charts rather than legacy RunnerDeployment resources or experimental charts. Both ARC charts are pinned to release 0.15.1; version selection remains subject to review against the official release. Controller configuration These Helm values select the system pool and an explicit controller service-account name. They adapt fields from the release-specific controller chart values. The names, pool selector, and resource sizes are design-specific values, not the chart defaults or measured sizing recommendations. The values correspond to the controller configuration input referenced by --values in the example command. fullnameOverride: arc-controller serviceAccount: name: arc-controller nodeSelector: kubernetes.azure.com/agentpool: systempool resources: requests: cpu: 100m memory: 128Mi limits: memory: 256Mi The installation command adapts the official controller Helm installation, adding the documented version and values-file options. The wait and timeout settings are operational choices, not ARC requirements. export ARC_CHART_VERSION="0.15.1" helm install arc \ --namespace arc-systems \ --create-namespace \ --version "$ARC_CHART_VERSION" \ --values ./controller-values.yaml \ --wait --timeout 10m \ oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller kubectl get deployments,pods --namespace arc-systems Step 9: Workflow targeting the private runner The workflow follows the official ARC quickstart's verification workflow, with a descriptive name, the example scale-set target, and an English output message. It uses workflow_dispatch and a runs-on value matching runnerScaleSetName. The empty permission set and five-minute job timeout are additional restrictions for this shell-only example, not ARC prerequisites. Manual dispatch requires the workflow to be available on the repository's default branch. See GitHub's manual workflow requirements. name: Private AKS runner verification on: workflow_dispatch: permissions: {} jobs: verify-runner: runs-on: arc-private-aks timeout-minutes: 5 steps: - run: echo "This job uses runner scale set runners." The expected lifecycle includes a queued job, an ephemeral runner pod placed on the runners pool, workflow output, and automatic removal of the runner after completion. A pool that has scaled to zero adds node-provisioning time before the runner can start. This workflow verifies job execution only. It intentionally uses no checkout action, cloud login, package feed, artifact upload, or deployment target, and does not actively probe a separate Internet destination. It does not establish complete build-pipeline readiness or prove the firewall route. Those dependencies require separate evidence. See using ARC in a workflow. Documented limitations and design boundaries Area Limitation and consequence Official reference Network-isolated AKS Requires Kubernetes 1.30 or later and the documented CLI minimum. A currently supported regional release is still required. Creation prerequisites Outbound mode none is GA and does not configure or block egress. block is preview and restricted to managed-VNet scenarios. Outbound types Nodes and networking Network isolation does not support Windows pools or kubenet. The documented node-OS upgrade channels are NodeImage and None. Network-isolation limits Bootstrap registry The AKS cache does not make arbitrary application images or workflows offline-capable. BYO ACR adds Premium/private-DNS work. Network-isolated AKS Add-ons and explicit egress Optional features can require additional endpoints. Node public IPs can permit outbound traffic and are not enabled here. Feature limitations Virtual WAN default route The default route is not propagated between hubs. This baseline uses local inspected Internet breakout. Routing intent Routing-intent compatibility Custom hub route tables and specified static next-hop-VNet-connection routes have restrictions. Routing prerequisites Same-VNet traffic Routing intent does not automatically attract traffic between subnets of the same VNet. Private API access here stays local. Hub routing considerations Firewall inspection Standard HTTPS filtering uses SNI, not decrypted payloads or full URL paths. Premium inspection needs certificate trust. Firewall SKUs Network-rule FQDNs Require DNS proxy. Wildcard support is currently limited to the regions listed in the product documentation. This design uses application rules for GitHub HTTPS. FQDN filtering Secured-hub SNAT design NAT Gateway integration inside a secured virtual hub is unsupported. Conventional firewall-subnet NAT patterns do not apply. NAT Gateway integration GitHub authentication scope GitHub App authentication is not supported for enterprise-level runner registration. That scope needs a different setup. ARC authentication Container-based jobs This shell-only configuration does not support Docker-dependent jobs as configured. Documented DinD needs privileged mode. ARC container modes Workload isolation Ephemeral runners, namespaces, and node pools are not a sandbox for hostile code. GitHub secure use, AKS isolation Support and customization GitHub ARC support does not certify the underlying Azure network or every custom pod template, hook, or storage integration. ARC support boundaries86Views2likes1CommentPrivate DNS and Hub–Spoke Networking for Enterprise AI Workloads on Azure
Introduction As organizations deploy enterprise AI platforms on Azure, security requirements increasingly drive the adoption of private-first architectures. Private networking only Centralized firewalls or NVAs Hub–and–spoke virtual network architectures Private Endpoints for all PaaS services While these patterns are well understood individually, their interaction often exposes hidden failure modes, particularly around DNS and name resolution. During a recent production deployment of a private, enterprise-grade AI workload on Azure, several issues surfaced that initially appeared to be platform or service instability. Closer analysis revealed the real cause: gaps in network and DNS design. This post shares a real-world technical walkthrough of the problem, root causes, resolution steps, and key lessons that now form a reusable blueprint for running AI workloads reliably in private Azure environments. Problem Statement The platform was deployed with the following characteristics: Hub and spoke network topology Custom DNS servers running in the hub Firewall / NVA enforcing strict egress controls AI, data, and platform services exposed through Private Endpoints Azure Container Apps using internal load balancer mode Centralized monitoring, secrets, and identity services Despite successful infrastructure deployment, the environment exhibited non-deterministic production issues, including: Container Apps intermittently failing to start or scale AI platform endpoints becoming unreachable from workload subnets Authentication and secret access failures DNS resolution working in some environments but failing in others Terraform deployments stalling or failing unexpectedly Because the symptoms varied across subnets and environments, root cause identification was initially non-trivial. Root Cause Analysis After end-to-end isolation, the issue was not AI services, authentication, or application logic. The core problem was DNS resolution in a private Azure environment. 1. Custom DNS servers were not Azure-aware The hub DNS servers correctly resolved: Corporate domains On‑premises records However, they could not resolve Azure platform names or Private Endpoint FQDNs by default. Azure relies on an internal recursive resolver (168.63.129.16) that must be explicitly integrated when using custom DNS. 2. Missing conditional forwarders for private DNS zones Many Azure services depend on service-specific private DNS zones, such as: privatelink.cognitiveservices.azure.com privatelink.openai.azure.com privatelink.vaultcore.azure.net privatelink.search.windows.net privatelink.blob.core.windows.net Without conditional forwarders pointing to Azure’s internal DNS, queries either: Failed silently, or Resolved to public endpoints that were blocked by firewall rules 3. Container Apps internal DNS requirements were overlooked When Azure Container Apps are deployed with: internal_load_balancer_enabled = true Azure does not automatically create supporting DNS records. The environment generates: A default domain .internal subdomains for internal FQDNs Without explicitly creating: A private DNS zone matching the default domain *, @, and *.internal wildcard records internal service-to-service communication fails. 4. Private DNS zones were not consistently linked Even when DNS zones existed, they were: Spread across multiple subscriptions Linked to some VNets but not others Missing links to DNS server VNets or shared services VNets As a result, name resolution succeeded in one subnet and failed in another, depending on the lookup path. Resolution No application changes were required. Stability was achieved entirely through architectural corrections. ✅ Step 1: Make custom DNS Azure-aware On all custom DNS servers (or NVAs acting as DNS proxies): Configure conditional forwarders for all Azure private DNS zones Forward those queries to: 168.63.129.16 This IP is Azure’s internal recursive resolver and is mandatory for Private Endpoint resolution. ✅ Step 2: Centralize and link private DNS zones A centralized private DNS model was adopted: All private DNS zones hosted in a shared subscription Linked to: Hub VNet All spoke VNets DNS server VNet Any operational or virtual desktop VNets This ensured consistent resolution regardless of workload location. ✅ Step 3: Explicitly handle Container Apps DNS For Container Apps using internal ingress: Create a private DNS zone matching the environment’s default domain Add: * wildcard record @ apex record *.internal wildcard record Point all records to the Container Apps Environment static IP Add a conditional forwarder for the default domain if using custom DNS This step alone resolved multiple internal connectivity issues. ✅ Step 4: Align routing, NSGs, and service tags Firewall, NSG, and route table rules were aligned to: Allow DNS traffic (TCP/UDP 53) Allow Azure service tags such as: AzureCloud CognitiveServices AzureActiveDirectory Storage AzureMonitor Ensure certain subnets (e.g., Container Apps, Application Gateway) retained direct internet access where required by Azure platform services Key Learnings 1. DNS is a Tier‑0 dependency for AI platforms Many AI “service issues” are DNS failures in disguise. DNS must be treated as foundational platform infrastructure. 2. Private Endpoints require Azure DNS integration If you use: Custom DNS ✅ Private Endpoints ✅ Then forwarding to 168.63.129.16 is non‑negotiable. 3. Container Apps internal ingress has hidden DNS requirements Internal Container Apps environments will not function correctly without manually created DNS zones and .internal records. 4. Centralized DNS prevents environment drift Decentralized or subscription-local DNS zones lead to fragile, inconsistent environments. Centralization improves reliability and operability. 5. Validate networking first, then the platform Before escalating issues to service teams: Validate DNS resolution Verify routing Check Private Endpoint connectivity In many cases, the perceived “platform issue” disappears. Quick Production Validation Checklist Before go-live, always validate: ✅ Private FQDNs resolve to private IPs from all required VNets ✅ UDR/NSG rules allow required Azure service traffic ✅ Managed identities can access all dependent resources ✅ AI portal user workflows succeed (evaluations, agents, etc.) ✅ terraform plan shows only intended changes Conclusion Running private, enterprise-grade AI workloads on Azure is absolutely achievable—but it requires intentional DNS and networking design. By: Making custom DNS Azure-aware Centralizing private DNS zones Explicitly handling Container Apps DNS Aligning routing and firewall rules an unstable environment was transformed into a repeatable, production-ready platform pattern. If you are building AI solutions on Azure with Private Endpoints and hub–spoke networking, getting DNS right early will save weeks of troubleshooting later.1.1KViews2likes0CommentsKubernetes Center: Security & LTS/Out-of-Support Version Insights Now Available
What's New Security Insights: The new Security page in Kubernetes Center gives you an immediate, all clusters or Kubernetes Fleet Manager-wide view of your security posture without leaving the portal. At the summary level you can see: Security vulnerabilities broken down by risk level Runtime alerts categorized by severity Non-compliant regulatory standards, with visibility into which benchmarks your clusters are falling short on Drilling deeper into the security detail view exposes four distinct panels: Security Vulnerabilities show a total count of vulnerabilities across all clusters, broken down by risk tier. Runtime Alerts surfaces live alerts from Defender for Containers categorized by High, Medium, Low, and Informational severity. You can see at a glance whether any active threats require immediate attention, and drill into the full alert list with one click. Misconfigurations show a count of configuration issues detected across your clusters, again broken down by risk level. Regulatory Compliance Standards lets you see which compliance standards your clusters are enrolled in, which are passing, and which are failing. The view surfaces the lowest-performing standard with its pass rate, so you know exactly where to focus remediation effort. Recommendations are shown alongside these panels, providing actionable and prioritized guidance. Each recommendation shows affected resource counts and links directly to remediation details. Note: Security insights require Microsoft Defender for Containers to be enabled. Kubernetes Center will confirm at a glance whether all your clusters have it enabled. Cluster Version Support Status: Stay Ahead of End-of-Support Running an out-of-support Kubernetes version is one of the most common and preventable sources of risk in production environments. The new Cluster Version Support Status panel in Kubernetes Center gives you a clear picture of where every cluster stands. The view breaks your clusters down into four states: Status What it means In support Running a supported Kubernetes version. No action needed. Expiring soon Version support is ending soon. Plan your upgrade. Out of support (LTS eligible) Out of support but eligible for Long Term Support. An easy path to extend coverage. Out of support No longer supported and not LTS eligible. Upgrade required. You can filter the view by cluster tier (Premium, Standard, or Free) to understand exposure by tier and prioritize accordingly. For clusters that are out of support but LTS eligible, a single Enable LTS for Eligible Clusters button lets you act immediately without navigating away. Kubernetes Center brings this into a single, always-on view so platform teams can: Catch version drift before it becomes an incident Spot misconfiguration patterns across clusters, not just within one Act on recommendations without switching tools Report on compliance posture without manual aggregation Try It Out These features are available now in Kubernetes Center in the Azure portal. → Open Security -Kubernetes Center in the Azure portal We'd love to hear what you think. Try the new security and version views with your clusters and share your feedback directly through the portal using the feedback button. FAQ Do I need Microsoft Defender for Containers enabled to use the security features? Yes. Security vulnerabilities, runtime alerts, and misconfiguration data are powered by MS Defender for Containers. Kubernetes Center will show you if any clusters don't have it enabled so you can quickly close that gap. Does this work across all my subscriptions and clusters? Kubernetes Center aggregates data across all AKS clusters you have access to. Make sure you have the appropriate RBAC permissions across the subscriptions you want visibility into. What is LTS and should I enable it for eligible clusters? Long Term Support (LTS) extends the supported lifecycle of a Kubernetes version beyond its standard window. It's available for clusters on eligible versions running the Premium tier. If you have clusters showing "Out of support, LTS eligible," enabling LTS is the fastest way to restore support coverage while you plan a full version upgrade. Is there a cost to use Kubernetes Center? Kubernetes Center itself is part of the Azure portal experience and there is no additional charge. Note that Microsoft Defender for Containers, which powers the security features, is a paid add-on. See the Defender for Containers pricing page for details. Where can I learn more about the Kubernetes version lifecycle? See the AKS Kubernetes version support policy documentation for full details on version support windows, LTS eligibility, and upgrade guidance.716Views1like0CommentsCaliptra 2.1: An Open-Source Silicon Root of Trust With Enhanced Protection of Data At-Rest
Introducing Caliptra 2.1: an open-source silicon Root of Trust subsystem, providing enhanced protection of data at-rest. Building upon Caliptra 1.0, which included capabilities for identity and measurement, Caliptra 2.1 represents a significant leap forward. It provides a complete RoT security subsystem, quantum resilient cryptography, and extensions to hardware-based key management, delivering defense in depth capabilities. The Caliptra 2.1 subsystem represents a foundational element for securing devices, anchoring through hardware a trusted chain for protection, detection, and recovery.8.4KViews1like0Comments