Generally Available: Azure Arc-enabled servers support for private endpoints
The Azure Arc team is excited to announce that Azure Arc-enabled servers’ support for private endpoints is now generally available! With private endpoints, you can send traffic from the Azure Connected Machine Agent to Azure over a site-to-site VPN or Express Route circuit instead of the public internet or proxy server. This can help you reduce network exposure and improve security while still allowing you to use Azure Arc to secure, monitor and govern your servers running outside of Azure.
How does it work?
Private endpoints allow you to connect an Azure service to an Azure virtual network using private IP addresses. Servers and other resources in that virtual network can then communicate with the Azure service using the private IP address and instead of sending data over the internet.
Azure Arc uses a Private Link Scope resource to associate a private endpoint with the non-Azure servers that will use the private endpoint. You’ll also need to set up a site-to-site VPN or Express Route circuit to connect your Azure virtual network with the network where your non-Azure servers are connected.
Once configured, the Connected Machine agent on your Arc-enabled servers will send all metadata updates, extension operations, and guest configuration package downloads over the private endpoint. Network traffic between extensions you’ve installed and the Azure services that support them will also route through the internet unless you’ve configured private endpoints for each of those services. Additionally, the Connected Machine agent will still require access to Azure Active Directory and Azure Resource Manager over the internet.
Network architecture diagram of Azure Arc-enabled servers private endpoints
Learn more and get started
You can learn more about private endpoints for Azure Arc-enabled servers in our documentation, which covers the concepts, prerequisites, and setup instructions for new and existing servers. There is also an Azure Arc Jumpstart scenario for private endpoints where you can set up a sandbox environment in Azure to learn more about private endpoints and practice working with them without affecting any of your production infrastructure. And lastly, our Azure Arc landing zone accelerator covers network topology and connectivity best practices, as you scale from testing to production workloads
Published on:
Learn moreRelated posts
Azurite: Build Azure Queues and Functions Locally with C#
Lets say you are a beginner Microsoft Azure developer and you want to : Normally, these tasks require an Azure Subscription. But what if I tol...
Data encryption with customer-managed key (CMK) for Azure Cosmos DB for MongoDB vCore
Built-in security for every configuration Azure Cosmos DB for MongoDB vCore is designed with security as a foundational principle. Regardless ...
Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines
Building on our previous post about implementing dev-to-prod promotion with GitHub Actions, this follow-up demonstrates the same “build ...
Azure DevOps OAuth Client Secrets Now Shown Only Once
We’re making an important change to how Azure DevOps displays OAuth client secrets to align with industry best practices and improve our overa...
Azure Managed Instance for Apache Cassandra v5.0 Generally Available!
Azure Managed Instance for Apache Cassandra Upgrade to Cassandra v5.0 is now generally available, bringing a host of powerful new features and...
Hunting Living Secrets: Secret Validity Checks Arrive in GitHub Advanced Security for Azure DevOps
If you’ve ever waded through a swamp of secret scanning alerts wondering, “Which of these are actually dangerous right now?”— this enhancement...
Real-Time Security with Continuous Access Evaluation (CAE) comes to Azure DevOps
We’re thrilled to announce that Continuous Access Evaluation (CAE) is now supported on Azure DevOps, bringing a new level of near real-time se...