Quickstart: Provision an Azure Spring Apps Standard consumption and dedicated plan service instance

Άρθρο
01/30/2024

Note

Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.

This article applies to: ✔️ Standard consumption and dedicated (Preview) ❌ Basic/Standard ❌ Enterprise

This article describes how to create a Standard consumption and dedicated plan in Azure Spring Apps for application deployment.

Prerequisites

An Azure subscription. If you don't have a subscription, create a free account before you begin.
(Optional) Azure CLI version 2.45.0 or higher. Use the following command to install the Azure Spring Apps extension: az extension add --name spring

Provision a Standard consumption and dedicated plan instance

You can use either the Azure portal or the Azure CLI to create a Standard consumption and dedicated plan.

Important

The Consumption workload profile has a pay-as-you-go billing model, with no starting cost. You're billed for the dedicated workload profile based on the provisioned resources. For more information, see Workload profiles in Consumption + Dedicated plan structure environments in Azure Container Apps (preview) and Azure Spring Apps pricing.

Azure portal
Azure CLI

Use the following steps to create an instance of Azure Spring Apps using the Azure portal.

Open the Azure portal.
In the search box, search for Azure Spring Apps, and then select Azure Spring Apps from the results.
On the Azure Spring Apps page, select Create.
Fill out the Basics form on the Azure Spring Apps Create page using the following guidelines:
- Project Details
  - Subscription: Select the subscription you want to be billed for this resource.
  - Resource group: Select an existing resource group or create a new one.
- Service Details
  - Name: Create the name for the Azure Spring Apps service instance. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number.
  - Location: Currently, only the following regions are supported: Australia East, Central US, East US, East US 2, West Europe, East Asia, North Europe, South Central US, UK South, West US 3.
- Plan: Select Standard Consumption and dedicated for the Pricing tier option.
- App Environment
  - Select Create new to create a new Azure Container Apps environment, or select an existing environment from the dropdown menu.
Fill out the Basics form on the Create Container Apps environment page. Use the default value asa-standard-consumption-app-env for the Environment name and choose Consumption and Dedicated workload profiles for the Plan.
At this point, you've created an Azure Container Apps environment with a default standard consumption workload profile. If you wish to add a dedicated workload profile to the same Azure Container Apps environment, you can select the Workload profiles tab and select Add workload profile.
Select Review and create.
On the Azure Spring Apps Create page, select Review and Create to finish creating the Azure Spring Apps instance.

Note

Optionally, you can also create an Azure Container Apps environment with your own virtual network. For more information, see Quickstart: Create an Azure Spring Apps instance in an Azure Container Apps environment with a virtual network.

The following sections show you how to create an instance of Azure Spring Apps using the Azure CLI.

Create an Azure Container Apps environment

An Azure Container Apps environment creates a secure boundary around a group of applications. Apps deployed to the same environment are deployed in the same virtual network and write logs to the same Log Analytics workspace.

You can create the Azure Container Apps environment in one of two ways:

Using your own virtual network. For more information, see Quickstart: Create an Azure Spring Apps instance in an Azure Container Apps environment with a virtual network.
Using a system assigned virtual network, as described in the following procedure.

Use the following command to sign in to Azure:
```
az login
```
Use the following command to install the Azure Container Apps extension for the Azure CLI:
```
az extension add --name containerapp --upgrade
```
Use the following command to register the Microsoft.App namespace:
```
az provider register --namespace Microsoft.App
```
If you haven't previously used the Azure Monitor Log Analytics workspace, register the Microsoft.OperationalInsights provider by using the following command:
```
az provider register --namespace Microsoft.OperationalInsights
```

Use the following commands to create variables to store name and location information. Be sure to replace the placeholder values with your own values.

export RESOURCE_GROUP="<resource-group-name>"
export LOCATION="eastus"
export AZURE_CONTAINER_APPS_ENVIRONMENT="<Azure-Container-Apps-environment-name>"

Use the following command to create a resource group:

az group create \
    --name $RESOURCE_GROUP \
    --location $LOCATION

Use the following command to create the Azure Container Apps environment:

az containerapp env create \
    --resource-group $RESOURCE_GROUP \
    --name $AZURE_CONTAINER_APPS_ENVIRONMENT \
    --location $LOCATION \
    --enable-workload-profiles

At this point, you've created an Azure Container Apps environment with a default standard consumption workload profile. You can also add a dedicated workload profile to the same Azure Container Apps environment by using the following command:
```
az containerapp env workload-profile set \
    --resource-group $RESOURCE_GROUP \
    --name $AZURE_CONTAINER_APPS_ENVIRONMENT \
    --workload-profile-name my-wlp \
    --workload-profile-type D4 \
    --min-nodes 1 \
    --max-nodes 2
```

Deploy an Azure Spring Apps instance

Use the following steps to deploy the service instance:

Use the following command to install the latest Azure CLI extension for Azure Spring Apps:
```
az extension remove --name spring && \
az extension add --name spring
```
Use the following command to register the Microsoft.AppPlatform provider for the Azure Spring Apps:
```
az provider register --namespace Microsoft.AppPlatform
```

Use the following commands to create variables to store name and location information. You can skip the first three variables if you set them in the previous section. Be sure to replace the placeholder values with your own values.

export RESOURCE_GROUP="<resource-group-name>"
export LOCATION="eastus"
export AZURE_CONTAINER_APPS_ENVIRONMENT="<Azure-Container-Apps-environment-name>"

export AZURE_SPRING_APPS_INSTANCE="<Azure-Spring-Apps-instance-name>"
export MANAGED_ENV_RESOURCE_ID=$(az containerapp env show \
    --resource-group $RESOURCE_GROUP \
    --name $AZURE_CONTAINER_APPS_ENVIRONMENT \
    --query id \
    --output tsv)

Use the following command to deploy a Standard consumption and dedicated plan for an Azure Spring Apps instance on top of the container environment. Create your Azure Spring Apps instance by specifying the resource of the Azure Container Apps environment you created.
```
az spring create \
    --resource-group $RESOURCE_GROUP \
    --name $AZURE_SPRING_APPS_INSTANCE \
    --managed-environment $MANAGED_ENV_RESOURCE_ID \
    --sku StandardGen2 \
    --location $LOCATION
```
After the deployment, an infrastructure resource group is created in your subscription to host the underlying resources for the Azure Spring Apps Standard consumption and dedicated plan instance. The resource group is named {AZURE_CONTAINER_APPS_ENVIRONMENT}_SpringApps_{SPRING_APPS_SERVICE_ID}, as shown with the following command:
```
export SERVICE_ID=$(az spring show \
    --resource-group $RESOURCE_GROUP \
    --name $AZURE_SPRING_APPS_INSTANCE \
    --query properties.serviceId \
    --output tsv)
export INFRA_RESOURCE_GROUP=${AZURE_CONTAINER_APPS_ENVIRONMENT}_SpringApps_${SERVICE_ID}
echo ${INFRA_RESOURCE_GROUP}
```

Clean up resources

Be sure to delete the resources you created in this article when you no longer need them. To delete the resources, just delete the resource group that contains them. You can delete the resource group using the Azure portal. Alternatively, to delete the resource group by using Azure CLI, use the following commands:

echo "Enter the Resource Group name:" &&
read resourceGroupName &&
az group delete --name $resourceGroupName &&
echo "Press [ENTER] to continue ..."

Next steps

Create an Azure Spring Apps Standard consumption and dedicated plan instance in an Azure Container Apps environment with a virtual network