除虚拟机外，Azure可用哪些能力实现Dynamics Nav与云电话提供商集成？

Great question! Since you want to avoid exposing your internal Dynamics NAV environment to inbound internet connections and skip the overhead of managing VMs, Azure has several tailored serverless and managed services that fit this scenario perfectly. Let’s break down the best options, along with how they’d work for your use case:

1. Azure Functions (Serverless Compute) #

This is probably the most flexible option for your public endpoint needs. Here’s how it would fit:

• Set up an HTTP-triggered Azure Function as the public endpoint your cloud phone provider will call.
• For communicating back to Dynamics NAV (without inbound connections), you have two solid patterns:
  • Persistent WebSocket Connection: Your Dynamics NAV instance initiates an outbound WebSocket connection to the Azure Function, keeping it alive. When the phone provider sends a request to the Function, it forwards the message through this open WebSocket to NAV.
  • Azure Service Bus Relay: Use the Service Bus Relay feature to let NAV establish an outbound "listener" that the Function can send messages to, without exposing NAV to the internet.
• Key perks: No VM management, pay-per-execution pricing, auto-scales based on traffic, and supports multiple programming languages if you need custom logic.

2. Azure Logic Apps (Low-Code Integration) #

If you prefer a no-code/low-code approach, Logic Apps is ideal for building the integration workflow:

• Create an HTTP-triggered Logic App to act as the phone provider’s public endpoint.
• Use Azure’s built-in connectors (or custom ones) to route requests to a message store like Azure Storage Queues or Azure Service Bus.
• Your Dynamics NAV instance initiates an outbound connection to pull messages from this queue/service bus whenever new requests arrive.
• Key perks: Visual drag-and-drop workflow designer, hundreds of pre-built connectors for common services, and fully managed infrastructure so you don’t have to worry about scaling or maintenance.

3. Azure SignalR Service (Real-Time Persistent Connections) #

If you need real-time, bidirectional communication between the phone provider and Dynamics NAV, SignalR Service simplifies connection management:

• Deploy an Azure SignalR Service to handle persistent connections. Your Dynamics NAV instance initiates an outbound connection to SignalR and stays connected.
• Pair it with an HTTP-triggered Azure Function: when the cloud phone provider sends a request to the Function, it uses SignalR Service to push the message directly to the connected NAV instance.
• Key perks: Handles connection lifecycle, reconnections, and scaling automatically. Perfect for scenarios where you need instant updates (like incoming call alerts sent to NAV in real time).

4. Azure Service Bus (Reliable Message Broker) #

For asynchronous, guaranteed message delivery, Service Bus is a rock-solid choice:

• Set up a Service Bus Queue or Topic. Your Azure Function (HTTP-triggered) receives requests from the phone provider and drops them into the queue/topic.
• Dynamics NAV initiates an outbound connection to Service Bus to pull messages from the queue/topic on a schedule or in real time.
• Key perks: Messages are persisted even if NAV is offline, supports dead-letter queues for failed messages, and ensures reliable delivery—great for mission-critical call data that can’t be lost.

Security & Best Practices #

• Protect your public endpoint: Use Azure AD authentication or API keys to restrict access to only your cloud phone provider. You can also add IP filtering to allow only their IP ranges.
• Secure NAV’s outbound connections: Store connection strings for Azure services in Azure Key Vault instead of hardcoding them in NAV. Use Managed Identities if your NAV environment can support it, to avoid credential management entirely.
• Monitor the integration: Use Azure Monitor to track request rates, connection statuses, and message delivery metrics—this helps you catch issues before they impact your workflow.

内容的提问来源于stack exchange，提问作者Mak Sim