How should remote developers securely access Azure SQL Managed Instance?
Short answer
D a private endpoint
Question

Key Takeaways
The question tests secure remote developer connectivity to SQL Managed Instance; the common trap is choosing a P2S VPN, which adds infrastructure cost and complexity versus a private endpoint.
Remote developers on Microsoft Entra joined Windows 11 devices need secure access to an Azure SQL Managed Instance deployed in a virtual network. Community consensus favors a private endpoint as the most secure, cost-effective, and management-friendly solution.
Common mistake: Many choose B (Point-to-Site VPN) because it seems intuitive for remote access, but it requires deploying and managing a VPN gateway, increasing cost and administrative effort compared to a private endpoint.
Expert Analysis
Why the Answer Is Correct
A private endpoint (Option D) exposes the SQL Managed Instance only within the virtual network using a private IP address, keeping traffic entirely on the Azure backbone. It satisfies the security requirement that only designated developers on Microsoft Entra joined Windows 11 devices can access the instance remotely. As noted in Comment [1], private endpoints are the most secure and resource-economical option because they avoid extra infrastructure like VPN gateways. Comment [5] reinforces that private endpoints reduce network traffic costs and eliminate the need for additional gateway infrastructure, aligning with the business requirement to minimize costs and administrative effort.
Why the Other Options Are Wrong
Options A and C (public endpoint via database-level or server-level firewall rule) are incorrect because SQL Managed Instance does not support public endpoints; it is inherently deployed inside a virtual network and only accessible via private connectivity. Option B (Point-to-Site VPN) is a plausible distractor, but as Comment [6] points out, it requires deploying a VPN gateway, incurring extra cost and management overhead. Comment [3] also notes that a private endpoint makes more sense when the MI is already in the target vNet, avoiding unnecessary VPN complexity.
Community Comment Notes
The community is split, with 60% voting D and 40% voting B. Comment [1] provides a strong rationale for D, citing Microsoft documentation that lists private endpoints as a top connectivity option. Comment [2] and [4] advocate for B, referencing P2S VPN documentation for remote developer connectivity. However, Comment [5] and [6] effectively counter the P2S argument by emphasizing cost and administrative efficiency, which aligns with the business requirements to minimize both.
Official Reference
- https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/connect-application-instance?view=azuresql
- https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview
- https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-about
These links open the official vendor documentation in a new tab.
Exam Strategy
Always align your answer with the business requirements stated in the case study. If minimizing cost and administrative effort is emphasized, choose the solution that avoids additional infrastructure like VPN gateways, such as a private endpoint.
Community Votes
60% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
JJJR 👍 3 Answered DI'd say D because of following: There are three options to connect to a SQL Managed Instance in a different virtual network: Private endpoints Azure VNet peering VNet-to-VNet VPN gateway (Azure portal, PowerShell, Azure CLI) Of the three, private endpoints are the most secure and resource-economical option because they: only expose the SQL Managed Instance from its virtual network. only allow one-way connectivity. require just one IP address in the application's virtual network. https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/connect-application-instance?view=azuresql#connect-from-inside-a-different-vnet
-
bingomutant 👍 1D Private Endpoint - satisfies the requirements - No Need for VPN Gateways: Unlike using a Point-to-Site (P2S) VPN, a private endpoint does not require the deployment of additional infrastructure such as a VPN gateway, which can incur extra costs. Reduced Network Traffic Costs: With a private endpoint, all traffic between your Azure resources and the SQL database remains within the Azure backbone network, avoiding egress charges that might apply if traffic were routed through the public internet or through a VPN - Administrative Effort Minimization: Simplified Network Configuration: Once the private endpoint is configured, it provides a straightforward way to secure the connection. You won't need to manage or configure VPN connections, which can require additional maintenance.
-
voodoo_sh 👍 1I think correct answer is B: a Point-to-Site (P2S) VPN Configure P2S VPN, so remote developers can connect to virtual network using the Azure VPN Client over VPN, using their Microsoft Entra (domain) accounts. And then connect to SQL MI's internal endpoint (hidden within virtual network), also using the Microsoft Entra accounts with MFA. Incorrect answers: Not A, C - because SQL Managed Instance doesn't have server-level or database-level firewall rules. Its possible to limit connections to public endpoint, using the Network Security Group's inbound rules, but that relates to NSG, not a MI's firewall. Not D - not a private endpoint - because private endpoint feature simply provides local IP address for SQL MI in a chosen virtual network.
-
JamC 👍 1 Answered BAnswer is B. From: https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-about A Point-to-Site (P2S) VPN gateway connection lets you create a secure connection to your virtual network from an individual client computer. A P2S connection is established by starting it from the client computer. This solution is useful for telecommuters who want to connect to Azure virtual networks from a remote location, such as from home or a conference.
-
voodoo_sh 👍 1 Answered BI think it is B - Point-to-Site VPN to on-premises datacenter (and it has connection to Azure's Network1), or P2S VPN directly to Azure Network1. D: Private endpoint doesn't make any sense here for me. It would make sense if SQL MI was in some different vNet, such as "Network2", and you would want to use private endpoint to connect MI to Network1 and then connect to MI from there.
Show 1 more comment
-
2f5c7cd 👍 1I think B-P2S, the requirement is developer to MI https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/connect-application-instance?view=azuresql#connect-a-developer-box
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DP-300 Questions
Access 105 questions with complete answers and detailed explanations.
View Full DP-300 Practice Test →