Ejento AI
GuidesQuickstart
RecipesREST APIsRelease NotesFAQs
GuidesQuickstart
RecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Setup After Deployment
  • 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. Setup After Deployment

Enable Managed Identity

Managed Identity Enablement Guide#

1. Overview#

A Managed Identity allows an application to authenticate to other Azure services without storing credentials in code or configuration. Enabling it is a prerequisite for any downstream integration (such as Azure Key Vault, Storage Accounts, or Azure databases) that relies on identity-based authentication.
This guide provides step-by-step instructions for enabling System Assigned Managed Identity on Azure App Services, Function Apps, and Container Apps.
Note: Every App Service, Function App, and Container App must have a System Assigned Managed Identity enabled. Repeat the steps in this guide for each individual resource.

2. Prerequisites#

Before proceeding, ensure you have:
Access to the Azure Portal
Contributor or Owner permissions on the target Azure resources

3. Enable Managed Identity#

3.1 App Services#

Follow these steps to enable a System Assigned Managed Identity for an App Service:
1.
Sign in to the Azure Portal.
2.
Navigate to App Services.
3.
Select the required App Service.
1.png
2.png
4.
From the left navigation menu, select Identity.
5.
Under System assigned, set Status to On.
6.
Click Save.
3.png
Result: Azure creates a System Assigned Managed Identity and generates a Principal (Object) ID for the App Service.

3.2 Function Apps#

Follow these steps to enable a System Assigned Managed Identity for a Function App:
1.
Sign in to the Azure Portal.
2.
Navigate to Function Apps.
3.
Select the required Function App.
4.
From the left navigation menu, select Identity.
5.
Under System assigned, set Status to On.
6.
Click Save.
Result: Azure creates a System Assigned Managed Identity and generates a Principal (Object) ID for the Function App.

3.3 Container Apps#

Follow these steps to enable a System Assigned Managed Identity for a Container App:
1.
Sign in to the Azure Portal.
2.
Navigate to Container Apps.
3.
Select the required Container App.
4.png
4.
Select the required container app.
5.png
5.
From the left navigation menu, select Security → Identity.
6.
Under System assigned, set Status to On.
7.
Click Save.
6.png
Result: Azure creates a System Assigned Managed Identity and generates a Principal (Object) ID for the Container App.

3.4 Verification#

After enabling Managed Identity, verify the following for each resource:
A Principal (Object) ID has been generated.
The identity is visible under Identity → System assigned in the Azure Portal.
The resource can now be granted access to other Azure resources using Azure RBAC.

3.5 Repeat for All Resources#

Repeat the steps in Section 3 for every applicable resource:
All App Services
All Function Apps
All Container Apps

4. Completion#

After completing the above steps for all applicable resources:
✅ System Assigned Managed Identity is enabled.
✅ A unique Principal (Object) ID has been generated for each resource.
✅ The resources are now ready to be granted identity-based access to Azure services such as Azure Key Vault, Storage Accounts, databases, and other supported resources.
Previous
Developer API Set Up
Next
Azure AI Search Indexer