azure arc
317 TopicsAzure Local security: closing the industry standards gap and improving enterprise adoption
Starting with Azure Local, version 2610, you can change a single security setting, keep drift control switched on, and keep your value through solution updates. It’s one of the most common requests we’ve heard from customers since we made Azure Local secure by default, and it ships alongside a baseline update that closes most of the distance to the CIS Benchmark and the DISA STIG. Those two changes belong together. A stricter baseline is only useful if you can live with it, and until now the honest answer for some environments was that you couldn't. Closer alignment with industry standards Most customers don't take a platform's security on our word. Their auditors measure it against the CIS Benchmarks and, in government and defense, the DISA STIG benchmark. Every rule the platform misses becomes an exception someone must document and defend. In finance, healthcare and the public sector, that alignment can be a condition of going to production. So, the closer the baseline sits to those standards from day one, the shorter the path from a new cluster to a live one can be. Version 2610 ships a revisited security payload for Azure Local and Azure Local disconnected operations that better align with the Windows Server 2025 CIS Benchmark and STIG guidance. A domain-joined deployment now evaluates 429 settings, up from 408. A deployment that uses local identities instead of Active Directory evaluates 403, up from 382. Both score higher than before, and you don't have to do anything to get there: the new settings arrive with the solution update, and drift control covers them from that point on. Sovereign private clouds get the same treatment. The infrastructure VM that supports disconnected operations runs the same baseline as the hosts. We compared both versions rule by rule against the CIS Windows Server 2025 Level 1 benchmarks (Member Server v2.1.0 and Stand-alone v2.0.0) on all three deployment types. On CIS: Azure Local, domain-joined, against the Member Server benchmark: from 77% to 87%. Azure Local with local identities, against the Stand-alone benchmark: from 79% to 87%. The disconnected operations infrastructure VM, against the Stand-alone benchmark: from 76% to 88%. The rules we still don't meet are deliberate. Some are needed for Azure Local capabilities to work at all: PKU2U, for example, stays on because cluster operations and Microsoft Entra ID sign-in depend on it. We also dropped settings for components that no longer produce events or that we consider deprecated, rather than collect empty logs. We’ve reviewed each of these overrides with CIS. Set those documented overrides aside and the baseline aligns with more than 99% of the CIS Level 1 rules on every deployment type. STIG tells a similar story. On the disconnected operations infrastructure VM, the DISA SCAP Compliance Checker passes 82% of the automated Windows Server 2025 STIG V2R3 rules, and 92% once the overrides are set aside. Most of what's left are OpenSSH rules from that revision, and we're working through them now. For the Azure Local host, a rule-by-rule review of the baseline against the STIG (V1R1) shows it covers 132 of the 148 automatable rules that apply. Alignment with a benchmark isn't a certification or an accreditation; your assessor still makes that call. That's the commitment we made: close the gap with CIS and STIG, and be clear about every place we still differ. Additional audit metadata in the security baseline The baseline now has answers for two different people. Your auditor wants to know which control each setting satisfies, and a percentage doesn't tell them that. Your security operations team wants to know what the setting actually does, why we evaluate it on Azure Local, what changing it would affect, and whether they're allowed to change it at all. Starting with 2610, the settings file we publish for each deployment type answers both, with seven additional columns on every setting. The mappings speed up your evidence work; they don’t replace your assessment. Hand the first four to your compliance team instead of building that mapping yourself; read the last three before you customize anything: CIS RuleID: the CIS Windows Server 2025 Benchmark recommendation the setting answers. CIS Control: the CIS Controls v8 safeguard, with its Implementation Groups. STIG ID: the DISA Windows Server 2025 STIG rule, to support DoD and federal accreditation work. NIST SP 800-53 Rev 5: the NIST control, useful when you assemble RMF and FedRAMP evidence. Security Impact: what the setting protects against and, where the baseline differs from a benchmark on purpose, why. Change Risk Level: the functional and security consequence of changing the setting, so you know before you change it. Customization Posture: whether Set-AzsSecurity lets you change the setting, and whether it warns you first. Download the 2610 files for domain-joined deployments and for deployments with local identities. Improving drift control and adoption in enterprise environments Until 2610, a customer who needed to adapt a handful of settings to their environment had one option: turn off drift control, which stopped the baseline from being enforced across the whole cluster. Even that didn't last. The next solution update reverted the changes, and only the seven security features you can switch with Enable-AzsSecurity and Disable-AzsSecurity kept their state. Version 2610 adds Set-AzsSecurity on top of those seven toggles. It changes one setting and leaves drift control on for everything else. Run it with -Cluster and Azure Local records your value as cluster policy intent, applies it on every machine in the cluster, and keeps it across solution updates. Drift control then protects your value instead of the baseline value. Backup is a common case. The baseline gives the Backup files and directories right to administrators only, which is what CIS and the STIG ask for. Many enterprises run their backup agent under a dedicated service account, and that account needs the same right. One command adds it on every machine in the cluster and keeps Administrators on the list: Set-AzsSecurity -Type SecuritySettings -SettingName "UserRightsBackupFilesAndDirectories" -Value @("*S-1-5-32-544", "*<backup service account SID>") -Cluster Before anything changes, the cmdlet shows the setting, the value it moves from and to, and where the change applies, then asks you to confirm. Get-AzsSecurityPolicyIntent lists every customization you've recorded. Run Set-AzsSecurity with -Default to put a setting back on the baseline. Without -Cluster, the change applies only to the machine you're connected to and still survives updates. If the same setting also has cluster intent, the cluster value wins. Settings that stay protected Some settings hold the platform together, and Set-AzsSecurity won't change them: credential protection, the signed boot chain and virtualization-based security, the host firewall, the minimum SMB version, remote management over WinRM, and Defender Antivirus real-time protection. When you target one, the cmdlet names the setting it rejected and writes nothing. No intent is recorded, and support can see the attempt. We would rather say no up front than let a change break an update three months later, when nobody remembers making it. The list will change as the platform does, so the documentation below is the place to check. What to do next Update to 2610 to pick up the new baseline. Download the settings list for your deployment type and run it past your own CIS or STIG scanner. Where your policy needs a different value, set it with Set-AzsSecurity and keep drift control on. Start with these pages: Manage security defaults on Azure Local Customize individual security settings Settings you can't customize View and download security settings229Views1like2CommentsBuilding a Trusted Ecosystem for Sovereign Private Cloud: Azure Local validated partner solutions
When organizations move critical workloads to Azure Local, the first question usually isn't about the platform. It's about everything that runs on and around it: Will my backup tool work? Can my Security Operations Center (SOC) still see the workloads it needs to monitor? Will my identity provider support authentication if the site loses its cloud connection? The answers can determine how confidently a sovereign or edge deployment moves to production. Customers want to run the independent software vendor (ISV) solutions they already trust, with confidence in how those solutions have been validated for their Azure Local environments. That's why we built the Azure Local Validated ISV Program. Why an ecosystem program, and why now Demand for Sovereign Private Cloud is increasing as organizations look for greater control over where and how their workloads operate. Governments, regulated industries, critical infrastructure providers and telecom operators want cloud-style operations while maintaining control of their data, security, compliance and operational boundaries. Azure Local supports a range of deployment architectures, including connected and disconnected operating models, and hyperconverged, disaggregated and multi-rack configurations. Infrastructure alone, however, does not make a production environment. Customers have invested for years in the tools that run their operations, including monitoring, security, data protection, identity and line-of-business applications. Successful adoption also depends on understanding how existing operational tools integrate with Azure Local and that need is growing now. As more sovereign and regulated workloads move to production on Azure Local, including disconnected and multi-rack deployments, customers need to know before they deploy that their existing tools are supported. That's why we're launching the program at Ignite with a published list of validated solutions and clear validation scope. How we validate We don't treat validation as a logo exercise. Our focus is on technical validation that gives customers greater clarity about supported configurations and integration scenarios. Each partner solution goes through a structured process: Architecture validation: Microsoft and the ISV review the solution architecture for Azure Local, including its deployment pattern, dependencies and integration points. Lab and product validation: Partner solutions undergo testing against defined scenarios and configurations to evaluate their operation on Azure Local. Deployment-specific validation: Validation scope is documented by supported deployment configuration, which may include connected, disconnected operations or multi-rack environments, as applicable. That last point matters. Every validated solution comes with documented information about the capabilities, scenarios and configurations evaluated. We'd rather be precise than broad, because customers make architecture and procurement decisions based on what we publish. Where we are today: 22 validated solutions across four solution categories The solutions are organized into four categories: Category Validated partners Security & Identity F5 BIG-IP VE, F5 (EOB), Fortinet, IBM QRadar, Keycloak, Splunk, Trellix, WSO2 Data Streaming & AI Confluent (Kafka), MongoDB, Qumulo Business Continuity & Migration Carbonite, Cirrus Data, CloudCasa / Catalogic, Commvault, RiverMeadow, Rubrik, Veeam Application Platform & DevOps EnterpriseDB (EDB), Leostream, Mattermost, PostgreSQL A few points stand out: Resiliency where it matters most. Validated backup, disaster recovery, and migration solutions provide customers with additional options for protecting and moving supported workloads. The capabilities available depend on the selected solution and its validated configuration. Identity for connected and disconnected environment: Five identity providers are validated. The five validated identity providers can support local authentication architectures for Azure Local workloads including certain disconnected scenarios where the required identity dependencies are available locally. Security across network and workload environments. F5 and Fortinet offer capabilities for application delivery, firewalling and deep network visibility. F5 EOB, for example, uses extended Berkeley Packet Filter (eBPF) technology to observe traffic in supported workload environments. Trellix provides endpoint security capabilities for supported workloads, subject to validated deployment configurations. Of the four categories, only Business Continuity & Migration provides workload resiliency directly. The other three contribute security, identity, observability, data and application-platform capabilities that support a well-run environment. We describe each category by the role it is validated to support so customers can design with accurate expectations. From validated products to repeatable solutions The next phase of the program goes beyond validating individual products. We're moving toward repeatable customer solutions. Our goal is to develop validated solution patterns that bring together Azure Local and complementary partner technologies for defined customer scenarios, such as a sovereign security operations center (SOC), a resilient manufacturing site, or a disconnected government deployment. The aim is to help customers evaluate solution compatibility and plan production deployments with greater confidence Get involved Customers: Talk to your Microsoft account team about which validated solutions fit your Azure Local deployment and confirm the validation scope for your configuration. Independent software vendors (ISVs): If your solution supports customers operating in sovereign, edge or regulated environments, we'd like to hear from you about joining the validation program. A platform is only as strong as the ecosystem around it. We're grateful to every partner who has invested engineering time to validate on Azure Local, and we're just getting started. Customers looking for help beyond Azure Local platforms or our partner ISV products can also work with global system integrators (GSIs). Your Microsoft account team can share a list of GSIs with specialized Azure Local expertise that offer services across the solution lifecycle, from design, deployment and integration to ongoing operations as a managed services partner. Validation applies to the specific capabilities and deployment configurations documented for each partner solution. Confirm the scope with your Microsoft or partner contact before making architecture or procurement decisions. For more information: Azure Local515Views1like1CommentAzure Arc at Microsoft Ignite 2026: Sessions, hands-on labs, and ways to connect
Microsoft Ignite 2026 is almost here! Join us November 17–20 in San Francisco or online to explore the latest innovations across Microsoft. As organizations operate across increasingly distributed environments, consistent visibility, governance, and management are more important than ever. Azure Arc extends Azure to help organizations discover, govern, secure, and operate infrastructure anywhere. This year at Ignite, we're bringing Azure Arc to life through breakout sessions, interactive table talks, and hands-on labs focused on unifying and simplifying operations across your distributed estate. Here's where to find us! Explore Azure Arc sessions at Ignite Looking to strengthen governance, simplify hybrid management, or discover what's new in onboarding and inventory? We've got sessions for you. In Breakout Session 413, explore how Azure Arc brings consistent management, security, and governance to servers, Kubernetes, databases, and applications across distributed environments. Discover how to reduce security gaps, optimize costs, and streamline operations, with a closer look at managing Arc-enabled SQL Server instances through Database Hub in Microsoft Fabric. FULL SCHEDULE: 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 MCP All times are Pacific. Get hands-on with Azure Arc Looking to put your knowledge into practice? Join LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP to explore practical approaches to managing and governing distributed infrastructure. With four opportunities to participate throughout the week, be sure to add the lab to your Ignite schedule. Join us online Can't make it to San Francisco? You can still participate in Microsoft Ignite through the free digital experience. Explore the Microsoft Ignite session catalog to discover sessions and build your schedule. Stay connected with Azure Arc The learning doesn't stop at Ignite! Explore these resources to continue your Azure Arc journey: Azure Arc-enabled Servers Customer Forum: Connect with the Azure Arc product team and share feedback. 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. See you at Ignite!380Views1like0CommentsStay ahead of Azure Arc agent health with Azure Advisor
Azure Advisor helps you stay ahead of potential connectivity issues by analyzing your Azure Arc-enabled servers and providing reliability recommendations when servers have been disconnected for an extended period. These recommendations give you visibility into potential issues and help you act before they affect your ability to manage your hybrid environment through Azure Arc. Understand your Azure Arc-enabled server health A reliable connection to Azure is an important part of keeping your Azure Arc-enabled servers healthy and manageable. The Azure Connected Machine agent sends regular heartbeats to Azure to confirm that connection and help identify when a server needs attention. If Azure does not receive a heartbeat for more than 15 minutes, the server is marked Disconnected. While disconnected, Azure-based management is limited, although existing extensions can continue running locally. If the server remains disconnected for an extended period, the agent’s managed identity certificate can eventually expire. The certificate is valid for 90 days, and the agent attempts to renew it when 45 or fewer days remain. Once the certificate expires, simply restoring connectivity is not enough. You’ll need to re-onboard the server to Azure Arc to restore management. For more information about how connectivity affects Arc-enabled servers, see Troubleshoot Azure Arc-enabled servers in disconnected scenarios. A look into the Azure Advisor recommendations Azure Advisor provides recommendations based on how long an Arc-enabled server has been disconnected: Restore connectivity for a server disconnected for 30–44 days. This provides an early opportunity to investigate the server and restore its connection to Azure. Reconnect a server that has been disconnected for at least 45 days. At this stage, the server's managed identity certificate is still valid, but connectivity should be restored so the agent can renew its credential before it expires. Re-onboard an expired server. If the server's managed identity certificate has expired, Azure Arc management capabilities remain unavailable until the server is reconnected using onboarding credentials. Azure Advisor helps surface connectivity conditions earlier, giving you an opportunity to identify disconnected servers and restore connectivity before they reach an expired state. How to view recommendations Azure Portal You can start in Azure Advisor to review recommendations across your environment or open an individual Azure Arc-enabled server and focus on that singular machine. From Azure Advisor blade In the Azure portal, search for and select Advisor. Select Operational Excellence. Use the subscription and resource type filters to narrow the results, but for only Azure Arc-enabled servers ensure the Type filter only has Machines - Azure Arc selected. If applicable to your machine, the health recommendation will be shown. From an Azure Arc-enabled server In the Azure portal, search for and select Azure Arc Select Machines. Select the server you want to review to open its resource page. Open the server’s Recommendations from the Overview page. If applicable to your machine, the health recommendation will be shown. Azure Resource Graph You can also use Azure Resource Graph to view Azure Advisor recommendations for Azure Arc-enabled servers across your selected subscriptions. In the Azure Resource Graph Explorer input the following query: advisorresources | where type =~ "microsoft.advisor/recommendations" | where properties.recommendationStatus == "New" | extend recommendationTypeId = tostring(properties.recommendationTypeId) | where recommendationTypeId in~ ( "18700d61-0b5a-4807-86a1-b7d669475335", // Restore connectivity (30-44 days) "5a6e1150-2d8a-4865-b423-df234577d29b", // Reconnect before cert expires (45+ days) "157eb7ac-9b3d-4a0c-9bfb-dd2ffa37d1ae" // Re-onboard expired server ) | extend id = tostring(properties.resourceMetadata.resourceId) | extend machineName = tostring(split(id, "/")[8]) | extend recommendation = case( recommendationTypeId =~ "18700d61-0b5a-4807-86a1-b7d669475335", "Restore connectivity (disconnected 30-44 days)", recommendationTypeId =~ "5a6e1150-2d8a-4865-b423-df234577d29b", "Reconnect before certificate expires (disconnected 45+ days)", recommendationTypeId =~ "157eb7ac-9b3d-4a0c-9bfb-dd2ffa37d1ae", "Re-onboard expired server", "Unknown") | distinct recommendation, machineName, id | order by recommendation asc, machineName asc Keep your Arc environment healthy As your Azure Arc environment grows, regularly reviewing Azure Advisor recommendations can help you identify servers that need attention and address connectivity issues before they become more disruptive. If you see an Azure Arc-related recommendation in Azure Advisor, review the affected server, investigate its agent and network connectivity, and take the recommended action to return it to a Connected state. Learn more: Resolve Azure Advisor recommendations for Azure Arc-enabled servers314Views0likes1CommentSimplify Azure Arc agent updates with Automatic Agent Upgrade, now generally available
Keeping the Azure Connected Machine agent up to date across a large server estate requires persistent coordination and manual work. When enabled, Automatic Agent Upgrade simplifies this process by allowing Microsoft to manage agent upgrades for you. What is Automatic Agent Upgrade? Automatic Agent Upgrade helps keep the Azure Connected Machine agent up to date. When enabled, machines are scheduled to upgrade to the latest agent version without requiring you to manually deploy each new agent version. Upgrades are rolled out in batches across regions and initiated during off-peak hours to help maintain stability and minimize disruption. This helps: Reduce operational overhead associated with manually managing agent upgrades. Stay current with the latest available security, reliability, quality, and platform improvements. Manage upgrades at scale across Azure Arc-enabled server environments. Enable Automatic Agent Upgrade at scale Since the initial public preview, we’ve added additional ways to make Automatic Agent Upgrade easier to adopt and manage across your environment. Azure Policy Use the built-in Configure Azure Arc-enabled Servers to enable automatic upgrades policy to turn on Automatic Agent Upgrade across an assigned scope and remediate machines that are not yet configured. For setup guidance, see the Azure Policy walkthrough. Enable during onboarding Automatic Agent Upgrade can also be used when connecting a new server to Azure Arc by adding --enable-automatic-upgrade to the azcmagent connect command. This makes it easier to include Automatic Agent Upgrade as part of existing at-scale onboarding processes. For setup guidance, see the onboarding walkthrough. Azure portal onboarding When generating an onboarding script through the Azure portal, you can select Automatic Agent Upgrade so that the generated script includes the required configuration. For setup guidance, see the Portal onboarding walkthrough. Frequently asked questions What is Automatic Agent Upgrade for Azure Arc-enabled servers? Automatic Agent Upgrade is a feature that helps keep the Azure Connected Machine agent up to date. After you turn it on, Microsoft manages agent upgrades for your Azure Arc-enabled servers. How does Automatic Agent Upgrade work? Machines are scheduled to receive the latest agent version. Upgrades roll out in batches across regions and occur during off-peak hours to help maintain stability and minimize disruption. What are the benefits of Automatic Agent Upgrade? Automatic Agent Upgrade reduces the operational work of managing upgrades manually, helps servers stay current with security, reliability, quality, and platform improvements, and supports upgrade management at scale. How can I turn on Automatic Agent Upgrade at scale? You can use the built-in Configure Azure Arc-enabled Servers to enable automatic upgrades policy across an assigned scope. The policy can also remediate machines that are not yet configured. Can I configure Automatic Agent Upgrade while onboarding a server? Yes. Add --enable-automatic-upgrade to the azcmagent connect command, or select Automatic Agent Upgrade when generating an onboarding script in the Azure portal. Get started Automatic Agent Upgrade is now generally available for Azure Arc-enabled servers. To get started, review the Automatic Agent Upgrade documentation for prerequisites and the available options for enabling and managing automatic upgrades across your environment.437Views4likes1CommentIntroducing Azure Copilot for Azure Local: AI-powered operations for distributed infrastructure
Managing distributed infrastructure can be complex. When an issue occurs, operators may need to navigate multiple tools, review health signals and diagnostics, interpret logs, and determine the right troubleshooting steps before they can move toward resolution. Azure Copilot for Azure Local helps bring an AI-powered, agentic experience to Azure Local operations, designed to make managing and troubleshooting infrastructure simpler and more intuitive. With Azure Copilot for Azure Local, operators can start with a natural-language question, such as: “Why is my Azure Local cluster disconnected?” “Is this node healthy?” “Why did my deployment fail?” “Is my environment ready for an update?” “Check my network configuration” Azure Copilot for Azure Local translates the operator’s intent into a troubleshooting workflow, bringing together infrastructure context, diagnostics, and relevant troubleshooting knowledge to help operators understand what is happening and determine the appropriate next steps for their infrastructure. Start troubleshooting with natural language Infrastructure problems rarely begin with a clearly identified root cause. An administrator may simply know that an update failed, a node is unhealthy, connectivity was lost, or a deployment cannot continue. Azure Copilot for Azure Local provides a natural language starting point for these investigations. Rather than first determining which command to run, which diagnostic tool to open, or which troubleshooting guide to follow, operators can describe the problem they are trying to understand. Copilot can help gather relevant information, analyze the results, explain findings, and guide the operator toward potential next steps. This provides operators with a more intuitive troubleshooting experience that helps bridge the gap between observing a problem and knowing what to investigate next. Guided, multi-step troubleshooting Azure Copilot for Azure Local is designed to go beyond simply answering questions. For supported scenarios, the experience can orchestrate multiple steps of an investigation, using infrastructure context, diagnostic capabilities, and troubleshooting knowledge to help operators work through a problem. The troubleshooting journey becomes: Ask a question → Gather context → Run diagnostics → Analyse findings → Recommend next steps The operator remains in control while Copilot helps with the investigative work required to understand the issue and identify a path forward. Designed for real Azure Local operational scenarios Azure Copilot for Azure Local can assist operators across common infrastructure management and troubleshooting scenarios, including: Infrastructure health Understand the health of an Azure Local system or individual node and identify areas that may require further investigation. Connectivity troubleshooting Investigate why an Azure Local system or machine is disconnected and surface information that can help narrow down the issue. Network configuration Investigate network-related conditions and help identify configuration issues affecting the environment. Deployment troubleshooting Investigate failed deployments and help operators understand potential blockers and next steps. Update readiness Evaluate the environment before an update and identify conditions that may require attention. Diagnostics and log collection Guide diagnostic collection when deeper troubleshooting or additional evidence is required. Helping operators move from questions to outcomes Troubleshooting infrastructure often involves connecting information spread across configuration, health signals, diagnostics, logs, and troubleshooting documentation. Azure Copilot for Azure Local is evolving toward an operator-focused experience where AI agents can help connect these pieces as part of a guided investigation. The goal is simple: reduce the effort required to understand what is happening and help operators get to the right next step faster. By combining natural-language interaction with agentic troubleshooting workflows, Azure Copilot for Azure Local can help make complex diagnostic information easier to understand and help operators navigate investigations while keeping them in control of applicable actions. Public preview planned for early 2027 Azure Copilot for Azure Local is planned to enter public preview in early 2027. Once available, customers can explore the agentic experience in their Azure Local environments, evaluate real operational scenarios, and provide feedback that helps shape future capabilities. For more details, reach out to us at AzureLocalCopilotTeam@microsoft.com836Views0likes0CommentsAdvancing sovereign AI with Foundry Local and Azure Local
The next chapter of AI is about more than powerful models. It’s about bringing AI closer to the data, applications, and systems that organizations depend on every day. For governments, regulated industries, and organizations operating critical infrastructure, this means making AI accessible in environments where data is sensitive, connectivity may be limited, and greater operational control is essential. Microsoft’s approach to sovereign AI starts with the requirements of each workload. Our vision is to give organizations the choice and flexibility to determine where AI runs, which models they use, and how their data and infrastructure are managed. Depending on the workload, this can include control over where data and models reside, who can access and operate the environment, how AI workloads are governed, and whether critical operations can continue when cloud connectivity is restricted or unavailable. The goal is to help organizations meet their security, regulatory, and operational requirements while maintaining access to modern cloud and AI capabilities. With Foundry Local, entering general availability on Azure Local at Ignite, we're bringing advanced AI capabilities to customer-controlled environments. This enables organizations to build and run AI applications closer to their data, with greater control over how AI workloads are deployed and operated, extending the possibilities of AI beyond the public cloud. Bringing the Microsoft Foundry experience to customer-controlled environments AI delivers the greatest value when organizations can connect it securely to the data, applications, and processes that power their business. Microsoft Foundry is our unified platform for building, optimizing, and governing AI applications and agents. Foundry Local extends these capabilities to customer-controlled environments, allowing organizations to deploy and run supported AI models on Azure Local infrastructure, with local inference, model management, and GPU acceleration. Built on Azure Arc-enabled Kubernetes, Foundry Local supports CPU- and GPU-backed deployments, model lifecycle management, and OpenAI-compatible APIs. Developers can select from an integrated model catalog or bring their own supported models. Models and inference workloads can run locally, including in supported disconnected environments. We're also expanding what organizations can build with Foundry Local, moving beyond standalone inference toward intelligent applications and agents that can securely interact with enterprise data. These capabilities include: Model catalog (general available): Offers a curated model catalog, making it easy to discover and deploy AI models optimized for local and edge environments. Gives organizations greater flexibility to select models based on capability, performance, latency, resource requirements, and the sovereignty needs of individual workloads. Agentic Retrieval (general available): Enables applications to ground responses in enterprise knowledge through local data ingestion, indexing, and multistep retrieval, with citations that allow users to verify the underlying sources. Agents and enterprise connectors (available in preview): Emerging capabilities for orchestrating agents and connecting them to enterprise systems, including on-premises Exchange Server, SharePoint Server, and SQL databases through Model Context Protocol (MCP). Configurable AI guardrails (available in preview): Support for applying safety and compliance controls to local AI workloads, with flexibility to select guardrail models based on security requirements and available compute resources. Together, these capabilities help organizations build AI applications where the data lives instead of requiring the data to move to the AI. From local inference to sovereign AI applications Running AI models locally is an important first step, but sovereign AI extends beyond inference. Organizations need to connect models to enterprise knowledge, build intelligent applications and agents, and maintain control over how those applications are developed, deployed, and operated. Foundry Local helps make this possible by bringing AI capabilities closer to enterprise data and applications. Developers can use familiar Microsoft tools and technologies to build AI applications across cloud and customer-controlled environments, with greater flexibility over where models run and how they interact with organizational data. Azure Local provides the infrastructure foundation for running these workloads across datacenters, distributed locations, and edge environments, including sovereign private cloud scenarios. For organizations requiring greater operational independence, Azure Local disconnected operations enables supported infrastructure and services to operate through a local control plane without continuous connectivity to the public cloud. Sovereignty also extends to the software development lifecycle. With GitHub Enterprise Local, becoming generally available at Ignite, organizations can bring familiar GitHub development capabilities to customer-controlled infrastructure on Azure Local. Developers can manage source code, collaborate, and automate build and deployment processes using GitHub Actions and self-hosted runners while maintaining greater control over their repositories, workflows, and artifacts. Foundry Local can also provide locally hosted models for AI-assisted development scenarios in supported disconnected environments. Together, Foundry Local, Azure Local, and GitHub Enterprise Local provide a foundation for building, deploying, and operating AI applications within customer-controlled environments, extending sovereignty from the infrastructure to the models, applications, and development processes that run on it. What this means for customers The significance of these capabilities is ultimately about what they enable organizations to do. Keep sensitive data in the environment they control. Organizations can bring AI to data that may need to remain within a specific facility, geography, security boundary, or operational environment. Run AI where decisions need to happen. Manufacturers, retailers, transportation providers, healthcare organizations, governments, and others can bring intelligence closer to physical operations and distributed locations rather than depending on every interaction traveling to a remote cloud service. Support environments with limited or disconnected connectivity. Organizations operating in remote, isolated, or highly controlled environments can continue to pursue AI scenarios where constant public cloud connectivity may not be appropriate or possible. Maintain greater control over the AI stack. Customers can make deliberate choices across infrastructure, data, models, applications, operations, and governance based on the requirements of individual workloads. Turn enterprise data into useful AI experiences. Retrieval, connectors, agents, and model capabilities can help organizations build AI experiences grounded in their own information and business processes while keeping those capabilities closer to the systems they support. Most importantly, customers do not have to define a single architecture for every workload. Some AI workloads will benefit from the scale and rapid innovation of the public cloud. Others will require greater local control. Many organizations will need both. Our strategy is to give customers the flexibility to choose the right architecture for each workload while maintaining a consistent foundation across their environments. Sovereignty that enables innovation As AI becomes more deeply embedded across applications, operations, and critical infrastructure, organizations will need architecture that give them both powerful AI capabilities and meaningful control over how those capabilities are deployed. With Azure Local and Foundry Local, we’re continuing to bring Microsoft AI innovation to the places customers need it, from the cloud to customer-controlled datacenters and edge locations. That is the foundation of our approach to sovereign AI: giving every organization the control and choice to pursue its AI ambitions on its own terms. Resources Join us at Microsoft Ignite in San Francisco to explore the latest innovations across Microsoft AI, Azure Local, and sovereign cloud. Learn about AI workloads on Azure Local Explore digital sovereignty at Microsoft Learn more about Microsoft Sovereign Private Cloud753Views2likes0CommentsGitHub Enterprise Local: Bringing modern development to environments you control
Today at the Frontier Tour in Paris, we’re announcing the next milestone for GitHub Enterprise Local, which will become generally available at Microsoft Ignite. GitHub Enterprise Local brings the GitHub Enterprise Server experience to organizations’ own environments, helping them keep source code and development workflows close to where their business operates. This is especially valuable for regulated industries, sovereign environments, remote locations, and organizations that need to continue working with limited or no internet connectivity. What's New Simpler deployment: A guided Azure experience brings the key deployment steps together and reduces manual configurations. Using AI for connected and disconnected environments: Customers can use GitHub Copilot when cloud connectivity is available or locally hosted models through Foundry Local when AI processing must remain within their environment, subject to current availability and requirements. A simpler way to deploy GitHub Enterprise Local GitHub Enterprise Local now uses Workload Orchestration to provide a guided, user-friendly deployment experience in Azure. Instead of coordinating separate tools and steps, administrators can enter the required settings in one workflow and let the platform prepare the core infrastructure and GitHub Enterprise Server appliance. Deployment secrets are securely stored in Azure Key Vault, helping organizations protect sensitive information and manage access within their environment. The result is a more consistent and repeatable deployment process, with fewer opportunities for configuration errors. Organizations still retain control over important choices such as networking, naming, security, and the environment in which GitHub Enterprise Local runs. This streamlined experience also makes it easier to establish a consistent operating model across multiple locations. Platform teams can apply repeatable deployment practices, protect deployment secrets in Azure Key Vault, and give application teams a familiar GitHub environment wherever the infrastructure is located. Choose the AI experience that fits your environment Organizations do not all operate with the same connectivity, security, or data requirements. GitHub Enterprise Local keeps repositories and core development workflows on customer-controlled Azure Local infrastructure, while giving customers a clear choice for adding AI assistance. Connected environments: use GitHub Copilot When controlled internet access is available, developers can use GitHub Copilot in supported development tools while their repositories remain hosted on GitHub Enterprise Local. To use GitHub Copilot in connected environments GitHub.com identity and license is required. This option is a good fit for organizations that allow managed outbound connectivity and want the broader GitHub Copilot experience without moving their source-code hosting away from their Azure Local environment. Restricted or disconnected environments: use local AI In environments where GitHub Cloud connectivity is unavailable or not permitted, Foundry Local can run approved AI models on Azure Local. AI requests are processed inside the customer-controlled environment, helping organizations support local data boundaries and disconnected operations. Developers can access the local AI endpoint through supported GitHub tooling, while administrators manage the models, security, certificates, and access controls within their own environment. Foundry Local provides a focused local AI option rather than the full cloud-backed GitHub Copilot experience. Availability and supported capabilities may vary, so customers should review the latest product documentation when planning their deployment. Find the right fit Environment Recommended AI path Key consideration Connected GitHub Copilot with GitHub-hosted services Best when approved internet access and GitHub Copilot licensing are available. Restricted / hybrid Use GitHub Copilot for approved connected work, or local models where data must remain in the environment. Choose the AI path based on network policy and data sensitivity. Disconnected Foundry Local with approved models running on Azure Local Designed for environments that cannot depend on GitHub Cloud connectivity. Built for hybrid, sovereign, and disconnected operations GitHub Enterprise Local brings together the familiar GitHub developer experience and the flexibility of Azure Local. Customers can keep code and development workflows in their own environment, deploy the solution through a more consistent process, and choose an AI approach that matches their connectivity and data requirements. Customers can begin with the operating model that best fits their current needs and expand over time. A connected site can use GitHub Copilot through approved cloud access, while a restricted site can keep AI processing local—both supported by the same Azure Local foundation and a consistent approach to management. GitHub Enterprise Local is entering general availability at Ignite. To get started, explore the product information, review deployment requirements, and work with your Microsoft account team to plan the right Azure Local environment for your organization. Learn more about GitHub Enterprise Local532Views0likes0CommentsSovereign Private Cloud: Bringing more choice and control to AI and cloud infrastructure
To identify which sovereign cloud solution may fit your organization’s needs, take the Microsoft Sovereign Cloud assessment Digital sovereignty is essential for organizations as they modernize critical infrastructure and bring AI into more sensitive and regulated environments. We’re hearing from our customers in Europe and beyond that they want to take advantage of cloud and AI innovation while maintaining greater control over where their data, applications, and infrastructure operate. Microsoft Sovereign Private Cloud, built on Azure Local, extends cloud capabilities into customer-controlled environments, helping organizations meet sovereignty, regulatory, and operational requirements while continuing to modernize applications, infrastructure, data, and AI. At Microsoft Frontier Tour stops this month in London, Paris and Cologne, we’re showcasing exciting new capabilities that expand what our customers can achieve with Sovereign Private Cloud and Azure Local. These advancements range from running frontier AI models locally to strengthening resiliency and workload isolation, enhancing security, and improving developer productivity. Run AI where your data lives with Foundry Local Foundry Local, generally available on Azure Local at Ignite, brings the Microsoft Foundry stack into customer-controlled environments, extending AI capabilities to on-premises infrastructure. Organizations can deploy and run AI models close to their data, enabling local inference while maintaining greater control over their infrastructure, data, and operations. With Foundry Local, organizations can bring the Foundry experience to connected and disconnected environments, giving them greater flexibility in where and how they deploy AI. This enables customers to bring AI to locations and workloads where cloud connectivity, data residency, latency, or operational requirements make local processing important. We’re continuing to expand the Foundry Local model catalog, giving organizations greater choice in the models they can deploy and run locally. Developers can select models based on the needs of their applications while keeping inference close to their data, applications, and operations. Beyond model inference, Foundry Local is expanding to support agentic AI scenarios on Azure Local into public preview. Agentic Retrieval provides local data ingestion, indexing and search, along with agents, tool calling, and Model Context Protocol (MCP) server, and a built-in chat experience with citations. Together, these capabilities enable developers to build AI applications that can use locally available enterprise knowledge, interact through conversational experiences, and connect agents with tools through MCP. This extends Foundry Local from local model inference to a broader foundation for building grounded AI applications and agents in customer-controlled environments. Learn more about Foundry Local on Azure Local. Strengthen resilience and operational flexibility across Azure Local environments Sovereign environments need to remain resilient and adaptable while supporting different teams, tenants, and workloads across shared infrastructure. We’re bringing more choice over how and where our customers can operate infrastructure based on their sovereignty, connectivity, and operational requirements. Azure Local is expanding the ways organizations can operate in their environments. The ability to move from connected to disconnected Azure Local operations is entering public preview, enabling organizations to rehome Azure-connected infrastructure and workloads to a fully disconnected Azure Local environment while maintaining operational continuity and governance. The process includes safeguards such as phased execution, user approval stages, and secure environment back-ups that ensure the safe and accurate migration of both infrastructure resources and workloads to the Azure Local disconnected environment. This empowers customers to more easily transition their environments to Azure Local disconnected operations and meet their evolving operational requirements related to connectivity to the cloud and data sovereignty. Multitenancy, coming soon to Azure Local, provides greater flexibility provides greater flexibility in how organizations use and allocate shared infrastructure. Through logical isolation, organizations can consolidate workloads and make more efficient use of available capacity while maintaining separation across tenants, teams, and workloads. Initial access will be limited to qualified customer opportunities. Together, these capabilities help organizations build Sovereign Private Cloud environments that are more resilient, adaptable, and capable of supporting a diverse range of workloads and operating models. Protect sensitive workloads with confidential computing Protecting data at rest and in transit is critical. For highly sensitive workloads, organizations may also need stronger protections while data is actively being processed. With confidential virtual machines on Azure Local, now generally available, organizations can extend confidential computing protections to customer-controlled infrastructure. Confidential virtual machines provide hardware-encrypted memory and hardware-based isolation between the virtual machine, hypervisor, and host management environment, helping protect sensitive data while it is in use. Hardware-rooted attestation provides additional assurance by enabling the integrity of the platform and workload to be verified before sensitive data or keys are released. Customers can also use integrity protection for the guest operating system to help protect the OS disk and boot chain from unauthorized modification. For organizations running regulated, sensitive, or mission-critical workloads, these capabilities provide an additional layer of protection within Sovereign Private Cloud. By combining customer-controlled infrastructure with hardware-enforced isolation and attestation, organizations can strengthen protection for sensitive workloads while maintaining greater control over where their data and applications run. Learn more about confidential virtual machines on Azure Local. Bring development and DevOps into the sovereign boundary with GitHub Enterprise Local Sovereignty extends beyond production infrastructure. Organizations also need to consider where applications are developed and how development environments are operated. GitHub Enterprise Local, entering general availability at Ignite, brings GitHub Enterprise Server into Azure Local and Sovereign Private Cloud environments. This enables organizations to support local development and DevOps while keeping development environments within their sovereign operational boundary. Delivered as a prebuilt virtual appliance on Azure Local, it keeps repositories, metadata, CI/CD workflows, and development artifacts within the organization’s infrastructure and security boundaries. Developers can use familiar GitHub capabilities including private repositories, pull requests, code reviews, issues, GitHub Actions with self-hosted runners, GitHub Packages, and GitHub Advanced Security, while organizations maintain control over identity, networking, security policies, upgrades, and administration. GitHub Enterprise Local supports both connected and fully disconnected environments. GitHub Enterprise Local supports AI-enabled developer experiences across connectivity models. In connected environments, developers can continue using cloud-connected capabilities such as GitHub Copilot, while in disconnected environments, Foundry Local on Azure Local can provide locally hosted AI models for AI-assisted development scenarios. The general availability of GitHub Enterprise Local expands Microsoft’s Sovereign Private Cloud platform beyond infrastructure and workloads to the tools developers use to build and manage applications. Learn more about GitHub Enterprise Local. Run critical data workloads locally At FabCon, we announced the general availability of SQL Server on Azure Local across connected and disconnected environments, expanding the options organizations have to run critical data workloads where they need greater control over their data and infrastructure. We are continuing to expand the data services available on Sovereign Private Cloud with DocumentDB on Azure Local and Blob Storage on Azure Local, both entering public preview at Ignite. DocumentDB on Azure Local brings a MongoDB-compatible, open-source document database to customer-controlled environments, giving organizations more flexibility to run document and JSON workloads locally. Blob Storage on Azure Local provides cloud-native object storage for unstructured data while keeping the data local, giving organizations more flexibility to store and access data within sovereign environments. Together with SQL Server, these capabilities expand Azure Local beyond infrastructure to support a broader data estate across relational databases, document databases, and object storage. For Sovereign Private Cloud customers, that means greater flexibility to modernize applications and data while keeping critical workloads and data in customer-controlled environments. Resources Learn more about Azure Local Explore digital sovereignty at Microsoft Learn more about Microsoft Sovereign Private Cloud Join us at Microsoft Ignite in San Francisco this November To identify which sovereign cloud solution may fit your organization’s needs, take the Microsoft Sovereign Cloud assessment1.1KViews2likes0CommentsEnd of Lifecycle for Windows Server 2012 and 2012 R2
On October 13, 2026, the Extended Security Updates (ESU) program for Windows Server 2012 and Windows Server 2012 R2 ended. This closes the three-year extended coverage period that began when these operating systems reached end of support in October 2023. After today, Microsoft will no longer provide security updates for Windows Server 2012 or Windows Server 2012 R2. How we got here Windows Server 2012 and 2012 R2 reached end of support on October 10, 2023. To give customers time to modernize, Microsoft offered up to three additional years of ESU for eligible servers. Over that time, ESU gave organizations a way to keep receiving critical security updates for workloads that needed more time to upgrade, migrate or modernize. What this means for you Servers still running Windows Server 2012 or 2012 R2 will no longer receive security updates from Microsoft. Unsupported operating systems become harder to secure and maintain over time and running them in production adds security and compliance risk. Unsupported infrastructure shouldn't be a long-term strategy. What to do next If you still have Windows Server 2012 or 2012 R2 workloads in production, start with these steps: Identify affected servers. Inventory your datacenter, edge and cloud environments to find where Windows Server 2012 and 2012 R2 are still running. Understand your dependencies. Many remaining deployments support business-critical applications. Validate what depends on each server before you decide what to do with it. Choose a path for each workload. Options include upgrading to a supported version of Windows Server, migrating workloads to Azure, modernizing applications onto Azure services, or adopting a hybrid approach. Set a timeline and prioritize. Move business-critical and highest-risk workloads first to reduce operational and security exposure. Get help. Engage your Microsoft account team and trusted partners to build a transition plan that fits your environment. Why modernizing is worth it Moving to a supported platform is the best way to stay secure, and it also gives you the following: A stronger security posture, with ongoing security updates and support Better operational efficiency through modern management capabilities The latest performance, reliability and resiliency improvements Less technical debt and lower long-term infrastructure risk Access to new AI, cloud and hybrid capabilities Looking ahead Microsoft is committed to helping you modernize on your terms, whether you're upgrading on-premises infrastructure, migrating to Azure or taking a hybrid approach. To learn more about support lifecycle information and modernization paths, see Overview of Extended Security Updates for Windows Server 2012 and 2012 R2 on Microsoft Learn.1.1KViews0likes0Comments