Integration Provider - Azure
TrueFoundry supports integrating with multiple Azure services like ABS, ACR, File Vault, AKS, Azure OpenAI Models, Azure Repos etc.
To integrate any of the above services, you simply need to add your Azure account as a provider account and add integrations for the same as shown below:
Share access with users, teams or everyone in your TrueFoundry account
As shown in the previous slides, you can share access of each integration with users, teams or everyone in your TrueFoundry account. This would allow them to view and use the integration. Only tenant-admins can edit the integrations.
Azure Blob Storage(ABS) Integration
Follow the steps below to connect your Azure blob storage to TrueFoundry:
- Create a Azure Storage account in your resource group
- Instance details - You must
Geo-redundant storage
to make sure your data is available through other regions in case of region unavailability. - Security - Make sure
- DISABLE
Allow enabling anonymous access on individual containers
- ENABLE
Enable storage account key access
- DISABLE
- Network access - ENABLE
Allow public access from all networks
- Recovery - You can keep it to default for 7 days.
- Instance details - You must
- Create an Azure container inside the above storage account.
- Search for
CORS
from the left panel and forBlob service
(optional forFile service
Queue service
andTable Service
, only apply the change if you are using them) select the below options- Allowed Origins -
*
or your control plane URL - Allowed Methods -
GET, POST, PUT
- Allowed Headers -
*
- Exposed Headers -
Etag
- MaxAgeSeconds -
3600
- Allowed Origins -
- Collect the following information
- Standard endpoint - Endpoint of the blob storage Once the container is created we need to get the standard endpoint of the blob storage along with the container which will look something like this. Replace this with your storage account name and the container name.
https://*mystorageaccount*.blob.core.windows.net/*mycontainer*/
- Connection string - From the Azure portal in your storage account, head over to the
Security + Networking
section underAccess keys
which will contain theConnection String
.
- Standard endpoint - Endpoint of the blob storage Once the container is created we need to get the standard endpoint of the blob storage along with the container which will look something like this. Replace this with your storage account name and the container name.
- Head over to the Integrations tab from the sidebar and follow the steps shown in the previous demo to complete the integration.
Azure Container Registry(ACR) Integration
To add Azure Container registry, follow the steps below:
- Create an Azure container registry in your Azure resource group.
- Connectivity access - Public from (all networks)
- Collect the following information
- Your container registry name will be in the format
<name>.azurecr.io
- The username and password for the container registry can be copied from Access keys under Settings in the left panel of the Azure portal in your container registry resource.
Enable the Admin User to copy the username and the password
- Your container registry name will be in the format
- Head over to the Integrations tab from the sidebar and follow the steps shown in the previous demo to complete the integration.
Azure AKS integration
To add support of Azure AKS integration, follow the below steps
- Create an Azure Ad App registration
- Create a client secret for the Azure AD application with custom expiration set to a long time. You can do this from the left panel -> Certificates and Secrets.
- Head over to the AKS cluster and add Reader role to the above Azure AD application. This can be done from Azure portal -> kubernetes services -> AKS cluster -> Access Control.
- Head over to the Integrations tab from the sidebar and follow the steps shown in the previous demo to complete the integration.
Updated 3 days ago