Ejento AI
GuidesQuickstart
RecipesREST APIsRelease NotesFAQs
GuidesQuickstart
RecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Quickstart
  • How to Setup Ejento on Azure
  • Prerequisites
  • Deployment on Azure
  • Setup After Deployment
    • Custom Domain Set Up
    • Microsoft SSO Authentication
    • Okta SSO Authentication
    • SharePoint Connection Set Up
    • Developer API Set Up
    • Enable Managed Identity
    • Azure AI Search Indexer
    • Container Session Pool Set Up
    • Workload Identity Federation — Azure to GCP Vertex AI
  • MCP Servers
    • Slack
    • Jira
    • Azure
    • Snowflake
    • Azure Cosmos DB
    • Microsoft OAuth MCPs
    • Azure SQL MCP
    • SharePoint
  • Overview
    • Azure Resources
  1. Quickstart

Prerequisites

Before deploying Ejento AI, ensure that you meet the following prerequisites. This will streamline the deployment process and help avoid common issues.

1. Creating an Azure OpenAI / Microsoft Foundry Resource#

When using a new Azure subscription, Microsoft requires a human to review and accept the Responsible AI Terms before a Microsoft Foundry resource can be provisioned. Automated deployments cannot bypass this requirement.
To ensure your Ejento deployment does not fail, please manually create a Microsoft Foundry resource in your subscription and accept the terms ahead of time. This guarantees the rest of the deployment will proceed smoothly without interruption.
Log in to your Azure portal.
Follow the steps in the official Microsoft documentation to create a multiservice resource: Create a multiservice resource for Microsoft Foundry.
WARNING
Make sure you have accepted the "Responsible AI Terms" while creating the Microsoft Foundry resource.
Note: This resource only needs to exist so you can accept the Responsible AI Terms and check quota in the next section. Quota is tracked per subscription, per region, per model — not per resource — so it doesn't matter if Ejento's deployment later creates a different resource in the same subscription and region. The quota pool is shared either way.

2. Access to Azure OpenAI / Microsoft Foundry#

To set up Ejento AI, you need:
(a) Access to Azure OpenAI models, provisioned either as an Azure OpenAI resource or a Microsoft Foundry resource, and
(b) Enough quota (Tokens-per-Minute, TPM) for your target model and region.
Azure OpenAI Service and Microsoft Foundry are separate services. Azure OpenAI is scoped to OpenAI models only. Microsoft Foundry is the broader platform that includes Azure OpenAI plus other model providers, agents, and evaluation tools. Either way, quota is checked and requested through the Microsoft Foundry portal, not through a menu on the resource itself in the Azure portal.

A. Confirm Service Access (Gated)#

Standard Azure OpenAI and Microsoft Foundry model usage does not require Limited Access registration. All Azure customers are eligible for standard access by default.
You only need to register for Limited Access if you specifically need to:
Modify Guardrails (previously called content filters) beyond the standard configurable severity thresholds, or
Modify abuse monitoring.
If your use case needs either of those, submit the relevant registration form and allow 5–10 business days for review. Otherwise, skip this step and go straight to checking quota.

B. Check Your Quota (Per Model, Per Region)#

Quota is allocated per subscription, per region, per model, in TPM. This is a shared pool — it doesn't matter whether the deployment sits on an Azure OpenAI resource or a Microsoft Foundry resource, they draw from the same quota. It also doesn't matter if the resource you use to check quota (created in Section 1) is different from the one Ejento's deployment later creates — as long as it's the same subscription and region, the available quota is the same.
1.
In the Azure portal, open your resource and select Go to Foundry portal.
For Microsoft Foundry Resources:
Step 1 screenshot
For Openai Resources:
Step 1 screenshot
2.
Find Quota in the left-hand navigation:
On the classic Azure OpenAI resource view, it's under Shared resources → Quota.
Step 2 screenshot
On the Microsoft Foundry hub/project resource view, it's under Management center → Quota.
Step 1 screenshot
Step 2 screenshot
3.
On the Quota page:
Use the Group by dropdown to group by Quota type, Region & Model to find your model/region.
Screenshot 2026-07-10 132406.png
Turn on Show all quota to also see models/regions you haven't deployed yet.
new.png
Each row shows quota used vs. total quota approved i.e exact TPM numbers.
4.
Note the available headroom (approved minus used) for your target model and region.
WARNING
Make sure your Azure account has Contributor access on the subscription (or at least the resource group). Without this, the Quota option may not show up in the Foundry portal navigation.
In case, a different UI is visible to you compared to what is shown above, please use the following snapshots to navigate in the new Microsoft Foundry UI.
Picture1.png
Picture2.png
Picture3.png
Select the region you want the model deployment to reside in. You can search the model by their names to filter.
Picture4.png
Picture5.png
Clicking on Request quota will redirect you to a form submission to Microsoft. The form will require some contact information along with the details regarding Model i.e. its category, name, region, etc.
The official SLA from Microsoft support to process the request is 2 days.

C. When You Can Skip the Quota Request#

If you already have ≥ 50,000 TPM for the model and region you plan to use:
You can skip the quota-increase request.
Proceed directly to deployment after completing the steps below.
Ejento AI will run within your assigned TPM.

D. If You Need More Quota#

From the same Quota view in the Foundry portal, expand the model grouping and select Request quota for the model/region you need. Read the instructions carefully and answer each question completely.
new2.png
Allow up to 15 minutes for quota changes to take effect after a request or edit.
WARNING: Make sure your Azure account has Contributor access on the subscription (or at least the resource group)

3. Register Resource Providers in MS Azure Subscription#

Certain Azure Resource Providers must be registered in your subscription to ensure all necessary services are available for Ejento AI.
If you prefer to automate this entire registration process, we have provided an automation script.
➡️ See: Automated Setup Script for Provider Registration
Here are the steps to register them manually:
Go to the Azure portal.
In the search bar, type "Subscriptions" and select it from the search results.
neww.png
Search your subscription in the search bar.
this.png
In the left-hand navigation, under Settings, select Resource providers.
yo.png
Search for and register the following providers:
1.
Microsoft.Resources
2.
Microsoft.CognitiveServices
3.
Microsoft.DBforPostgreSQL
4.
Microsoft.Search
5.
Microsoft.Storage
6.
Microsoft.ServiceBus
7.
Microsoft.Insights
8.
Microsoft.Web
9.
Microsoft.Logic
10.
Microsoft.Communication
11.
Microsoft.Solutions
12.
Microsoft.BackupSolutions
13.
Microsoft.ApiCenter
14.
Microsoft.ApiManagement
15.
Microsoft.HealthcareApis
16.
Microsoft.DocumentDB
17.
Microsoft.DBforMySQL
18.
Microsoft.App
19.
Microsoft.Cdn
20.
Microsoft.Compute
21.
Microsoft.BotService
22.
Microsoft.AlertsManagement
23.
Microsoft.AppConfiguration
24.
Microsoft.Cache
25.
Microsoft.ContainerService
26.
Microsoft.OperationalInsights
27.
Microsoft.Network
28.
Microsoft.Advisor
29.
Microsoft.Automation
30.
Microsoft.AzureArcData
31.
Microsoft.ContainerInstance
32.
Microsoft.DesktopVirtualization
33.
Microsoft.GuestConfiguration
34.
Microsoft.HybridCompute
35.
Microsoft.KeyVault
36.
Microsoft.ManagedIdentity
37.
Microsoft.OperationsManagement
38.
Microsoft.PolicyInsights
39.
Microsoft.RecoveryServices
40.
Microsoft.ResourceHealth
41.
Microsoft.Security
42.
Microsoft.CloudShell
43.
Microsoft.ConnectedCache
44.
Microsoft.Diagnostics
45.
Microsoft.ResourceIntelligence
46.
Microsoft.DataProtection
47.
Microsoft.KubernetesConfiguration
ay.png
Search for each provider and then click Register.

Automated Setup Script for Provider Registration#

This script is intended for developer and admin use during setup or environment provisioning. It automates the registration of all required resource providers to ensure consistency and save time.
This script automates the registration of all required Azure Resource Providers in your subscription using the Azure CLI. It handles login, subscription selection, and provider registration automatically with progress tracking.

Common Requirements#

Dependencies#

Azure CLI installed and added to PATH
Windows installer: https://aka.ms/installazurecli
Verify installation:
az --version
Sign in to the correct Azure tenant:
az login --use-device-code
Verify current tenant:
az account show -o table

Role Requirements (Minimum)#

ActionRequired Role
Register resource providersContributor or Owner role on the subscription
Note:
Ensure you have the appropriate permissions on the subscription before running the script.
The script will prompt you to enter your Subscription ID or Subscription Name.

How to Run the Scripts#

1.
Open any text editor and paste the script below.
2.
Save the file with a meaningful name: resource-provider.ps1
3.
Open PowerShell in the same directory as the script.
4.
Run the script:
.\resource-provider.ps1
The script will:
Log you into Azure (if not already logged in)
Prompt you to enter your Subscription ID or Name
Set the specified subscription as active
Register all required resource providers
Display real-time progress for each provider
Provide a summary of successful and failed registrations

Resource Provider Registration Script: resource-provider.ps1#

# resource-provider.ps1
Write-Host "Logging in to Azure..."
az login | Out-Null

# Prompt for subscription ID or name
$subscriptionId = Read-Host "Enter the Subscription ID or Subscription Name"

Write-Host "Setting subscription: $subscriptionId ..."
az account set --subscription $subscriptionId

$currentSubscription = az account show --query "id" -o tsv
Write-Host "Using subscription: $currentSubscription"
Write-Host ""

$providers = @(
    "Microsoft.Resources",
    "Microsoft.CognitiveServices",
    "Microsoft.DBforPostgreSQL",
    "Microsoft.Search",
    "Microsoft.Storage",
    "Microsoft.ServiceBus",
    "Microsoft.Insights",
    "Microsoft.Web",
    "Microsoft.Logic",
    "Microsoft.Communication",
    "Microsoft.Solutions",
    "Microsoft.BackupSolutions",
    "Microsoft.HealthcareApis",
    "Microsoft.DocumentDB",
    "Microsoft.DBforMySQL",
    "Microsoft.App",
    "Microsoft.Cdn",
    "Microsoft.Compute",
    "Microsoft.BotService",
    "Microsoft.AlertsManagement",
    "Microsoft.AppConfiguration",
    "Microsoft.Cache",
    "Microsoft.ContainerService",
    "Microsoft.OperationalInsights",
    "Microsoft.Network",
    "Microsoft.Advisor",
    "Microsoft.Automation",
    "Microsoft.AzureArcData",
    "Microsoft.ContainerInstance",
    "Microsoft.DesktopVirtualization",
    "Microsoft.GuestConfiguration",
    "Microsoft.HybridCompute",
    "Microsoft.KeyVault",
    "Microsoft.ManagedIdentity",
    "Microsoft.OperationsManagement",
    "Microsoft.PolicyInsights",
    "Microsoft.RecoveryServices",
    "Microsoft.ResourceHealth",
    "Microsoft.Security",
    "Microsoft.CloudShell",
    "Microsoft.ConnectedCache",
    "Microsoft.Diagnostics",
    "Microsoft.ApiCenter",
    "Microsoft.ApiManagement",
    "Microsoft.ResourceIntelligence",
    "Microsoft.DataProtection",
    "Microsoft.KubernetesConfiguration"
)

$total = $providers.Count
$completed = 0
$failed = @()

Write-Host "Starting registration of $total providers..."
Write-Host ""

foreach ($provider in $providers) {
    $completed++
    $remaining = $total - $completed

    Write-Host "[$completed/$total] Registering $provider (Remaining: $remaining)"

    try {
        $state = az provider show --namespace $provider --query "registrationState" -o tsv 2>$null

        if ($state -eq "Registered") {
            Write-Host "  Already registered"
            continue
        }

        az provider register --namespace $provider --only-show-errors 2>$null

    }
    catch {
        Write-Host "  Error occurred for $provider"
    }

    Write-Host ""
}

Write-Host "----------------------------------------------"
Write-Host "Registration Completed"
Write-Host "Total Providers: $total"


if ($failed.Count -gt 0) {
    Write-Host "Failed Providers:"
    $failed | ForEach-Object { Write-Host " - $_" }
} else {
    Write-Host "All providers registered successfully."
}
Note:
If you get an Execution Policy error when running the script, you can temporarily enable it for the current PowerShell session by running the following command:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Security Considerations#

Ensure you have the necessary permissions (Contributor or Owner) on the subscription.
Review the list of providers before running the script.
Keep a record of any failed registrations for troubleshooting.

4. Checking PostgreSQL Quota in Azure#

To ensure your PostgreSQL database runs smoothly, check your quota before deployment. Follow these steps:
Go to the Azure Portal.
Sign in with your credentials.
In the search bar, type "Subscriptions" and select it from the search results.
Choose your subscription from the list.
On the Subscription page, in the left-hand navigation, under Settings, select Usage + quotas.
In Usage + quotas:
bb.png
Filter by Region and Provider Select Azure Postgres and Apply.
aa.png
If you see "The selected provider is not registered..." on this page, go back to Section 3.
c.png
Register the PostgreSQL resource provider first in step 3 — quota data won't display until it's registered.
eh.png
TIP
Ensure there's enough vCore quota available for deploying PostgreSQL to avoid issues.
If quota isn't available in your target region: PostgreSQL must sit in the same region as the rest of the Ejento AI deployment. If the region is still flexible, consider a region with more headroom. Otherwise, use the New Quota Request button at the top of the Usage + quotas page and allow time for Azure to process it.

Tips and Additional Information#

Make sure you have the necessary administrative permissions to perform these actions in your Azure subscription.
Double-check that you are using the correct Azure region for all resources, as this can affect service availability and performance.

Next Steps#

After completing these prerequisites, you are ready to proceed with the deployment on Azure. For detailed deployment instructions, please refer to our Deployment Guide
Previous
How to Setup Ejento on Azure
Next
Deployment on Azure