> This page location: /docs.md > /docs/management.md > /docs/atlas/reference.md > /docs/atlas/reference/cloud-providers.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

<!--
Tab options on this page. Append to the .md URL to filter:
  ?tabs=<id,...>   select specific tabs (e.g. ?tabs=nodejs,shell)
  ?allTabs=true    include every tab
  (no param)       default: one tab per tabset

Available tabs:
  other tabs: americas, europe, asia-pacific, africa, middleeast, low-cpu, high-cpu
-->

# Microsoft Azure

**Important:**

The feature described on this page is not currently supported on Atlas Infinite clusters during public preview. For the features supported in public preview, see [Public Preview Availability.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/#public-preview-availability)

Atlas supports deploying clusters onto Microsoft Azure.

## Availability Zones and Supported Regions

Atlas supports the following Azure (Microsoft Azure) regions and [Availability Zones](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure-availability-zones). While all of the following regions support dedicated clusters (`M10+`), some regions don't support Free clusters (formerly known as `M0`) or Flex clusters. The Atlas [API](https://www.mongodb.com/docs/atlas/api.md#std-label-graphql-api-overview) uses the corresponding Atlas Region.

**Note:**

Clusters spun up in an Atlas organization created through Azure (Microsoft Azure) Native Integration aren't limited to the specific Azure (Microsoft Azure) region where the organization is based. Clusters can be deployed in any of the 40+ worldwide Azure (Microsoft Azure) regions in which Atlas is supported. The organization region is only required to fit the Azure (Microsoft Azure) resource requirements and has no impact on the regions where clusters in the organization are deployed.

**Important:**

We recommend that you use the regions marked by an asterisk () in the following table as a secondary disaster recovery (DR) region only in a [multi-region cluster](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-multi-region-cluster) because these regions cost higher than the other regions in the table.

Also, these regions might not be available in your Azure (Microsoft Azure) environments without approval from Azure (Microsoft Azure) support. If you want to leverage private networking options, such as [VNet peering](https://www.mongodb.com/docs/atlas/security-vpc-peering.md#std-label-vpc-peering) or [private endpoints](https://www.mongodb.com/docs/atlas/security-configure-private-endpoints.md#std-label-private-endpoint), with a cluster deployed in one or more of these regions, you must allow your Azure (Microsoft Azure) subscription to create resources in these regions. To learn more, contact [Azure support.](https://azure.microsoft.com/en-us/support/)

### Americas

| Azure Region | Location | Atlas Region | `Free` Support | `Flex` Support | `M10+` Support | Availability Zones |
| --- | --- | --- | --- | --- | --- | --- |
| `centralus` | Iowa, USA | `US_CENTRAL` |  |  |  | |
| `eastus` | Virginia (East US) | `US_EAST` |  |  |  | |
| `eastus2` | Virginia, USA | `US_EAST_2` |  |  |  | |
| `northcentralus` | Illinois, USA | `US_NORTH_CENTRAL` |  |  |  | |
| `westus` | California, USA | `US_WEST` |  |  |  | |
| `westus2` | Washington, USA | `US_WEST_2` |  |  |  | |
| `westus3` | Arizona, USA | `US_WEST_3` |  |  |  | |
| `westcentralus` | Wyoming, USA | `US_WEST_CENTRAL` |  |  |  | |
| `southcentralus` | Texas, USA | `US_SOUTH_CENTRAL` |  |  |  | |
| `brazilsouth` | Sao Paulo, Brazil | `BRAZIL_SOUTH` |  |  |  | |
| `brazilsoutheast` | Rio de Janeiro, Brazil | `BRAZIL_SOUTHEAST` |  |  |  | |
| `canadaeast` | Quebec City, QC, Canada | `CANADA_EAST` |  |  |  | |
| `canadacentral` | Toronto, ON, Canada | `CANADA_CENTRAL` |  |  |  | |
| `chilecentral` | Santiago | `CHILE_CENTRAL` |  |  |  | |
| `mexicocentral` | Querétaro State, Mexico | `MEXICO_CENTRAL` |  |  |  | |

## Extended Standard IOPS and Extended Storage Supported Regions

Atlas supports [NVMe storage](https://www.mongodb.com/docs/atlas/nvme-storage.md#std-label-nvme-storage), [Extended Standard IOPS](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-extend-iops-azure-steps), and [Extended Storage Sizes](https://www.mongodb.com/docs/atlas/tutorial/manage-project-settings.md#std-label-enable-extended-storage) in the following Azure (Microsoft Azure) regions.

Extended Storage is not available for [multi-region clusters.](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-multi-region-cluster)

**Note:**

Clusters in these regions created after November 1, 2024 support extended storage. Clusters existing in these regions prior to this date will automatically support extended storage over time. To enable extended storage on clusters created prior to November 1, 2024 earlier, contact [MongoDB Support](https://support.mongodb.com/welcome).

### Americas

| Azure Region | Location | Atlas Region | NVMe Support | Extended Standard IOPS |
| --- | --- | --- | --- | --- |
| `centralus` | Iowa, USA | `US_CENTRAL` |  | |
| `eastus` | Virginia (East US) | `US_EAST` |  | |
| `eastus2` | Virginia, USA | `US_EAST_2` |  | |
| `northcentralus` | Illinois, USA | `US_NORTH_CENTRAL` |  | |
| `westus` | California, USA | `US_WEST` |  | |
| `westus2` | Washington, USA | `US_WEST_2` |  | |
| `westus3` | Arizona, USA | `US_WEST_3` |  | |
| `westcentralus` | Wyoming, USA | `US_WEST_CENTRAL` |  | |
| `southcentralus` | Texas, USA | `US_SOUTH_CENTRAL` |  | |
| `brazilsouth` | Sao Paulo, Brazil | `BRAZIL_SOUTH` |  | |
| `brazilsoutheast` | Rio de Janeiro, Brazil | `BRAZIL_SOUTHEAST` |  | |
| `canadaeast` | Quebec City, QC, Canada | `CANADA_EAST` |  | |
| `canadacentral` | Toronto, ON, Canada | `CANADA_CENTRAL` |  | |
| `chilecentral` | Santiago | `CHILE_CENTRAL` |  | |
| `mexicocentral` | Querétaro State, Mexico | `MEXICO_CENTRAL` |  | |

## Cluster Configuration Options

Each Atlas cluster tier comes with a default set of resources. Atlas provides the following resource configuration options:

Custom Storage Size

The size of the server root volume. Atlas clusters deployed onto Azure (Microsoft Azure) use premium SSD (Solid State Disk)s.&#x20;

**Note: RAM Availability**

The actual amount of RAM available to each cluster tier might be slightly less than the stated amount, due to memory that the kernel reserves.

**Note:**

As of October 18, 2021, the following Atlas clusters deployed to Azure (Microsoft Azure) offer 16,000 IOPS (up from 7,500) and 500 MB/second throughput (up from 250 MB/second):

- New clusters with 4 TB storage volumes.

- Existing clusters that you scale up to 4 TB storage volumes.

The following cluster tiers are available:

| Cluster Tiers | Storage Range | Default Storage | Default RAM | Default vCPU |
| --- | --- | --- | --- | --- |
| M0 | .5 GB | .5 GB | Shared | Shared |
| Flex | 5 GB | 5 GB | Flex | Flex |
| M10 | 8 GB to 128 GB | 8 GB | 2 GB | 1 |
| M20 | 8 GB to 256 GB | 16 GB | 4 GB | 1 or 2 |
| M30 | 8 GB to 512 GB | 32 GB | 8 GB | 2 |
| M40 | 8 GB to 1 TB | 64 GB | 16 GB | 4 |
| M40 Low-CPU | 8 GB to 1 TB | 64 GB | 16 GB | 2 |
| M50 | 8 GB to 4 TB | 128 GB | 32 GB | 8 |
| M50 Low-CPU | 8 GB to 4 TB | 128 GB | 32 GB | 4 |
| M60 | 8 GB to 4 TB | 128 GB | 64 GB | 16 |
| M60_NVME | 1600 GB | 1600 GB | 64 GB | 8 |
| M60 Low-CPU | 8 GB to 4 TB | 128 GB | 64 GB | 8 |
| M80 | 8 GB to 4 TB | 256 GB | 128 GB | 32 |
| M80 Low-CPU | 8 GB to 4 TB | 256 GB | 128 GB | 16 |
| M80_NVME | 1600 GB | 1600 GB | 128 GB | 16 |
| M200 | 8 GB to 4 TB | 256 GB | 256 GB | 64 |
| M200 Low-CPU | 8 GB to 4 TB | 256 GB | 256 GB | 32 |
| M200_NVME | 3100 GB | 3100 GB | 256 GB | 32 |
| M300 Low-CPU | 8 GB to 4 TB | 512 GB | 384 GB | 48 |
| M300_NVME | 3600 GB | 3600 GB | 384 GB | 48 |
| M400 Low-CPU | 8 GB to 4 TB | 512 GB | 512 GB | 64 |
| M400_NVME | 4000 GB | 4000 GB | 512 GB | 64 |
| M600_NVME | 4000 GB | 4000 GB | 640 GB | 80 |

&#x20;Can use this tier for a multi-cloud cluster.

The `M20` tier includes 1 or 2 vCPUs depending on the Azure (Microsoft Azure) virtual machine series available in the region.

&#x20;Not available in the following regions:

- **germanywestcentral**

- **switzerlandnorth**

- **switzerlandwest**

**Note: Cluster Tier & API Naming Conventions**

For purposes of management with the [Atlas Administration API](https://www.mongodb.com/docs/atlas/api.md#std-label-atlas-api), cluster tier names that are prepended with `R` instead of an `M` (`R40` for example) run a [low-CPU](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-storage-class-ui) version of the cluster. When [creating](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster) or [modifying](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupcluster) a cluster with the API, be sure to specify your desired cluster class by name with the `replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize` attribute.

**Important: Multi-Cloud Low-CPU clusters**

Low-CPU cluster tiers (M40 Low-CPU, M50 Low-CPU, M60 Low-CPU, and so on) are available in [multi-cloud cluster configurations](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region) as long as the cluster tier is available for all the regions that the cluster uses.

Workloads typically require less than `2TB`.

[NVMe clusters](https://www.mongodb.com/docs/atlas/nvme-storage.md#std-label-nvme-storage) don't support [multi-cloud cluster configurations.](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region)

Atlas configures the following resources automatically and does not allow user modification:

Encrypted Storage Volumes

Azure (Microsoft Azure) storage volumes are [always encrypted](https://azure.microsoft.com/en-us/blog/azure-managed-disks-sse/).

## Azure Availability Zones

Azure (Microsoft Azure) maintains multiple data centers within each region. Azure (Microsoft Azure) groups the data centers into [availability zones](https://docs.microsoft.com/en-us/azure/availability-zones/az-overview), which are separate locations within the region. Maintaining data centers in different physical locations helps Azure (Microsoft Azure) tolerate local failures.

Azure (Microsoft Azure) availability zones aren't available in all regions. To learn which Azure (Microsoft Azure) regions maintain availability zones, see the [Azure Region table](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure-supported-regions). In regions where availability zones aren't yet available, Azure (Microsoft Azure) uses [fault domains](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure-fault-domains) to help ensure failure tolerance.

Atlas uses Azure (Microsoft Azure) availability zones automatically when you deploy a dedicated cluster to a region that supports them. Atlas splits the cluster's nodes across availability zones. For example, a three-node replica set cluster would have one node deployed onto each zone. A local failure in the Azure (Microsoft Azure) data center hosting one node doesn't impact the operation of data centers hosting the other nodes.

**Note:**

Regions with availability zones provide higher uptime for dedicated clusters deployed after September 12, 2019. Clusters deployed before September 13, 2019 to regions that now offer availability zones aren't split across availability zones automatically. To learn more about availability zones, see Azure (Microsoft Azure)'s [documentation](https://docs.microsoft.com/en-us/azure/availability-zones/az-overview).

## Azure Fault Domains

Each Azure (Microsoft Azure) region includes a set number of fault domains for failure tolerance. Fault domains consist of a group of virtual machines that share a common power source and network switch. If you deploy your cluster to a region that doesn't support availability zones, Atlas spreads the nodes across the fault domains instead.

Atlas uses [availability sets](https://docs.microsoft.com/en-us/azure/virtual-machines/availability-set-overview) to deploy clusters across fault domains. For regions that have at least three fault domains (3FD), Atlas deploys clusters across three fault domains. For regions that only have two fault domains (2FD), Atlas deploys clusters across two fault domains.

The Atlas [Add New Cluster](https://www.mongodb.com/docs/atlas/tutorial/create-new-cluster.md#std-label-create-new-cluster) form marks regions that support 3FD (Three Fault Domain) clusters as Recommended, as they provide higher availability.

The number of fault domains in a region has no effect on the number of MongoDB nodes Atlas can deploy. MongoDB Atlas clusters are always made of replica sets with a minimum of three MongoDB nodes.

For general information on Azure (Microsoft Azure) fault domains and availability sets, see [Availability Sets Overview](https://docs.microsoft.com/en-us/azure/virtual-machines/availability-set-overview)

### Regions with at Least Three Fault Domains

If the selected Azure (Microsoft Azure) region has at least three fault domains, Atlas clusters are split across three fault domains. For example, a three node replica set cluster would have one node deployed onto each zone.

![A 3-node replica set deployed across a 3-fault-domain Azure region.](/images/microsoft-azure-3az.svg)

3FD (Three Fault Domain) clusters have higher availability compared to 2FD (Two Fault Domain) clusters. However, not all regions support 3FD (Three Fault Domain) clusters.

### Regions with Only Two Fault Domains

If the selected Azure (Microsoft Azure) region has two fault domains, Atlas clusters are split across the two fault domains. For example, a three node replica set cluster would have two nodes deployed to one zone and the remaining node deployed to the other zone.

![A 3-node replica set deployed across a 2-fault-domain Azure region.](/images/microsoft-azure-2az.svg)

2FD (Two Fault Domain) clusters have a higher chance of loss of availability in the event of the loss of an zone than 3FD (Three Fault Domain) clusters. However, where latency or location are a priority, a region that supports 2FD (Two Fault Domain) clusters may be preferred.

For detailed documentation on Azure (Microsoft Azure) storage options, see [High-performance Premium Storage and managed disks for VMs](https://docs.microsoft.com/en-us/azure/storage/storage-premium-storage)

## Adaptive Capacity

Adaptive capacity is a feature that Atlas uses to help keep your cluster available when an Azure (Microsoft Azure) region is temporarily out of capacity for the instance type that your cluster uses. When a region temporarily runs out of capacity for the instance type that your cluster uses, you might be unable to scale the cluster, and Atlas might be unable to replace a node during automatic recovery. To keep your cluster available, Atlas provisions an alternate instance type with available capacity and moves the cluster to it temporarily.

Atlas enables adaptive capacity by default for clusters on Azure (Microsoft Azure) that have at least one node.

**Note:**

Azure (Microsoft Azure) [capacity reservations](https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-overview) aren't the same as Atlas's use of Azure (Microsoft Azure) adaptive capacity. Atlas uses the logic described in this section while respecting Azure (Microsoft Azure) capacity reservations.

### How Adaptive Capacity Works

When Atlas detects that the instance type your cluster uses is out of capacity, Atlas provisions an alternate instance type with available capacity and moves your cluster to it temporarily so the cluster can continue running. Atlas selects the alternate instance type from the same [cluster class](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-storage-class-ui) and doesn't move your data.

Atlas uses adaptive capacity only when you change a cluster's compute resources, such as when you:

- [Create a cluster](https://www.mongodb.com/docs/atlas/tutorial/create-new-cluster.md#std-label-create-new-cluster)

- [Scale a cluster tier](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster)

Atlas doesn't use adaptive capacity when you add nodes or shards.

The alternate instance type keeps your cluster available, and the change causes no downtime. The alternate instance type might provide lower performance than the original instance type, so your application might experience higher CPU use, increased latency, or timeouts until Atlas returns your cluster to its original instance type.

Atlas doesn't change your cluster's price when it provisions an alternate instance type because of capacity constraints.

### Auto-Scaling and Adaptive Capacity

Adaptive capacity also applies when Atlas [auto-scales your cluster tier](https://www.mongodb.com/docs/atlas/cluster-autoscaling.md#std-label-cluster-autoscaling). When an auto-scaling tier change encounters an out-of-capacity error, Atlas completes the operation on an alternate instance type of the target tier.

Atlas doesn't use adaptive capacity when it scales your cluster down. If the lower tier's instance type is out of capacity, Atlas doesn't trigger the downscale event. The cluster stays at its current tier, which prevents an unexpected decrease in performance.

When Atlas replaces a failed or unhealthy node during automatic recovery, adaptive capacity doesn't trigger. If the instance type is out of capacity when a node requires replacement, Atlas might be unable to replace the node until capacity returns. To learn how Atlas maintains cluster availability, see [How does MongoDB Atlas deliver high availability?.](https://www.mongodb.com/docs/atlas/reference/faq/deployment.md#std-label-high-availability)

### Supported Clusters

Atlas uses adaptive capacity for dedicated clusters `M30` and larger that have at least one node. Atlas doesn't use adaptive capacity for `M10` clusters, Free clusters, or Flex clusters.

For `M20` clusters, adaptive capacity is available only in regions that offer alternative instance families as fallback. If the `M20` instance type itself runs out of capacity, Atlas can't fall back to an alternate instance type.

If you select an `M10` or `M20` instance type that has no available capacity in your desired region, Atlas notifies you in the Atlas UI. To deploy your cluster, do one of the following:

- Select a different region.

- Select a larger cluster tier (`M30` or larger).

- Wait for capacity to return.

Capacity shortages are temporary. The instance type becomes available again when the cloud provider restores capacity in the region.

Atlas doesn't use adaptive capacity for clusters that use [NVMe storage](https://www.mongodb.com/docs/atlas/nvme-storage.md#std-label-nvme-storage) because Atlas couples their storage to the instance type.

### Opt Out of Adaptive Capacity

We recommend that you enable adaptive capacity to maintain the availability of your cluster during capacity shortages. Atlas enables adaptive capacity by default. You can opt out of using adaptive capacity for an individual cluster. When you opt out, Atlas keeps your cluster on its original instance type, and a capacity shortage might prevent you from scaling the cluster.

To opt out of Atlas adaptive capacity changes, see [Adaptive Capacity for Azure and Google Cloud Clusters.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-adaptive-capacity-setting)

## Dedicated Search Nodes

### Supported Regions

Atlas supports deploying separate [Search Nodes](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-configure-search-nodes) for `M10` and higher clusters on Azure (Microsoft Azure).

Atlas doesn't support Search Nodes in the following Azure (Microsoft Azure) regions:

| Region Name | Azure Region |
| --- | --- |
| AUSTRALIA_CENTRAL_2 | `australiacentral2` |
| AUSTRALIA_SOUTH_EAST | `australiasoutheast` |
| BRAZIL_SOUTHEAST | `brazilsoutheast` |
| CANADA_EAST | `canadaeast` |
| GERMANY_NORTH | `germanynorth` |
| INDIA_WEST | `westindia` |
| INDIA_SOUTH | `southindia` |
| ITALY_NORTH **(available for low-CPU Search Nodes only)** | `italynorth` |
| JAPAN_WEST | `japanwest` |
| KOREA_SOUTH | `koreasouth` |
| NORWAY_WEST | `norwaywest` |
| SOUTH_AFRICA_WEST | `southafricawest` |
| SPAIN_CENTRAL | `spaincentral` |
| SWEDEN_SOUTH | `swedensouth` |
| SWITZERLAND_WEST | `switzerlandwest` |
| UAE_CENTRAL | `uaecentral` |
| UK_WEST | `ukwest` |
| US_WEST_CENTRAL | `westcentralus` |
| US_WEST | `westus` |

### Available Search Tiers

Atlas provides different [search tiers](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-select-tiers-for-search-nodes) for Search Nodes deployed on Azure (Microsoft Azure).

The following table lists the search tiers available for each class of hardware (low-CPU and high-CPU), with default RAM and storage measured in gibibytes (GiB):

### Low-CPU

| Instance Size | Instance Details |
| --- | --- |
| S40 | **Default RAM**: 16 GiB; **Default Storage**: 75 GiB; **vCPU**: 2 |
| S50 | **Default RAM**: 32 GiB; **Default Storage**: 150 GiB; **vCPU**: 4 |
| S60 | **Default RAM**: 64 GiB; **Default Storage**: 300 GiB; **vCPU**: 8 |
| S80 | **Default RAM**: 128 GiB; **Default Storage**: 600 GiB; **vCPU**: 16 |
| S90 | **Default RAM**: 256 GiB; **Default Storage**: 1200 GiB; **vCPU**: 32 |
| S100 | **Default RAM**: 384 GiB; **Default Storage**: 1800 GiB; **vCPU**: 48 |
| S110 | **Default RAM**: 512 GiB; **Default Storage**: 2400 GiB; **vCPU**: 64 |
| S130 | **Default RAM**: 672 GiB; **Default Storage**: 3600 GiB; **vCPU**: 96 |
| S135 | **Default RAM**: 672 GiB; **Default Storage**: 3800 GiB; **vCPU**: 104 |

## Stream Processing Workspaces

**Important:**

To request an unlisted region, add your feedback to the [MongoDB Feedback Portal](https://feedback.mongodb.com/?category=7529546585152608284). Your input helps prioritize future expansions of Atlas Stream Processing coverage.

Atlas supports deploying [Stream Processing Workspaces](https://www.mongodb.com/docs/atlas/atlas-stream-processing/manage-processing-instance.md#std-label-atlas-sp-manage-spi) in the follow Azure (Microsoft Azure) regions:

### Americas

| Azure Region | Location | Atlas Region |
| --- | --- | --- |
| `eastus` | Virginia, USA | `US_EAST_1` |
| `eastus2` | Virginia, USA | `US_EAST_2` |
| `westus` | California, USA | `US_WEST` |
| `brazilsouth` | Sao Paulo, Brazil | `BRAZIL_SOUTH` |

## Integrations

Along with [global region support](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure), the following product integrations enable applications running on Azure (Microsoft Azure), such as Azure Virtual Machines, Azure Functions, and Azure Container Instances, to use Atlas instances easily and securely.

### Networking Services

- Azure Virtual Network: [Set up network peering connections with Azure](https://www.mongodb.com/docs/atlas/security-vpc-peering.md#std-label-vpc-peering)

- Azure Private Link: [Set up private endpoints with Azure](https://www.mongodb.com/docs/atlas/security-configure-private-endpoints.md#std-label-private-endpoint)

- Azure Key Vault:

  - [Configure Atlas disk encryption with Key Vault](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption)

  - [Configure client-side field level encryption with Key Vault](https://www.mongodb.com/docs/manual/core/security-client-side-encryption-key-management/)

### Security and Identity Services

- Microsoft Entra ID: [Configure federated authentication to the MongoDB UI](https://www.mongodb.com/docs/atlas/security/federated-auth-azure-ad.md#std-label-federated-auth-azure-ad)

- Microsoft Entra ID Domain Services: [Configure database user authentication and authorization](https://www.mongodb.com/docs/atlas/security-ldaps-azure.md#std-label-security-ldaps-azure)

### Procurement

- Azure Marketplace: [Pay for Atlas usage through Azure](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/mongodb.mongodb_atlas_self_serve_prod_2022?tab=Overview)

### Integrations with other Azure Services

- Azure Databricks: [Read and write to Atlas using Databricks and Apache Spark](https://docs.databricks.com/data/data-sources/mongodb.html)

- Azure Data Factory: [Copy data from or to MongoDB Atlas using Azure Data Factory or Synapse Analytics](https://docs.microsoft.com/en-us/azure/data-factory/connector-mongodb-atlas)

- Microsoft Fabric: [Mirror Atlas data to OneLake for near real-time analytics](https://github.com/mongodb-partners/MongoDB_Fabric_Mirroring)

- Azure Native Integration: [Create Atlas organizations from Azure, billed self-service](https://www.mongodb.com/docs/atlas/reference/partner-integrations/azure.md#std-label-azure)

## More Information

For more information on how to use Azure (Microsoft Azure) with Atlas most effectively, review the following best practices, guides, and case studies:

- Power BI Desktop: [Connect to Atlas from Power BI Desktop](https://www.mongodb.com/docs/sql-interface/connect.md#std-label-sql-connect-powerbi)

- Visual Studio (VS) Code: [Work with MongoDB from VS Code](https://code.visualstudio.com/docs/azure/mongodb)
