Repository navigation
[Enhancement]: Add Azure Managed Identity (MI) Support for Blob Storage Authentication #10784
Copy link
Copy link
Open
Labels
✨ enhancementNew feature or requestNew feature or request🗺️ Backend Infracodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Cloud Infra Configcodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Core Infra & Seccodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ File Storagecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Platform Securitycodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
Description
What features would you like to see added?
I would like LibreChat to support Azure Managed Identity (MI) authentication for Azure Blob Storage. Specifically, LibreChat should be able to authenticate to Azure Blob Storage without requiring a connection string or account key, by leveraging:
DefaultAzureCredentialManagedIdentityCredential- Pod-assigned or user-assigned managed identities on AKS
This enables secure, keyless, identity-based access to storage using Azure AD, fully aligned with cloud-native best practices.
More details
Currently, LibreChat supports Azure Blob Storage only via:
AZURE_STORAGE_CONNECTION_STRING- Account name + account key (
AZURE_STORAGE_ACCOUNT_NAME,AZURE_STORAGE_ACCESS_KEY) - (Partial) SAS tokens
However, LibreChat does not support Azure AD / Managed Identity authentication.
For AKS and other Azure environments, using connection strings or storage keys is discouraged because:
- Keys cannot be scoped per service
- Keys cannot be revoked per identity
- Rotation is difficult
- Connection strings give full storage account access
- Managed Identity provides least-privilege, identity-based access without secrets
Azure Blob Storage supports MI authentication via the official Azure SDK:
import { DefaultAzureCredential } from "@azure/identity";
const credential = new DefaultAzureCredential();
const client = new BlobServiceClient(
`https://${account}.blob.core.windows.net`,
credential
);
### Which components are impacted by your request?
_No response_
### Pictures
_No response_
### Code of Conduct
- [x] I agree to follow this project's Code of ConductReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
✨ enhancementNew feature or requestNew feature or request🗺️ Backend Infracodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Cloud Infra Configcodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Core Infra & Seccodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ File Storagecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Platform Securitycodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
Activity
rahepler2 commentedon May 30, 2026
I added a PR to address this. Would love your feedback on it: #13411