- Prerequisites
- Where to Configure Azure OpenAI
- Enabling Azure OpenAI
- Required Configuration Fields
- Model and Deployment Mapping
- Advanced Azure Settings
- Testing the Azure OpenAI Connection
- Common Azure Configuration Issues
- Cost and Quota Management
- Using Azure OpenAI Alongside Other Providers
- Feature Compatibility
- What Happens After Configuration
This guide explains how to configure Azure OpenAI in Aimogen. Azure OpenAI provides OpenAI models hosted on Microsoft’s infrastructure and is often used in enterprise environments where reliability, regional compliance, or Azure-native integrations are required.
Azure OpenAI behaves very similarly to OpenAI inside Aimogen, but the setup requires additional configuration details.
Prerequisites #
Before configuring Azure OpenAI, you must have:
- An active Microsoft Azure account
- An Azure OpenAI resource created
- At least one deployed model in Azure
- An Azure OpenAI API key
- The endpoint URL for your Azure OpenAI resource
Azure OpenAI access must already be approved in your Azure subscription.
Where to Configure Azure OpenAI #
Azure OpenAI settings are located in:
Aimogen → API Keys
All Azure-related behavior is controlled from this panel unless overridden at feature or workflow level.
Enabling Azure OpenAI #
To enable Azure OpenAI in Aimogen:
- Open the ‘Settings’ menu -> ‘API Keys’ tab.
- Toggle ‘Main API Service Provider Selector‘ to ‘Microsoft Azure’
- Enter the required credentials (your API key in ‘Azure API Keys‘ + endpoint in the ‘Azure OpenAI Endpoint‘ settings field + the deployment name for the models you want to use, in the ‘Azure OpenAI Deployment Name For …’ – be sure to deploy any models you want to use in Azure and remember the name you gave to them, as you need to enter the same name in the plugin settings also)
- Save settings
Once enabled, Azure OpenAI becomes available as a selectable provider throughout Aimogen.
Required Configuration Fields #
Azure OpenAI requires more fields than standard OpenAI.
API Key #
This is the key generated in the Azure OpenAI resource.
Endpoint URL #
This is the base URL of your Azure OpenAI resource, for example:https://your-resource-name.openai.azure.com/
API Version #
Azure OpenAI requires an API version. Aimogen provides compatible defaults, but you can change this if needed for newer deployments.
Azure OpenAI Deployment Name For … #
Unlike OpenAI, Azure uses deployments instead of model names.
These settings are required and will need to have added the deployment names you created for each model you want to use in the plugin. You must enter the exact deployment name you created in Azure for:
- Chat / text generation
- Embeddings
- Image generation (if applicable)
Aimogen maps its internal model selection to Azure deployment names.
Model and Deployment Mapping #
In Azure OpenAI, models are not selected directly. Instead:
- You deploy a model in Azure
- You give the deployment a name
- Aimogen references that deployment name
For example:
- A GPT-style chat model deployment for content and chat
- An embedding model deployment for embeddings
Each deployment must exist and be active in Azure, or requests will fail.
Advanced Azure Settings #
Depending on your Aimogen version, Azure-specific options may include:
- Request timeout settings
- Streaming support
- Rate-limit handling
- Deployment-specific overrides
These settings are useful in high-load or enterprise scenarios.
Testing the Azure OpenAI Connection #
After configuration:
- Go to the Chatbot to test an AI model provided by Azure.
- Aimogen sends a minimal request to your deployment
- A success or error message is displayed
A successful test confirms:
- API key validity
- Correct endpoint URL
- Deployment name correctness
- Azure resource availability
If the test fails, the error message usually indicates which field is incorrect.
Common Azure Configuration Issues #
Most Azure OpenAI issues come from:
- Incorrect endpoint URL
- Typo in deployment name
- Using the wrong API version
- Deployment not fully provisioned yet
- Azure subscription limits reached
Unlike OpenAI, Azure errors are often strict and descriptive. Always check the error message in Aimogen logs.
Cost and Quota Management #
Azure OpenAI usage is billed through your Azure subscription.
Consider:
- Azure region pricing differences
- Deployment-specific quotas
- Subscription-level limits
Aimogen does not manage Azure billing or quotas; it only reports execution errors.
Using Azure OpenAI Alongside Other Providers #
Azure OpenAI can be used together with other providers.
Common setups include:
- Azure OpenAI for primary content generation
- OpenAI for images or assistants
- Claude or Gemini for editing
- Groq for real-time chat
Provider selection is configurable per feature or workflow.
Feature Compatibility #
Azure OpenAI supports most OpenAI-based features, including:
- Content generation and editing
- Chatbots
- Embeddings
- Assistants (depending on deployment)
Some features depend on Azure deployment capabilities and model support.
What Happens After Configuration #
Once Azure OpenAI is enabled and tested:
- It appears as a selectable provider everywhere in Aimogen
- Existing workflows can switch to it without changes
- No plugin restart is required
Azure OpenAI is ideal when you need OpenAI-quality models within a Microsoft-managed environment. Aimogen integrates with it at the same execution level as other providers, making it a drop-in alternative rather than a separate system.
