Connectivity modes and requirements
This article describes the connectivity modes available for Azure Arc-enabled data services, and their respective requirements.
Connectivity modes
There are multiple options for the degree of connectivity from your Azure Arc-enabled data services environment to Azure. As your requirements vary based on business policy, government regulation, or the availability of network connectivity to Azure, you can choose from the following connectivity modes.
Azure Arc-enabled data services provide you the option to connect to Azure in two different connectivity modes:
- Directly connected
- Indirectly connected
The connectivity mode provides you the flexibility to choose how much data is sent to Azure and how users interact with the Arc Data Controller. Depending on the connectivity mode that is chosen, some functionality of Azure Arc-enabled data services might or might not be available.
Importantly, if the Azure Arc-enabled data services are directly connected to Azure, then users can use Azure Resource Manager APIs, the Azure CLI, and the Azure portal to operate the Azure Arc data services. The experience in directly connected mode is much like how you would use any other Azure service with provisioning/de-provisioning, scaling, configuring, and so on, all in the Azure portal. If the Azure Arc-enabled data services are indirectly connected to Azure, then the Azure portal is a read-only view. You can see the inventory of SQL managed instances and PostgreSQL servers that you have deployed and the details about them, but you can't take action on them in the Azure portal. In the indirectly connected mode, all actions must be taken locally using Azure Data Studio, the appropriate CLI, or Kubernetes native tools like kubectl.
Additionally, Microsoft Entra ID and Azure Role-Based Access Control can be used in the directly connected mode only because there's a dependency on a continuous and direct connection to Azure to provide this functionality.
Some Azure-attached services are only available when they can be directly reached such as Container Insights, and backup to blob storage.
| Indirectly connected | Directly connected | Never connected | |
|---|---|---|---|
| Description | Indirectly connected mode offers most of the management services locally in your environment with no direct connection to Azure. A minimal amount of data must be sent to Azure for inventory and billing purposes only. It's exported to a file and uploaded to Azure at least once per month. No direct or continuous connection to Azure is required. Some features and services that require a connection to Azure won't be available. | Directly connected mode offers all of the available services when a direct connection can be established with Azure. Connections are always initiated from your environment to Azure and use standard ports and protocols such as HTTPS/443. | No data can be sent to or from Azure in any way. |
| Current availability | Available | Available | Not currently supported. |
| Typical use cases | On-premises data centers that don’t allow connectivity in or out of the data region of the data center due to business or regulatory compliance policies or out of concerns of external attacks or data exfiltration. Typical examples: Financial institutions, health care, government. Edge site locations where the edge site doesn’t typically have connectivity to the Internet. Typical examples: oil/gas or military field applications. Edge site locations that have intermittent connectivity with long periods of outages. Typical examples: stadiums, cruise ships. |
Organizations who are using public clouds. Typical examples: Azure, AWS or Google Cloud. Edge site locations where Internet connectivity is typically present and allowed. Typical examples: retail stores, manufacturing. Corporate data centers with more permissive policies for connectivity to/from their data region of the datacenter to the Internet. Typical examples: Nonregulated businesses, small/medium sized businesses |
Truly "air-gapped" environments where no data under any circumstances can come or go from the data environment. Typical examples: top secret government facilities. |
| How data is sent to Azure | There are three options for how the billing and inventory data can be sent to Azure: 1) Data is exported out of the data region by an automated process that has connectivity to both the secure data region and Azure. 2) Data is exported out of the data region by an automated process within the data region, automatically copied to a less secure region, and an automated process in the less secure region uploads the data to Azure. 3) Data is manually exported by a user within the secure region, manually brought out of the secure region, and manually uploaded to Azure. The first two options are an automated continuous process that can be scheduled to run frequently so there's minimal delay in the transfer of data to Azure subject only to the available connectivity to Azure. |
Data is automatically and continuously sent to Azure. | Data is never sent to Azure. |
Feature availability by connectivity mode
| Feature | Indirectly connected | Directly connected |
|---|---|---|
| Automatic high availability | Supported | Supported |
| Self-service provisioning | Supported Use Azure Data Studio, the appropriate CLI, or Kubernetes native tools like Helm, kubectl, or oc, or use Azure Arc-enabled Kubernetes GitOps provisioning. |
Supported In addition to the indirectly connected mode creation options, you can also create through the Azure portal, Azure Resource Manager APIs, the Azure CLI, or ARM templates. |
| Elastic scalability | Supported | Supported |
| Billing | Supported Billing data is periodically exported out and sent to Azure. |
Supported Billing data is automatically and continuously sent to Azure and reflected in near real time. |
| Inventory management | Supported Inventory data is periodically exported out and sent to Azure. Use client tools like Azure Data Studio, Azure Data CLI, or kubectl to view and manage inventory locally. |
Supported Inventory data is automatically and continuously sent to Azure and reflected in near real time. As such, you can manage inventory directly from the Azure portal. |
| Automatic upgrades and patching | Supported The data controller must either have direct access to the Microsoft Container Registry (MCR) or the container images need to be pulled from MCR and pushed to a local, private container registry that the data controller has access to. |
Supported |
| Automatic backup and restore | Supported Automatic local backup and restore. |
Supported In addition to automated local backup and restore, you can optionally send backups to Azure blob storage for long-term, off-site retention. |
| Monitoring | Supported Local monitoring using Grafana and Kibana dashboards. |
Supported In addition to local monitoring dashboards, you can optionally send monitoring data and logs to Azure Monitor for at-scale monitoring of multiple sites in one place. |
| Authentication | Use local username/password for data controller and dashboard authentication. Use SQL and Postgres logins or Active Directory (AD isn't currently supported) for connectivity to database instances. Use Kubernetes authentication providers for authentication to the Kubernetes API. | In addition to or instead of the authentication methods for the indirectly connected mode, you can optionally use Microsoft Entra ID. |
| Role-based access control (RBAC) | Use Kubernetes RBAC on Kubernetes API. Use SQL and Postgres RBAC for database instances. | You can use Microsoft Entra ID and Azure RBAC. |
Connectivity requirements
Some functionality requires a connection to Azure.
All communication with Azure is always initiated from your environment. This is true even for operations that are initiated by a user in the Azure portal. In that case, there is effectively a task, which is queued up in Azure. An agent in your environment initiates the communication with Azure to see what tasks are in the queue, runs the tasks, and reports back the status/completion/fail to Azure.
| Type of Data | Direction | Required/Optional | Additional Costs | Mode Required | Notes |
|---|---|---|---|---|---|
| Container images | Microsoft Container Registry -> Customer | Required | No | Indirect or direct | Container images are the method for distributing the software. In an environment which can connect to the Microsoft Container Registry (MCR) over the Internet, the container images can be pulled directly from MCR. If the deployment environment doesn’t have direct connectivity, you can pull the images from MCR and push them to a private container registry in the deployment environment. At creation time, you can configure the creation process to pull from the private container registry instead of MCR. This also applies to automated updates. |
| Resource inventory | Customer environment -> Azure | Required | No | Indirect or direct | An inventory of data controllers, database instances (PostgreSQL and SQL) is kept in Azure for billing purposes and also for purposes of creating an inventory of all data controllers and database instances in one place which is especially useful if you have more than one environment with Azure Arc data services. As instances are provisioned, deprovisioned, scaled out/in, scaled up/down the inventory is updated in Azure. |
| Billing telemetry data | Customer environment -> Azure | Required | No | Indirect or direct | Utilization of database instances must be sent to Azure for billing purposes. |
| Monitoring data and logs | Customer environment -> Azure | Optional | Maybe depending on data volume (see Azure Monitor pricing) | Indirect or direct | You might want to send the locally collected monitoring data and logs to Azure Monitor for aggregating data across multiple environments into one place and also to use Azure Monitor services like alerts, using the data in Azure Machine Learning, etc. |
| Azure Role-based Access Control (Azure RBAC) | Customer environment -> Azure -> Customer Environment | Optional | No | Direct only | If you want to use Azure RBAC, then connectivity must be established with Azure at all times. If you don’t want to use Azure RBAC, then local Kubernetes RBAC can be used. |
| Microsoft Entra ID (Future) | Customer environment -> Azure -> Customer environment | Optional | Maybe, but you might already be paying for Microsoft Entra ID | Direct only | If you want to use Microsoft Entra ID for authentication, then connectivity must be established with Azure at all times. If you don’t want to use Microsoft Entra ID for authentication, you can use Active Directory Federation Services (ADFS) over Active Directory. Pending availability in directly connected mode |
| Backup and restore | Customer environment -> Customer environment | Required | No | Direct or indirect | The backup and restore service can be configured to point to local storage classes. |
| Azure backup - long term retention (Future) | Customer environment -> Azure | Optional | Yes for Azure storage | Direct only | You might want to send backups that are taken locally to Azure Backup for long-term, off-site retention of backups and bring them back to the local environment for restore. |
| Provisioning and configuration changes from Azure portal | Customer environment -> Azure -> Customer environment | Optional | No | Direct only | Provisioning and configuration changes can be done locally using Azure Data Studio or the appropriate CLI. In directly connected mode, you can also provision and make configuration changes from the Azure portal. |
Details on internet addresses, ports, encryption, and proxy server support
| Service | Port | URL | Direction | Notes |
|---|---|---|---|---|
| Helm chart (direct connected mode only) | 443 | arcdataservicesrow1.azurecr.io |
Outbound | Provisions the Azure Arc data controller bootstrapper and cluster level objects, such as custom resource definitions, cluster roles, and cluster role bindings, is pulled from an Azure Container Registry. |
| Azure monitor APIs * | 443 | *.ods.opinsights.azure.com*.oms.opinsights.azure.com*.monitoring.azure.com |
Outbound | Azure Data Studio and Azure CLI connect to the Azure Resource Manager APIs to send and retrieve data to and from Azure for some features. See Azure Monitor APIs. |
| Azure Arc data processing service * | 443 | *.<region>.arcdataservices.com 2 |
Outbound |
1 Requirement depends on deployment mode:
- For direct mode, the controller pod on the Kubernetes cluster needs to have outbound connectivity to the endpoints to send the logs, metrics, inventory, and billing information to Azure Monitor/Data Processing Service.
- For indirect mode, the machine that runs
az arcdata dc uploadneeds to have the outbound connectivity to Azure Monitor and Data Processing Service.
2 For extension versions up to and including February 13, 2024, use san-af-<region>-prod.azurewebsites.net.
Azure Monitor APIs
Connectivity from Azure Data Studio to the Kubernetes API server uses the Kubernetes authentication and encryption that you have established. Each user that is using Azure Data Studio or CLI must have an authenticated connection to the Kubernetes API to perform many of the actions related to Azure Arc-enabled data services.
Additional network requirements
In addition, resource bridge requires Arc-enabled Kubernetes endpoints.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for