|
| 1 | +--- |
| 2 | +title: Upgrade from Azure OpenAI to Azure AI Foundry |
| 3 | +titleSuffix: Azure AI Foundry |
| 4 | +description: Upgrade seamlessly from Azure OpenAI to Azure AI Foundry and unlock advanced capabilities like a broader model catalog, agents service, and evaluation tools. |
| 5 | +ms.author: sgilley |
| 6 | +author: sdgilley |
| 7 | +ms.reviewer: deeikele |
| 8 | +ms.date: 09/03/2025 |
| 9 | +ms.service: azure-ai-foundry |
| 10 | +ms.topic: how-to |
| 11 | +--- |
| 12 | + |
| 13 | +# Upgrade from Azure OpenAI to Azure AI Foundry |
| 14 | + |
| 15 | +The Azure AI Foundry resource type offers a superset of capabilities compared to the Azure OpenAI resource type. It enables access to a broader model catalog, agents service, and evaluation capabilities. |
| 16 | + |
| 17 | +An upgrade option is available for you to keep your existing Azure OpenAI API endpoint, state of work, and security configurations, without creating a new Azure AI Foundry resource. |
| 18 | + |
| 19 | + |
| 20 | +## Benefits of upgrading |
| 21 | + |
| 22 | +Upgrading to Azure AI Foundry unlocks the following capabilities. |
| 23 | + |
| 24 | +|Feature|Azure OpenAI|Azure AI Foundry| |
| 25 | +|---|---|---| |
| 26 | +| Models sold directly by Azure | Azure OpenAI only | Azure OpenAI, Black Forest Labs, DeepSeek, Meta, xAI, Mistral, Microsoft | |
| 27 | +| Partner & Community Models sold through Marketplace - Stability, Bria, Cohere, etc.| | ✅ | |
| 28 | +| Azure OpenAI API (batch, stored completions, fine-tuning, evaluation, etc.) | ✅ | ✅ | |
| 29 | +| Agent service | | ✅ | |
| 30 | +| Azure Foundry API | | ✅ | |
| 31 | +| AI Services (Speech, Vision, Language, Content Understanding) | | ✅ | |
| 32 | + |
| 33 | +Your existing resource configurations and state remain preserved including: |
| 34 | + |
| 35 | +* Resource name |
| 36 | +* Azure resource tags |
| 37 | +* Network configurations |
| 38 | +* Access and identity configurations |
| 39 | +* API endpoint and API key |
| 40 | +* Custom Domain Name |
| 41 | +* Existing state including fine-tuning jobs, batch, stored completions, etc. |
| 42 | + |
| 43 | +## Limitations |
| 44 | + |
| 45 | +Backend limitations: |
| 46 | + |
| 47 | +* Azure OpenAI resources using **customer-managed keys** for encryption aren't supported for upgrade. |
| 48 | +* The AI Foundry resource type doesn't support configuring Weights & Biases. |
| 49 | + |
| 50 | +Foundry portal limitations: |
| 51 | + |
| 52 | +* The evaluations view doesn't yet support all the capabilities available in the Azure OpenAI evaluations view. |
| 53 | + |
| 54 | +## Support level post-upgrade |
| 55 | + |
| 56 | +The upgrade converts your Azure OpenAI resource type to Azure AI Foundry resource type. Both services are generally available and supported before and after the upgrade. This is an early access feature. If needed, you can [roll back to your previous setup](#rollback-to-azure-openai). |
| 57 | + |
| 58 | +## How to upgrade |
| 59 | + |
| 60 | +As a prerequisite to upgrade, managed identity must be enabled on your Azure OpenAI resource. Upgrade can be completed via the Azure AI Foundry portal or using Azure Bicep or Resource Manager templates. |
| 61 | + |
| 62 | +# [Foundry portal](#tab/portal) |
| 63 | + |
| 64 | +**Option 1: Use Azure AI Foundry portal** |
| 65 | + |
| 66 | +1. Sign in to [Azure AI Foundry](https://ai.azure.com/?cid=learnDocs). |
| 67 | +1. Select your Azure OpenAI resource. |
| 68 | +1. On the overview page, find the banner **Make the switch to AI Foundry** and select **Switch now.** |
| 69 | +1. Provide the name for your first project. A project is a folder to organize your work in Azure AI Foundry. Your first 'default' project has backwards compatibility with your previous work in Azure OpenAI. |
| 70 | +1. Confirm to start the upgrade. The upgrade takes up to two minutes. |
| 71 | + |
| 72 | +> [!NOTE] |
| 73 | +> While the upgrade capability is rolling out to all users, you might not see the upgrade action yet in the portal for your resource. Use Azure Bicep or wait until you see the banner. |
| 74 | +
|
| 75 | +# [Azure Bicep](#tab/bicep) |
| 76 | + |
| 77 | +**Option 2: Use an Azure Bicep template** |
| 78 | + |
| 79 | +Starting with your existing Azure OpenAI template configuration, set the following properties: |
| 80 | + |
| 81 | +* Update kind from value 'OpenAI' => 'AIServices' |
| 82 | +* Set allowProjectManagement: True |
| 83 | +* Configure managed identity |
| 84 | + |
| 85 | +Sample configuration: |
| 86 | + |
| 87 | +```bicep |
| 88 | +resource aiFoundry 'Microsoft.CognitiveServices/accounts@2025-06-01' = { |
| 89 | + name: aiFoundryName // Your existing resource name |
| 90 | + location: location |
| 91 | + identity: { |
| 92 | + type: 'SystemAssigned' |
| 93 | + } |
| 94 | + sku: { |
| 95 | + name: 'S0' |
| 96 | + } |
| 97 | + kind: 'AIServices' // Update from 'OpenAI' |
| 98 | + properties: { |
| 99 | + // required to work in AI Foundry |
| 100 | + allowProjectManagement: true |
| 101 | +
|
| 102 | + // Needed for capabilities that require EntraID authentication |
| 103 | + customSubDomainName: aiFoundryName |
| 104 | + disableLocalAuth: true |
| 105 | + } |
| 106 | +} |
| 107 | +``` |
| 108 | + |
| 109 | +Run the template using Azure CLI options or your VS Code extension for Bicep as a patch operation on your current resource. |
| 110 | + |
| 111 | +--- |
| 112 | + |
| 113 | +## Rollback to Azure OpenAI |
| 114 | + |
| 115 | +In case you run into any issues, a rollback option is available. As prerequisite to rollback, you're required to delete any of the following configurations first: |
| 116 | + |
| 117 | +* Projects |
| 118 | +* Connections |
| 119 | +* Non-Azure OpenAI model deployments |
| 120 | + |
| 121 | +Then, use either AI Foundry Portal or ARM template to rollback: |
| 122 | + |
| 123 | +# [Foundry portal](#tab/portal) |
| 124 | + |
| 125 | +**Option 1: Use Azure AI Foundry portal** |
| 126 | + |
| 127 | +1. Navigate to management center in the left bottom of your screen. |
| 128 | +1. On your resource overview page, find the rollback option. |
| 129 | +1. Select **Rollback**. |
| 130 | + |
| 131 | +:::image type="content" source="../media/upgrade-azure-openai/rollback.png" alt-text="Screenshot shows the rollback option in the Azure AI Foundry portal." lightbox = "../media/upgrade-azure-openai/rollback.png"::: |
| 132 | + |
| 133 | +# [Azure Bicep](#tab/bicep) |
| 134 | + |
| 135 | +**Option 2: Use an Azure Bicep template** |
| 136 | + |
| 137 | +To rollback, convert your template configuration back to 'OpenAI' as kind. |
| 138 | + |
| 139 | + ```bicep |
| 140 | + resource aiFoundry 'Microsoft.CognitiveServices/accounts@2025-06-01' = { |
| 141 | + name: aiFoundryName |
| 142 | + location: location |
| 143 | + identity: { |
| 144 | + type: 'SystemAssigned' |
| 145 | + } |
| 146 | + sku: { |
| 147 | + name: 'S0' |
| 148 | + } |
| 149 | + kind: 'OpenAI' |
| 150 | + properties: { |
| 151 | +
|
| 152 | + // Defines developer API endpoint subdomain |
| 153 | + customSubDomainName: aiFoundryName |
| 154 | + disableLocalAuth: true |
| 155 | + } |
| 156 | + ``` |
| 157 | + |
| 158 | + Run the template using Azure CLI options or your VS Code extension for Bicep as a patch operation on your current resource. |
| 159 | + |
| 160 | +--- |
| 161 | + |
| 162 | +## How to inspect whether a resource has been upgraded |
| 163 | + |
| 164 | +The following Azure resource property is available to inspect whether a resource was previously upgraded to AI Foundry. |
| 165 | + |
| 166 | +```bicep |
| 167 | +{ |
| 168 | + { |
| 169 | + // Read only properties if your resource was upgraded: |
| 170 | + previouskind: "OpenAI" |
| 171 | + } |
| 172 | +} |
| 173 | +``` |
| 174 | + |
| 175 | +Not sure who upgraded your resource to Azure AI Foundry? You can inspect the activity sign in the Azure portal: |
| 176 | + |
| 177 | +1. Use Azure Activity Logs (under "Monitoring") to see if an upgrade operation was performed. |
| 178 | +1. Filter by "Write" operations on the storage account. |
| 179 | +1. Look for operations listed as `Microsoft.CognitiveServices/accounts/write`. |
| 180 | + |
| 181 | +## Related content |
| 182 | + |
| 183 | +* [Choose an Azure resource type for AI foundry](../concepts/resource-types.md) |
0 commit comments