Regional Availability
Learn about Azure regions and Oracle Database@Azure service availability.
The following sections contain Azure regions and availability zones (AZs) that offer Oracle Database@Azure services.
To provision Oracle Database@Azure resources in a supported region in Azure, your OCI tenancy must be subscribed to the paired OCI region. For example, to provision resources in the Azure East US region, your OCI tenancy must be subscribed to US East (Ashburn). For more information, see Managing Regions and Subscribing to an Infrastructure Region.
Asia Pacific (APAC)
Azure Region and Physical zone | OCI Region | Oracle Exadata Database Service on Dedicated Infrastructure | Oracle Autonomous Database | Oracle Exadata Database Service on Exascale Infrastructure | Oracle Base Database Service | Oracle Database Autonomous Recovery Service |
---|---|---|---|---|---|---|
Australia East (New South Wales): Australia East (New South Wales): |
Australia East (Sydney) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ |
✓ | |
Central India (Pune): |
India West (Mumbai) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
![]() |
||
Japan East (Tokyo, Saitama): Japan East (Tokyo, Saitama): |
Japan East (Tokyo) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]()
|
✓ | |
Japan West (Osaka): |
Japan Central (Osaka) | ✓ ![]() |
✓![]() Oracle Database 19c, 23ai |
![]() |
||
Southeast Asia (Singapore): Southeast Asia (Singapore): |
Singapore (Singapore) |
✓ ![]() |
✓ Oracle Database 19c, 23ai |
![]() |
✓ |
Europe, Middle East, Africa (EMEA)
Azure Region and Physical zone | OCI Region | Oracle Exadata Database Service on Dedicated Infrastructure | Oracle Autonomous Database | Oracle Exadata Database Service on Exascale Infrastructure | Oracle Base Database Service | Oracle Database Autonomous Recovery Service |
---|---|---|---|---|---|---|
France Central (Paris): France Central (Paris): |
France Central (Paris) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
![]() |
✓ | |
Germany North (Berlin): |
Germany Central (Frankfurt) |
✓ |
|
|
||
Germany West Central (Frankfurt): Germany West Central (Frankfurt): |
Germany Central (Frankfurt) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]() |
✓ | |
Italy North (Milan): Italy North (Milan): |
Italy Northwest (Milan) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]() |
✓ | |
North Europe (Ireland): |
Ireland (Dublin) | ✓ ![]() |
|
|
||
Sweden Central (Gävle): Sweden Central (Gävle): |
Sweden Central (Stockholm) | ✓ ![]() |
|
|
||
UAE North (Dubai): |
UAE East (Dubai) | ✓ ![]() |
|
|
||
UAE Centraluaecentral |
UAE Central (Abu Dhabi) | ✓ ![]() |
|
|
||
UK South (London): UK South (London): |
UK South (London) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]() |
✓ | |
UK West (Newport): |
UK West (Newport) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]() |
Latin America (LATAM)
Azure Region and Physical zone | OCI Region | Oracle Exadata Database Service on Dedicated Infrastructure | Oracle Autonomous Database | Oracle Exadata Database Service on Exascale Infrastructure | Oracle Base Database Service | Oracle Database Autonomous Recovery Service |
---|---|---|---|---|---|---|
Brazil South (Sao Paulo State): Brazil South (Sao Paulo State): |
Brazil Southeast (Vinhedo) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]() |
✓ |
North America (NA)
Azure Region and Physical zone | OCI Region | Oracle Exadata Database Service on Dedicated Infrastructure | Oracle Autonomous Database | Oracle Exadata Database Service on Exascale Infrastructure | Oracle Base Database Service | Oracle Database Autonomous Recovery Service |
---|---|---|---|---|---|---|
Canada Central (Toronto): Canada Central (Toronto): |
Canada Southeast (Toronto) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ ![]() |
✓ | |
Central US (Iowa): Central US (Iowa): |
US Midwest (Chicago) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
![]() |
✓ | |
East US (Virginia): East US (Virginia): |
US East (Ashburn) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
✓ |
✓ | |
*East US 2 (Virginia): *East US 2 (Virginia): |
US East (Ashburn) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
![]() |
✓ | |
**South Central US (Texas): **South Central US (Texas): |
US South (Dallas) | ✓ ![]() |
✓ |
|
||
West US (California): |
US West (San Jose) | ✓ ![]() |
✓ Oracle Database 19c, 23ai |
![]() |
✓ | |
West US 2 (Washington): |
US West (Quincy) | ✓ ![]() |
|
|
||
West US 3 (Phoenix): West US 3 (Phoenix): |
US West (Phoenix) | ✓ ![]() |
|
![]() |
*See Prerequisites for the Azure East US 2 Region if you onboarded before April 15, 2025.
**To access this region, contact your Oracle customer sales representative. Because of unavailability of auto-detection of the MTU size, you must set the MTU size on Azure VM manually until the feature is enabled in October, 2025. The following special instruction are applicable only for Mongo database connectivity. This operation normally takes under two minutes to complete:
- To set up the MTU Size, run the following command:
sudo ip link set dev eth0 mtu 1200
- To validate the setting, run the following command:
ip link show eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1200 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 02:00:17:00:44:68 brd ff:ff:ff:ff:ff:ff
Note that eth0
is the interface name, and it could be different in your environment. You can find this value by running ifconfig
.