Quickstart: Create a service connection in Azure Container Apps from the Azure portal

This quickstart shows you how to connect Azure Container Apps to other Cloud resources using the Azure portal and Service Connector. Service Connector lets you quickly connect compute services to cloud services, while managing your connection's authentication and networking settings.

Important

This feature in Container Apps is currently in preview. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

Prerequisites

Sign in to Azure

Sign in to the Azure portal at https://portal.azure.com/ with your Azure account.

Create a new service connection

You'll use Service Connector to create a new service connection in Container Apps.

  1. To create a new service connection in Container Apps, select the Search resources, services and docs (G +/) search bar at the top of the Azure portal, type Container Apps in the filter and select Container Apps.

    Screenshot of the Azure portal, selecting Container Apps.

  2. Select the name of the Container Apps resource you want to connect to a target resource.

  3. Select Service Connector (preview) from the left table of contents. Then select Create.

    Screenshot of the Azure portal, selecting Service Connector and creating new connection.

  4. Select or enter the following settings.

    Setting Example Description
    Container my-container The container of your container app.
    Service type Storage - Blob The type of service you're going to connect to your container.
    Subscription my-subscription The subscription that contains your target service (the service you want to connect to). The default value is the subscription that this container app is in.
    Connection name storageblob_700ae The connection name that identifies the connection between your container app and target service. Use the connection name provided by Service Connector or choose your own connection name.
    Storage account my-storage-account The target storage account you want to connect to. If you choose a different service type, select the corresponding target service instance.
    Client type .NET The application stack that works with the target service you selected. The default value is None, which will generate a list of configurations. If you know about the app stack or the client SDK in the container you selected, select the same app stack for the client type.

    Screenshot of the Azure portal, filling out the Basics tab.

  5. Select Next: Authentication to choose an authentication method: system-assigned managed identity (SMI), user-assigned managed identity (UMI), connection string, or service principal.

    System-assigned managed identity is the recommended authentication option. Select System-assigned managed identity to connect through an identity that's automatically generated in Azure Active Directory and tied to the lifecycle of the service instance.

  6. Select Next: Networking to select the network configuration and select Configure firewall rules to enable access to target service so that your container can reach the Blob Storage.

    Screenshot of the Azure portal, connection networking set-up.

  7. Select Next: Review + Create to review the provided information. Running the final validation takes a few seconds.

    Screenshot of the Azure portal, Container App connection validation.

  8. Select Create to create the service connection. The operation can take up to a minute to complete.

View service connections

  1. Container Apps connections are displayed under Settings > Service Connector.

  2. Select > to expand the list and see the environment variables required by your application.

  3. Select Validate check your connection status, and select Learn more to review the connection validation details.

    Screenshot of the Azure portal, get connection validation result.

Next steps

Check the guide below for more information about Service Connector: