hybrid
2003 TopicsGovern, Secure, and Operate Anywhere with Azure Arc
Over the past year, the way the world does work has shifted significantly. Agents have gone mainstream, infrastructure is being purpose-built for AI inferencing, and expectations around data sovereignty continue to grow. While the goals for our systems are evolving, one need remains constant: centralized visibility and control of your IT infrastructure, wherever your workloads run. Hybrid by default With geopolitical pressures and disaster risks rising, enterprises are increasingly choosing distributed infrastructure deliberately for strategic workloads to meet requirements for latency, data gravity, AI inferencing, resiliency, sovereignty, operational continuity, and regulation. Common drivers include: Unreliable connectivity: Remote sites and factory locations often operate with unreliable connections and high latency. Regulations: State, corporate, and industry rules on sovereignty and data mean some workloads must stay where they are. Acquisitions: Legacy systems and inherited environments from organic growth and team-level choices need to be integrated, not rebuilt. Optimization: Compute and power costs vary by location, so workloads need to be placed with economics in mind. As a result, many customers juggle multiple tools to manage on-premises, multicloud, and multi-OS environments, often from one central operations team. What those teams want most is consistency. One platform for your entire estate Azure Arc extends Azure management to servers and Kubernetes clusters wherever they run, so organizations can unify hybrid, multicloud, and edge estates on one platform for operations, innovation, and insights. That's where cloud-native innovation shows up. Beyond basic health and status monitoring, Azure Arc lets you collect richer operational, security, and configuration data and query it at massive scale. It also centralizes governance with consistent tags and unified identity and access management through RBAC. With centralized insights teams are able to close vulnerabilities faster, fix compliance drift, and maintain day-to-day operations, including modern patching, across hybrid and multicloud estates with better control. At Ignite 2026, we're expanding capabilities to help you see more, control more, and secure more, wherever your infrastructure runs. See Everything- Unify your distributed estate with Azure Arc You can't govern what you can't see, and full visibility used to mean deploying the Azure Arc agent to every machine first. However, at Ignite 2026 we are introducing Improved onboarding and discovery help you understand your estate and extend Azure management where it matters most. Onboarding and discovery: Google Cloud (GCP) connector (generally available): Multicloud shouldn't mean managing in silos. In addition to the AWS connector we announced last Ignite, we now support bringing all your Google Cloud resources into Azure for centralized visibility and control. Kubernetes Onboarding Solutions (Public Preview): Bring Kubernetes clusters running in Google Kubernetes Engine and Amazon EKS under Azure Arc through the Multicloud Connector. Clusters in Google Cloud and AWS join the same inventory and management as the rest of your estate, so platform teams can govern every cluster from one place. Microsoft Endpoint Configuration Manager (MECM) connector enabled by Azure Arc (preview): Bring years of Configuration Manager server inventory into Azure, with visibility into machines, software, and configuration without installing an agent on every machine. Then extend Arc management only where you need it. Visualize inventory and gain insights: Once machines are connected, the next question is what's running on them. Machine Inventory (preview): A central, Azure-native view of what's inside your Azure VMs and Arc-enabled servers, including applications, services, certificates, users, groups, and Windows OS details. Questions like "Which servers still run this app version?" or "Which certificates are about to expire?" no longer require scripts and spreadsheets. Azure Resource Manager MCP server (preview): AI agents are becoming a new way to manage Azure, and the ARM MCP server gives them a governed way to do it. Through the Model Context Protocol, agents can query resources, deploy ARM templates, create or update resources, inspect schemas, and analyze costs. And because Azure Arc-enabled resources appear in Azure Resource Manager, agents can query your hybrid estate the same way they query Azure, turning "Which on-premises servers are missing the latest agent?" into a natural-language request. And with the new Machine Configuration centralized UI (preview), users get a fleet-wide view of posture and compliance, guided setup for scenarios like custom policy and security baselines, and one-step enablement at the subscription scope. Simplify Operations- Manage, govern, operate, & secure Manage, govern and operate: Day-to-day operations are where hybrid estates take the most manual effort. New capabilities reduce that effort so teams can focus on innovation, not upkeep. Essential Machine Management, Day N operations (preview): Enable a subscription, and all its VMs and Arc-enabled servers are automatically enrolled and configured with curated management features, including monitoring, update management, security baseline auditing, and change tracking and inventory. Day N updates go beyond onboarding, with new dashboards that surface top issues at the subscription level and a central view of which subscriptions are onboarded to EMM. VM Applications for Azure Arc-enabled machines (preview): Package and deploy third-party and internal applications, agents, and middleware to Azure VMs and Arc-enabled servers without rebuilding images. Applications are stored centrally and versioned, so software deploys consistently across thousands of servers with less image management overhead. Azure Arc automatic agent upgrade (generally available): With this feature Microsoft automatically manages Azure Connected Machine agent updates, rolling them out in batches across regions during off-peak hours, with no server restart required. Turn it on across your estate with Azure Policy to keep your fleet current with no manual work. Upgrade Insights for Azure Arc-enabled Kubernetes (preview): Kubernetes version upgrades are a common cause of outages. Upgrade Insights checks clusters beforehand and flags deprecated APIs, compatibility issues, readiness problems, and configuration blockers, so platform teams can upgrade with confidence. DISA STIG audit (preview) and CIS Windows audit (generally available): Audit servers against Defense Information Systems Agency Security Technical Implementation Guides (DISA STIGs), and Windows Server 2022 and 2025 against CIS benchmarks, with hybrid support through Azure Arc. Defense, public sector, and other regulated organizations can verify compliance with the standards they're measured against, using one consistent assessment across on-premises, Azure, and other clouds. Secure and remediate: Security has to cover the whole estate, from the hardware up. These announcements strengthen identity, close compliance gaps, and speed recovery when things go wrong. TPM-backed identity for Azure Arc-enabled servers (preview): Instead of storing managed identity credentials on local disk, the Azure Connected Machine agent can now use the machine's physical TPM or virtual TPM (vTPM) as a hardware-backed root of trust. Credentials are protected against exfiltration, including by privileged users, which matters most in regulated and high-security environments. User-assigned managed identity (UAMI) for Azure Arc-enabled machines (preview): Create one identity, grant it access once, and assign it across many machines, instead of relying on per-machine system-assigned identities. This simplifies access management at scale and matches how customers already manage identity for Azure VMs. Microsoft Defender for Cloud + CIS Benchmark remediation (preview): Azure Policy and Machine Configuration assess Windows and Linux servers against CIS benchmarks and Azure security baselines, with findings and remediation in Azure Policy and Defender for Cloud. Azure Arc applies the same assessment on-premises and in other clouds, so you can audit and remediate consistently across your hybrid estate. Windows Recovery Environment (WinRE) with Quick Machine Recovery (preview): When a server can't boot, every minute offline counts, and remote sites are hard to reach. One Azure Policy now turns on WinRE and QMR across eligible Windows Server 2025 Arc-enabled servers, so they can self-repair startup problems and get critical workloads back online faster. A new Windows Recovery tab in the portal shows which servers are protected or recovering. For widespread boot issues, QMR can apply a Microsoft-provided fix through Windows Update. Recovery is best effort, so not every failure has an automated fix. Hotpatch enabled by Azure Arc is now free for Windows Server 2025: Patching shouldn't force a choice between security and uptime. Hotpatch applies updates without restarts, cutting reboots on Windows Server 2025 from roughly monthly to about four planned reboots per year (the quarterly baselines), while security content lands continuously in between. There's no separate SKU and no premium tier, just the Azure Arc onboarding step. Run Apps and Data anywhere- Consistent deployment across boundaries GitOps-based deployments with Azure Kubernetes Fleet Manager and Flux extension (preview): Fleet Manager now integrates with the Flux extension, so platform teams can roll out applications and configurations through GitOps to AKS and Arc-enabled Kubernetes clusters across Azure, on-premises, AWS, and Google Cloud. Manage Kubernetes at scale from a single control plane, with safe upgrades and multi-cluster operations. All centralized for scale Each capability is useful on its own. Together, they let you manage your whole estate the same way, at any size. Azure Arc projects every server, cluster, and cloud resource into Azure Resource Manager, so the same tools work everywhere: Azure Policy, Defender for Cloud, Machine Configuration, Update Manager, and now AI agents through MCP. That holds whether you manage ten servers or a hundred thousand, in a factory, a sovereign datacenter, or a third-party cloud. Hybrid by default doesn't have to mean complex by default. With Azure Arc, you can govern, secure, and operate anywhere, all from a single pane of glass. Want to learn more? Join the Arc Monthly Customer Forum Connect with the Azure Arc product team and hear from other customers on how they use Azure Arc. Azure Arc on Microsoft Learn: Explore documentation, tutorials, and technical guidance. Azure Arc Tech Community blog: Stay up to date on product news and announcements. Azure Arc on Microsoft Azure: Discover how Azure Arc helps simplify hybrid, multicloud, and edge management. FULL SCHEDULE: Explore Azure Arc sessions at Ignite Tuesday, November 17 3:45–5:00 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP 4:10–4:55 PM | TT1691: Audit-ready everywhere: Governance for hybrid and edge AI Wednesday, November 18 9:00–9:45 AM | TT1694: Discover everything: Unified hybrid and edge AI asset inventory 10:15–11:00 AM | BRK421: Operate a global AKS fleet across regions, edge, and sovereign clouds 12:00–1:15 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP Thursday, November 19 10:45 AM-12:00 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP 1:30–2:15 PM | BRK413: Govern, secure, and operate anywhere with Azure Arc (News from Azure Arc) Friday, November 20 9:00–10:15 AM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP49Views1like0CommentsAnnouncing SQL Server 2025 Preview Support on Ubuntu 26.04 LTS
We are excited to announce preview support for SQL Server 2025 on Ubuntu 26.04 LTS, starting with SQL Server 2025 CU11. This brings SQL Server 2025 to Canonical's latest long-term support release, giving developers and organizations an opportunity to evaluate SQL Server on a modern Ubuntu platform. Alongside this announcement, this blog covers: how to install SQL Server 2025 on Ubuntu 26.04, and the simplified Azure deployment experience for SQL Server on Linux Azure VMs. Preview note: SQL Server 2025 support on Ubuntu 26.04 is currently in preview and is intended for evaluation and testing, not production workloads. Supported platforms and package availability continue to evolve - always check the Release notes for SQL Server on Linux for the latest supported OS matrix. Why Ubuntu 26.04 support matters Organizations increasingly standardize their infrastructure on long-term support (LTS) operating system releases to maintain consistency across their environments. With SQL Server 2025 support on Ubuntu 26.04, you can begin evaluating your database workloads on Canonical's latest LTS release while taking advantage of improvements in the underlying operating system. SQL Server 2025 also introduces capabilities such as native vector search and external AI model integration, enabling developers to build modern AI-enabled applications using their existing SQL Server data. This preview provides an opportunity to validate application compatibility, evaluate deployment configurations, and prepare for future adoption. One SQL Server engine across deployment environments SQL Server provides a consistent core database engine across Windows and Linux, allowing organizations to use familiar database capabilities and tools across different environments. SQL Server on Linux can be deployed on physical servers, virtual machines, and supported container platforms, giving customers flexibility in how they manage their database infrastructure. Ubuntu 26.04 preview support expands the operating system options available for evaluating SQL Server 2025. Installing SQL Server 2025 on Ubuntu 26.04 You can install SQL Server 2025 directly on an Ubuntu 26.04 machine, whether it is running on Azure, another cloud platform, or on-premises. The installation follows the familiar SQL Server on Ubuntu workflow: configure the Microsoft package repository, install SQL Server, and complete the initial setup. Step 1: Import Microsoft’s GPG key First, install the required utilities and import Microsoft's package signing key. # Ensure curl is available, then import the Microsoft signing key sudo apt-get update && sudo apt-get install -y curl curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft-prod.gpg Step 2: Register the SQL Server 2025 repository Note: The Ubuntu 26.04 package repository configuration is temporarily unavailable, and we are working on a resolution. In the meantime, you can continue using the container image: mcr.microsoft.com/mssql/server:2025-CU11-ubuntu-26.04-preview Configure the Microsoft package repository for SQL Server 2025 on Ubuntu 26.04. # Register the SQL Server 2025 repo for Ubuntu 26.04 curl -fsSL https://packages.microsoft.com/config/ubuntu/26.04/mssql-server-preview.list | sudo tee /etc/apt/sources.list.d/mssql-server-peview.list Step 3: Install SQL Server 2025 Update the package index and install the SQL Server engine. sudo apt-get update sudo apt-get install -y mssql-server Step 4: Configure SQL Server Run the SQL Server configuration utility to select your edition, accept the license terms, and configure the system administrator password. # Choose edition, accept the license terms, set the SA password sudo /opt/mssql/bin/mssql-conf setup # Verify the service is running systemctl status mssql-server --no-pager Step 5: Install SQL Server command-line tools (optional) You can also install the SQL Server command-line utilities, including sqlcmd and bcp. First, register the Microsoft production repository. # Add the prod repo, then install sqlcmd / bcp (mssql-tools18) curl -fsSL https://packages.microsoft.com/config/ubuntu/26.04/prod.list | sudo tee /etc/apt/sources.list.d/mssql-release.list sudo apt-get update sudo apt-get install -y mssql-tools18 unixodbc-dev That’s it. With SQL Server 2025 installed on Ubuntu 26.04, you can connect using familiar tools such as SQL Server Management Studio (SSMS), the MSSQL extension for Visual Studio Code, or sqlcmd. You can now begin exploring SQL Server 2025 capabilities and validating your applications on Ubuntu 26.04. Simplifying SQL Server on Linux deployments in Azure In addition to expanding operating system support, we've introduced a more flexible way to deploy SQL Server on Linux Azure Virtual Machines. Traditionally, customers deployed SQL Server on Linux using preconfigured Azure Marketplace images that included both the operating system and SQL Server. The new script-based deployment experience simplifies this approach by allowing customers to provision a Linux VM and configure SQL Server as part of the deployment process. Instead of relying on a preconfigured SQL Server image, customers can start with a supported Linux operating system image and select their SQL Server configuration. How script-based deployment works If you prefer a SQL-first deployment experience, the Azure SQL hub provides a streamlined way to deploy SQL Server on Linux Azure VMs. Go to the Azure SQL hub at aka.ms/azuresqlhub. Under SQL Server, select SQL Server on Azure VMs, and then select + Create. Select the operating system for your deployment. You will be redirected to the Create a virtual machine experience. Your operating system selection is automatically carried forward, and Install SQL Server option is enabled by default under the Advanced tab. Configure the remaining VM and SQL Server settings. You can also use advanced configuration to upload a custom mssql.conf file, configure SQL connectivity, enable Azure Key Vault integration, and the tuned performance profile. Select Review + create, review the configuration summary, and then select Create. Azure provisions the VM, installs and configures SQL Server through the same script-based deployment flow, and automatically registers the VM with the SQL IaaS Agent extension. Getting started & reference Install on Ubuntu: Quickstart: Install SQL Server and create a database on Ubuntu Installation guidance: Installation guidance for SQL Server on Linux Supported platforms: Release notes for SQL Server on Linux Containers: Deploy and connect to SQL Server Linux containers SQL IaaS Agent extension (Linux): Overview · Register a Linux SQL Server VM Wrapping up Preview support for SQL Server 2025 on Ubuntu 26.04 LTS marks another step in expanding deployment flexibility for SQL Server on Linux. Together with the new script-based deployment experience on Azure VMs and integration with the SQL IaaS Agent extension, customers have more options to deploy and manage SQL Server on Linux. We encourage you to explore SQL Server 2025 on Ubuntu 26.04 in your test environments and share your feedback to help us continue improving the experience.42Views2likes0CommentsAnnouncing the Configuration Manager connector for Azure Arc (preview)
If you run Microsoft Configuration Manager, you already have one of the best records of your servers: what's deployed, which roles are running and which applications are installed. Until now, getting that picture into Azure meant installing the Azure Connected Machine agent on every machine. For many teams, that's a big job just to answer the question "what do we have?" Today we're excited to announce the public preview of the Configuration Manager connector for Azure Arc. The connector runs on-premises and brings inventory from your Configuration Manager-managed machines into Azure. You choose the device collections to include. The connector then uses their inventory data to show those machines in Azure, with no agent needed on each managed machine. Why we built it Customers keep telling us they want one view of their hybrid estate in Azure. They don't want to deploy agents across thousands of servers before they get any value. You've already invested in Configuration Manager, and that investment should carry forward. Configuration Manager stays the source of inventory and the management authority for those machines. Azure gets a connected view of them that you can query. How it works You deploy the connector once, on your Configuration Manager site server, not on each managed machine. The site server connects to Azure Arc using the Azure Connected Machine agent. You select device collections from the Configuration Manager console. The connector makes the selected machines and their inventory visible in Azure. Connected inventory includes server roles, services and applications, taken from the data already in Configuration Manager. What you can do with it See your Azure resources, Azure Arc-enabled servers and Configuration Manager machines in one inventory view. Query machines, roles, services and applications at scale with Azure Resource Graph. You don't need a Log Analytics workspace. Start with a pilot collection, check the results, then expand at your own pace. Use the inventory to decide which machines should be fully onboarded to Azure Arc next. Inventory today, full Azure management enabled by Azure Arc when you're ready The connector shows inventory as read-only. It doesn't move management of the machines to Azure, and it doesn't deploy the agent to them. When you want Azure Arc features that need an agent on each machine, such as update management, security, monitoring or Extended Security Updates, you can still use the existing Configuration Manager onboarding options: the PowerShell onboarding script a custom task sequence Getting started You'll need: An Azure subscription, a resource group and your Microsoft Entra tenant ID. Permission to connect the site server to Azure Arc and to manage connected inventory resources in the target resource group. Admin access to the site server, with rights to approve and install console extensions. Azure Connected Machine agent version 1.70 or later on the site server, plus Windows PowerShell 5.1. A small device collection for your first test. To set it up: In the Azure portal, open Azure Arc. Under Supported environments, select On-premises connectors, then Create. Download the onboarding script and run it as Administrator on the site server. Approve the console extension and choose your collections. Full guidance and sample queries: Configuration Manager connector for Azure Arc (preview) This is just the beginning Configuration Manager is a natural place to start, because it's where many of you keep the most complete picture of your servers. But it isn't the only system that knows your servers well. Our goal is simple: wherever your on-premises inventory lives today, Azure Arc should be able to see it, without asking you to start over. Keep an eye on this space. Tell us what you think This is a preview, and your feedback directly shapes what we do next. Try the connector with a pilot collection and tell us what works, what doesn't and what you'd like to see. Leave a comment below or use the feedback link in the Azure portal.71Views1like0CommentsGet your Arc-enabled Windows servers back online faster with Windows Recovery Environment (preview)
When a server hits a critical failure like a stop error, every minute offline counts, and getting to a machine in a remote datacenter or branch office is rarely quick. That's where Windows Recovery Environment (WinRE) comes in. This built-in recovery environment starts automatically when Windows can't boot, letting Windows Server diagnose and repair startup problems on its own, so your critical workloads have a safety net and your team can get back up fast. Now, you can enable WinRE and centrally monitor recovery status across your Arc-enabled servers, right from the Azure portal. What's new Previously, Azure Arc offered two separate Azure policies: one to audit whether WinRE is enabled and one to configure it. Today, we're excited to introduce a new Azure policy that, when enabled, will give you a centralized view of your machines' health status, along with automatic remediation capabilities. The new Configure Quick Machine Recovery (QMR) on Windows machines policy enables WinRE and QMR for your 2025 Arc-enabled Windows servers. Because it's delivered through Azure Policy, you can turn on recovery protection across your entire fleet at once, without touching individual machines. For widespread boot issues, QMR streamlines recovery by finding a Microsoft-provided fix through Windows Update, applies it, and restarts without manual intervention. It is important to note that QMR is best-effort feature, so an automated remediation might not exist for every failure. A centralized experience in the portal The new Windows Recovery (preview) tab under Machine configuration in the Azure portal lets you enable WinRE and QMR on eligible machines, see which servers have it enabled, and spot machines currently recovering, ultimately providing a central place to manage these machines. Pricing The Azure Policy carries no additional charge for servers covered by: Windows Server 2016 Extended Security Updates Microsoft Defender for Servers Plan 2 Windows Server Software Assurance attestation Windows Server pay-as-you-go licensing Other servers incur Machine Configuration charges. To check whether your servers have Software Assurance attestation, see Windows Server Management enabled by Azure Arc. Get started Deploy and assign the following Azure Policy to Azure Arc-enabled servers in your existing subscription: Configure Quick Machine Recovery (QMR) on Windows machines (preview). For more information on prerequisites and step-by-step guidance, please visit Enable Windows Recovery Environment and Quick Machine Recovery through Azure Arc.40Views1like0CommentsSimplify Kubernetes operations with Upgrade Insights and GitOps with Azure Kubernetes Fleet Manager
As organizations expand their Kubernetes environments, operating clusters consistently becomes increasingly challenging. Platform teams may be responsible for hundreds or even thousands of clusters distributed across Azure, on-premises datacenters, edge locations, and other clouds. At this scale, two challenges become particularly important: keeping Kubernetes clusters safely up to date and consistently deploying applications and configuration across those clusters. We’re introducing new capabilities to help platform teams address both: Upgrade Insights for Azure Arc-enabled Kubernetes (In public preview), helps teams assess Kubernetes upgrade readiness and identify potential issues before beginning an upgrade. Flux GitOps integration with Azure Kubernetes Fleet Manager (In public preview), brings GitOps together with Fleet Manager workload placement to simplify how applications and configurations are delivered across Kubernetes fleets. Together, these capabilities help platform teams establish a more consistent approach to managing both Kubernetes infrastructure and applications across distributed environments. Understand upgrade risks before you upgrade Kubernetes upgrades can introduce risk when applications still depend on deprecated APIs, cluster components aren't compatible with the target Kubernetes version, or configurations prevent workloads from being safely moved during an upgrade. Upgrade Insights for Azure Arc-enabled Kubernetes helps teams identify these issues earlier by assessing upgrade readiness across three key areas: Deprecated Kubernetes APIs: Identifies workloads and controllers using APIs that may be deprecated or removed in the target Kubernetes version. Component compatibility: Evaluates commonly used Kubernetes components, such as cert-manager, Istio, Cilium, and containerd, for compatibility with the target version. Upgrade readiness: Identifies configuration issues, such as Pod Disruption Budgets, that could interfere with node drains and upgrades. For teams operating Kubernetes at scale, these insights provide a centralized way to understand which clusters are ready to upgrade, and which require remediation first. For Azure Arc-enabled Kubernetes, Upgrade Insights is advisory. It helps operators understand potential upgrade risks while leaving the actual Kubernetes upgrade under the control of the underlying Kubernetes platform. Simplify GitOps across Kubernetes fleets Keeping Kubernetes infrastructure current is only one part of operating at scale. Platform teams also need a consistent way to deploy applications and configuration across many clusters. The Flux extension integration with Azure Kubernetes Fleet Manager brings GitOps together with Fleet Manager's multi-cluster workload placement capabilities. Flux runs on the Fleet Manager hub cluster and reconciles application manifests and Fleet resources from a Git or OCI source. Fleet Manager then evaluates placement policies and distributes the appropriate resources to member clusters. The responsibilities are straightforward: Git or OCI provides the source of truth. Flux provides GitOps reconciliation. Fleet Manager determines where resources should run across the fleet. This means application definitions don't need to identify every destination cluster individually. Teams can define the desired state and placement intent, while Fleet Manager determines which clusters should receive the resources. Author once. Reconcile through GitOps. Place across the fleet. Bringing upgrade readiness and application management together Together, Upgrade Insights and the Flux integration with Fleet Manager address two important challenges for platform teams operating Kubernetes at scale. Upgrade Insights helps teams understand whether their clusters and workloads are ready for Kubernetes upgrades before changes are introduced. Flux and Fleet Manager provide a scalable GitOps model for defining application state and placing those applications consistently across a changing fleet of clusters. As Kubernetes environments grow, platform teams need to understand what is ready to change, where that change should be applied, and how to manage it consistently across the fleet. Upgrade Insights provides visibility before infrastructure changes, while Flux and Azure Kubernetes Fleet Manager provide a scalable foundation for managing applications across the Kubernetes estate. Attending Ignite 2026? See related sessions and resources below. Tuesday, November 17 3:45–5:00 PM | LAB724 | Govern your estate with Azure Arc and Azure Resource Manager MCP 4:10–4:55 PM | TT1691 | Audit-ready everywhere: governance for hybrid and edge AI Wednesday, November 18 9:00–9:45 AM | TT1694 | Discover everything: Unified hybrid and edge AI asset inventory 10:15-11:00 AM | BRK421 | Operate a global AKS fleet across regions, edge, and sovereign clouds 12:00–1:15 PM | LAB724 | Govern your estate with Azure Arc and Azure Resource Manager MCP Thursday, November 19 1:00–2:15 PM | LAB724 | Govern your estate with Azure Arc and Azure Resource Manager MCP 1:30–2:15 PM | BRK413 | Govern, secure, and operate anywhere with Azure Arc Friday, November 20 9:00–10:15 AM | LAB724 | Govern your estate with Azure Arc and Azure Resource Manager MCP Learn more: https://aka.ms/Ignite26/ArcBlog FAQ: 1. How can organizations assess Kubernetes upgrade readiness across hybrid and multicloud environments? Organizations can use Upgrade Insights for Azure Arc-enabled Kubernetes to assess upgrade readiness across Kubernetes clusters running on-premises and in other clouds. Upgrade Insights identifies potential issues, including deprecated Kubernetes APIs, incompatible components, and configuration problems that could disrupt upgrades. These insights help platform teams identify and address risks before initiating Kubernetes version upgrades. 2. What is Upgrade Insights for Azure Arc-enabled Kubernetes? Upgrade Insights for Azure Arc-enabled Kubernetes is a capability in public preview that helps platform teams identify potential Kubernetes upgrade risks before updating cluster versions. It assesses deprecated API usage, component compatibility, and configuration issues such as Pod Disruption Budgets. Upgrade Insights provides advisory recommendations, while the underlying Kubernetes platform remains responsible for executing upgrades. 3. How does Azure Arc help organizations manage Kubernetes clusters across multiple clouds? Azure Arc extends Azure management capabilities to Kubernetes clusters running outside Azure, including on-premises datacenters and other cloud environments. With Azure Arc-enabled Kubernetes, organizations can bring distributed clusters into a common management model. Combined with Azure Kubernetes Fleet Manager, platform teams can coordinate workload placement and apply consistent application configurations across their Kubernetes environments. 4. How does Flux GitOps integration with Azure Kubernetes Fleet Manager simplify application deployment? Flux GitOps integration with Azure Kubernetes Fleet Manager helps platform teams deploy applications and configurations consistently across multiple Kubernetes clusters. Flux reconciles application manifests and Fleet resources from a Git or OCI source on the Fleet Manager hub cluster, while Fleet Manager uses placement policies to determine which member clusters receive those resources. This reduces the need to manage deployment destinations individually and supports a more scalable approach to multi-cluster application management. 5. What is the difference between Azure Arc-enabled Kubernetes and Azure Kubernetes Fleet Manager? Azure Arc-enabled Kubernetes extends Azure management capabilities to Kubernetes clusters running outside Azure, including on-premises and multicloud environments. Azure Kubernetes Fleet Manager focuses on managing groups of Kubernetes clusters together, providing capabilities such as workload placement, coordinated updates, and fleet-level resource management. Together, they help organizations establish a more consistent approach to managing distributed Kubernetes infrastructure and applications.30Views0likes0CommentsAnnouncing General Availability of GCP support in the Azure Arc Multicloud Connector
We're excited to announce the general availability of Google Cloud Platform (GCP) support in the Multicloud Connector enabled by Azure Arc! For teams that have been evaluating the GCP connector in Public Preview, you can build on the experience you already know: discover supported Google Cloud resources, maintain a shared inventory in Azure, and onboard eligible virtual machines to Azure Arc without moving your workloads. Integrated Azure Cloud Shell support also simplifies connector setup by letting you authenticate to Google Cloud and run setup commands directly from the Azure portal, reducing context switching and the need to prepare a separate execution environment. Build on your existing Multicloud management experience The core workflow remains familiar: connect your Google Cloud environment, choose your solutions, and define the scope of resources you want to discover and onboard. The Inventory solution maintains Azure representations of supported Google Cloud resources through periodic synchronization. Teams can query those resources alongside Azure and AWS resources through Azure Resource Graph, using imported metadata to understand their connected environments. Azure tags and Azure policies can also be applied to those representations to help organize and govern inventory. With Arc VM onboarding, eligible Google Cloud VMs are connected to Azure Arc through installation of the Azure Connected Machine agent. Supported region and GCP label filters help teams control onboarding scope, while periodic synchronization allows newly discovered machines that meet the prerequisites and configured filters to be onboarded automatically. For Kubernetes workloads, Arc GKE onboarding (Public Preview) is also available now, bringing discovery and Azure Arc onboarding together for eligible Google Kubernetes Engine clusters. Choose the solutions that match your workloads The following Multicloud Connector solutions are available for GCP, covering resource inventory, Azure Arc onboarding, security configuration assessment, licensing, and Extended Security Updates. Supported solution What it enables Inventory View supported Google Cloud resources in a shared inventory and query their Azure representations through Azure Resource Graph. Arc VM onboarding Connect eligible GCP VMs to Azure Arc, enabling access to services such as Azure Monitor and Microsoft Defender for Cloud when configured. Arc GKE onboarding (preview) Discover and connect eligible GKE clusters to Azure Arc-enabled Kubernetes. Security Baselines (preview) Audit connected machines against security baselines, including CIS Benchmarks and the Azure security baseline, powered by Machine Configuration. SQL Server licensing and ESU Manage SQL Server licensing and subscribe to Extended Security Updates for eligible SQL Server instances. Windows Server ESU Attach an Extended Security Updates license to eligible Azure Arc-enabled Windows Server machines. Security Baselines, SQL Server licensing and ESU, and Windows Server ESU require Arc VM onboarding, along with applicable configuration, eligibility, and licensing requirements. For more information about these solutions, their prerequisites, and how to get started, see our companion article: Expanding Multicloud Management with Azure Arc | Microsoft Community Hub. Take the next step Ready to get started? Follow the Multicloud Connector setup documentation to connect your Google Cloud environment.26Views0likes0CommentsAzure VM Applications for Azure Arc-enabled servers now in Public Preview
VM Applications let organizations package, version, share, deploy and manage applications on VMs using Azure Compute Gallery. Today, we’re announcing the Public Preview of VM Applications for Azure Arc-enabled servers, extending these capabilities beyond Azure VMs to servers running on-premises, at the edge, and in other clouds. Customers can now publish custom or third-party applications to Azure Compute Gallery and deploy them across Azure and Arc-enabled servers. Key Benefits One application management plane across Azure, hybrid, and multi-cloud servers, reducing tooling sprawl and operational complexity. Private gallery: Host your organization’s line of business applications and third-party applications in a private, centrally managed gallery. Improved security & privacy: Share applications using RBAC‑controlled private galleries, control which versions are approved for organizational use, enforce required application and versions using Azure Policies, and rapidly publish and patch critical security updates. Built‑in failure resiliency: Reduce risk of CDN failures and improve availability with automatic regional replication. Support gradual rollouts and fast rollback to mitigate issues from bad releases. Flexible operations at any scale: Deploy declaratively with templates & policies, manage individual servers with PowerShell or CLI, or manage entire fleet with Portal. Centralized governance and enforcement using Azure Policy and Azure Resource Graph for auditing, compliance, and fleet‑wide visibility. Getting started To use VM Applications on Azure Arc-enabled servers, you’ll need servers connected to Azure Arc and a compatible VM Application published in Azure Compute Gallery, with its version replicated to the target servers’ region. Review the prerequisites for supported agent versions, networking, and permissions. Learn more about VM Applications, including application packaging, versioning, and distribution. When you’re ready, deploy your first application with the publishing and deployment guide.41Views0likes0CommentsSecuring Azure Arc-enabled servers with TPM-backed identity and user-assigned identities (preview)
As organizations expand their hybrid environments, protecting server identities becomes increasingly critical. Azure Arc-enabled servers use managed identities to securely access Azure services, and until now those identity credentials have been stored on disk and protected by local access controls. Each server has also been limited to a single system-assigned identity that is created with the server and deleted with it. Today we are excited to announce two capabilities that work together to change that: TPM-backed identity, which protects managed identity credentials with the Trusted Platform Module (TPM) or virtual TPM (vTPM), and user-assigned managed identity support, which lets you connect a server with one or more identities you create and manage yourself. Both are available in public preview today. TPM-backed identity: hardware protection for server credentials With TPM-backed identity, the managed identity's private key is sealed by the server's TPM. By onboarding servers with TPM-backed key storage, you gain: Hardware-backed credential protection, so the identity key is sealed by a hardware component instead of relying on local access controls alone. Unexportable credentials, so even privileged users cannot extract or export the identity material from the TPM. You opt in at onboarding with a single parameter, --identity-key-store, and the agent handles the rest of the process transparently. User-assigned managed identities: identities you control A system-assigned identity is tied to the life of one server. A user-assigned managed identity is a standalone Azure resource that you create, govern and reuse. With this preview you can: Connect a server with one or more existing user-assigned managed identities, up to 10 per server. Choose whether the server uses only user-assigned identities or keeps a system-assigned identity alongside them. Add, replace or detach user-assigned identities after onboarding, without reconnecting the server. Add a system-assigned identity later, even to a server onboarded with only user-assigned identities. Because a UAMI exists independently of any one machine, you can grant its role assignments once and attach the same identity to many servers or rotate a server to a new identity on your own schedule. Better together TPM-backed identity and user-assigned managed identities bring hardware-backed protection and flexible identity management together. UAMI onboarding requires TPM-backed key storage, helping protect credentials while giving you control over which identities your servers use. The result: access can evolve with your organization while credential protection remains anchored to the server’s hardware. Get started To get started, explore the prerequisites, onboarding commands and verification steps for TPM-backed identity and user-assigned managed identities for Azure Arc-enabled servers.32Views0likes0CommentsStrengthen SQL Server security on Azure Local with confidential VMs (In Preview)
SQL Server holds some of the most sensitive data an organization runs, including the business data that local AI applications and agents query. Azure Local provides a Microsoft-managed, distributed infrastructure platform for running SQL Server in virtual machines at customer locations, so data can stay on premises. Data at rest and in transit is commonly protected, but while SQL Server processes queries, the data it works with sits in memory. Confidential virtual machines (CVMs) on Azure Local help protect it there. Protecting SQL Server requires more than securing the database engine. With a standard VM, the host operating system, the hypervisor, and anyone with administrative access to the host all sit inside the trust boundary of the workload. At edge and remote sites with less physical control, that is a lot of trust to place in the infrastructure. CVMs on Azure Local, now generally available on AMD processors and in preview on Intel processors, bring hardware-based memory encryption and attestation to customer-owned edge infrastructure. They provide hardware-based isolation between the VM, the hypervisor, and host management code. SQL Server 2025 runs on Ubuntu 24.04 inside the CVM. For SQL Server workloads, the value is straightforward: help keep data confidential while it is in use, even from the infrastructure it runs on. Where confidential VMs fit Consider CVMs when SQL Server data should stay private from the people and systems that operate on the underlying infrastructure, such as regulated and sovereign data, edge and remote sites, hosted or partner-run clusters, and local AI applications that query sensitive business data. Protect SQL Server data while it is in use CVMs on Azure Local use AMD SEV-SNP or Intel TDX to encrypt guest memory in hardware, so SQL Server's buffer pool and in-memory data stay encrypted and isolated from the host and its administrators. CVMs don't protect against sophisticated physical side-channel attacks, so pair them with physical safeguards at the site. Data on disk, in backups, and in transit still needs SQL Server's own protections. The following table shows how they fit together. What you're protecting Threat Protection SQL Server memory, including the buffer pool Host administrators or a compromised host CVM memory encryption (AMD SEV-SNP or Intel TDX) Operating system disk and boot chain Host-side tampering Integrity-protected image Data, log, and tempdb files A copy of the data disk taken from the host TDE with keys in Azure Key Vault Backups Copies stored outside the VM Backup encryption Network traffic Interception between clients and SQL Server Encrypted connections (TLS) Sensitive columns Privileged database users Always Encrypted Start from an integrity-protected image CVMs follow a clean-room, image-driven model. You build a hardened Ubuntu 24.04 image with SQL Server 2025 installed and enable integrity protection, which helps protect the guest operating system disk and boot chain from host-side tampering. The root file system is read-only, so SQL Server databases, logs, and tempdb live on a separate writable data disk. To maintain the security boundary, guest management isn't supported, so plan guest changes, including SQL Server updates, as new image builds rather than in-place changes. Plan availability around confidential VMs CVMs don't support live migration or failover between nodes in an Azure Local cluster, so plan maintenance around the CVMs on each node, build availability into the database design, and keep regular SQL Server backups outside the VM. Verify the environment with attestation Attestation helps you confirm that SQL Server is running in a genuine confidential environment before you trust it with sensitive data. The CVM produces a hardware-rooted attestation report that Microsoft Azure Attestation validates, so plan cloud connectivity from the site. Get started with SQL Server on confidential VMs Prepare a CVM-ready cluster. Deploy Azure Local 2607 or later on validated AMD or Intel hardware with confidential VMs enabled by following the Azure Resource Manager template guidance. Hardware partners for both include Dell, HPE, and Lenovo. Find specific validated systems in the Azure Local solutions catalog. Build the SQL Server image. Use the integrity-protected CVM image builder in the AzureStack-Tools repository to create an Ubuntu 24.04 image, add SQL Server 2025, and point SQL Server at a separate data disk. Create the confidential VM. Create the CVM from your image with the data disk attached by following the CVM creation and connection guidance. Verify and connect. Verify the CVM with attestation and connect your applications. For detailed guidance, see Deploy SQL Server on Azure Local. Review the confidential VM overview for current limitations. Frequently asked questions How is this different from Always Encrypted? Always Encrypted protects selected columns from anyone without the column keys, including database administrators. A CVM protects all of SQL Server's memory from the host and infrastructure operators. They address different threats, so use both when you need protection from both groups. Can I convert an existing VM into a confidential VM? No. CVMs are created from a purpose-built, integrity-protected image. Create a new CVM and move your databases into it with backup and restore. Does it support SQL Server on Windows? Not yet. This release supports Ubuntu 24.04 guests only. A stronger foundation for sensitive database workloads When SQL Server runs in a confidential VM on Azure Local, its memory is encrypted and isolated from the host, the hypervisor, and infrastructure operators, and attestation provides evidence of that protection before applications connect. That brings confidential computing to SQL Server workloads that need to stay on premises.26Views2likes0Comments