Feedback Edit

Provision cloud resources

  • Article
  • 19 minutes to read

TeamsFx integrates with Azure and the Microsoft 365 cloud, which allows you to place your application in Azure with a single command. TeamsFx integrates with Azure Resource Manager (ARM), which enables you to provision Azure resources that your application needs for code approach.

Provision using Teams Toolkit in Visual Studio Code

Provision is performed with a single command in Teams Toolkit for Visual Studio Code or TeamsFx CLI. For more information, see provision Azure-based app

Create Resources

When you trigger the provision command in Teams Toolkit or TeamsFx CLI, you can get the following resources:

  • Microsoft Azure Active Directory (Azure AD) application under your Microsoft 365 tenant.
  • Teams app registration under your Microsoft 365 tenant's Teams platform.
  • Azure resources under your selected Azure subscription.

When you create a new project, you can use all the Azure resources. The ARM template defines all the Azure resources and helps to create required Azure resources during provision. When you add new capability resource to an existing project, the updated ARM template reflects the latest change.

Note

Azure services incur costs in your subscription. For more information on cost estimation, see pricing calculator.

The following list shows the resource creation for different types of app and Azure resources:

Resource creation for Teams Tab application
Resource Purpose Description
Azure storage Host your tab app Enables static web app feature to host your tab app
User assigned identity Authenticate Azure service-to-service requests Shared across different capabilities and resources

Resource creation for Teams bot or message extension application
Resource Purpose Description
Azure bot service Registers your app as a bot with the bot framework Connects bot to Teams
App service plan for bot Host the web app of bot Not applicable
Web app for bot Host your bot app Adds user assigned identity to access other Azure resources.
Adds app settings required by TeamsFx SDK
User assigned identity Authenticate Azure service-to-service requests Shared across different capabilities and resources

Resource creation for Azure Functions in the project
Resource Purpose Description
App service plan for function app Host the function app Not applicable
Function app Host your Azure functions APIs Adds a user assigned identity to access other Azure resources.
Adds cross-origin resource sharing (CORS) rule to allow requests from your tab app
Adds an authentication setting that only allows requests from your Teams app.
Adds app settings required by TeamsFx SDK
Azure storage for function app Required to create function app Not applicable
User assigned identity Authenticate Azure service-to-service requests Shared across different capabilities and resources

Resource creation for Azure SQL in the project
Resource Purpose Description
Azure SQL server Host the Azure SQL database instance Allows all Azure services to access the server
Azure SQL database Store data for your app Grants user assigned identity, read or write permission to the database
User assigned identity Authenticate Azure service-to-service requests Shared across different capabilities and resources

Resource creation for Azure API Management in the project
Resource Purpose
Azure AD application for API management service Allows Microsoft Power Platform access APIs managed by API management service
API management service Manage your APIs hosted in function app
API management product Group your APIs, define terms of use, and runtime policies
API management OAuth server Enables Microsoft Power Platform to access your APIs hosted in function app
User assigned identity Authenticate Azure service-to-service requests

Resources created when including Azure Key Vault in the project
Resources Purpose of this resource
Azure Key Vault Service Manage secrets (for example, Azure AD app client secret) used by other Azure services
User Assigned Identity Authenticate Azure service-to-service requests

Customize resource provision

Teams Toolkit enables you to use an infrastructure-as-code approach to define the Azure resources that you want to provision and how you want to configure. The tool uses the ARM template to define Azure resources. The ARM template is a set of bicep files that defines the infrastructure and configuration for your project. You can customize Azure resources by modifying the ARM template. For more information, see bicep document.

Provision with ARM involves changing the following sets of files, parameters, and templates:

  • ARM parameter files (azure.parameters.{your_env_name}.json) located at .fx/configs folder, for passing parameters to templates.

  • ARM template files located at templates/azure, this folder contains following files:

    File Function Allow customization
    main.bicep Provide an entry point for Azure resource provision Yes
    provision.bicep Create and configure Azure resources Yes
    config.bicep Add TeamsFx required configurations to Azure resources Yes
    provision/xxx.bicep Create and configure each Azure resource consumed by provision.bicep Yes
    teamsfx/xxx.bicep Add TeamsFx required configurations to each Azure resource consumed by config.bicep No

Note

When you add resources or capabilities to your project, teamsfx/xxx.bicep is regenerated, you can't customize the same. To modify the bicep files, you can use Git to track your changes to teamsfx/xxx.bicep files, which helps you not lose changes while adding resources or capabilities.

Azure AD parameters

The ARM template files use placeholders for parameters. The purpose of the placeholders is to ensure the creation of new resources for you in new environment. The actual values are resolved from .fx/states/state.{env}.json.

There are two types of parameters such as:

Parameter name Default value place holder Meaning of the place holder How to customize
Microsoft 365 ClientId {{state.fx-resource-aad-app-for-teams.clientId}} Your app's Azure AD app client Id is created during provision Use an existing Azure AD app for your bot
Microsoft 365 ClientSecret {{state.fx-resource-aad-app-for-teams.clientSecret}} Your app's Azure AD app client secret is created during provision Use an existing Azure AD app for your Teams app
Microsoft 365 TenantId {{state.fx-resource-aad-app-for-teams.tenantId}} Tenant Id of your app's Azure AD app Use an existing Azure AD app for your Teams app
Microsoft 365 OAuthAuthorityHost {{state.fx-resource-aad-app-for-teams.oauthHost}} OAuth authority host of your app's Azure AD app Use an existing Azure AD app for your Teams app
botAadAppClientId {{state.fx-resource-bot.botId}} Bot's Azure AD app client Id created during provision Use an existing Azure AD app for your bot
botAadAppClientSecret {{state.fx-resource-bot.botPassword}} Bot's Azure AD app client secret is created during provision Use an existing Azure AD app for your bot
Parameter name Default value place holder Meaning of the place holder How to customize
azureSqlAdmin {{state.fx-resource-azure-sql.admin}} Azure SQL Server admin account you provided during provision Delete the placeholder and fill the actual value
azureSqlAdminPassword {{state.fx-resource-azure-sql.adminPassword}} Azure SQL Server admin password you provided during provision Delete the placeholder and fill the actual value

Referencing environment variables in parameter files

If you don't want to hardcode the values in parameter files, for example, when the value is a secret. The parameter files support referencing the values from environment variables. You can use the syntax {{$env.YOUR_ENV_VARIABLE_NAME}} in parameter values for the tool to resolve the current environment variable.

The following example reads the value of the mySelfHostedDbConnectionString parameter from the environment variable DB_CONNECTION_STRING:

...
    "mySelfHostedDbConnectionString": "{{$env.DB_CONNECTION_STRING}}"
...

Customize ARM template files

If the predefined templates doesn't meet your application requirement, you can customize the ARM templates under templates/azure folder. For example, you can customize the ARM template to create some additional Azure resources for your app. You need to have basic knowledge of the bicep language, which is used to author ARM template. You can get started with bicep at bicep documentation.

Note

The ARM template is shared by all environments. You can use conditional deployment if the provision behavior varies between environments.

To ensure the TeamsFx tool functions properly, ensure you customize ARM template, which satisfies the following requirement. If you use other tool for further development, you can ignore these requirements.

  • Keep the folder structure and file name unchanged. The tool may append new content to existing files when you add more resources or capabilities to your project.
  • Keep the names of the auto-generated parameters and its property names unchanged. The auto-generated parameters may be used when you add more resources or capabilities to your project.
  • Keep the output of the auto-generated ARM template unchanged. You can add additional outputs to the ARM template. The output is .fx/states/state.{env}.json and can be used in other features such as deploy, validate manifest file.

Customization scenarios

You can customize the following scenarios:

Use an existing Azure AD app for your Teams app

You can add the following configuration snippet to .fx/configs/config.{env}.json file to use an Azure AD app created by yourself for your Teams app. To create an Azure AD app, see https://aka.ms/teamsfx-existing-aad-doc.

"auth": {
    "clientId": "<your Azure AD app client id>",
    "clientSecret": "{{$env.ENV_NAME_THAT_STORES_YOUR_SECRET}}",
    "objectId": "<your Azure AD app object id>",
    "accessAsUserScopeId": "<id of the access_as_user scope>"
}

After adding the snippet, add your secret to the related environment variable so the tool can resolve the actual secret during provision.

Note

Ensure not to share the same Azure AD app in multiple environments. If you don't have permission to update the Azure AD app, you can get a warning with instructions about how to manually update the Azure AD app. Follow the instructions to update your Azure AD app after provision.

Use an existing Azure AD app for your bot

You can add following configuration snippet to .fx/configs/config.{env}.json file to use an Azure AD app created by yourself for your bot:

"bot": {
    "appId": "<your Azure AD app client id>",
    "appPassword": "{{$env.ENV_NAME_THAT_STORES_YOUR_SECRET}}"
}

After adding the preceding snippet, add your secret to related environment variable for the tool to resolve the actual secret during provision.

Skip adding user for SQL database

If you have an insufficient permission error when the tool tries to add a user to the SQL database, you can add the following configuration snippet to .fx/configs/config.{env}.json file to skip adding the SQL database user:

"skipAddingSqlUser": true

Specifying the name of Function App instance

You can use contosoteamsappapi for function app instance instead of using the default name.

Note

If you have already provisioned the environment, specifying the name can create a new function app instance for you, instead of renaming the instance created previously.

Follow the steps to specify the name of the Function App instance:

  1. Open .fx/configs/azure.parameters.{env}.json for your current environment.

  2. Add a new property, for example, functionAppName under the provisionParameters section.

  3. Enter a value of functionAppName, for example contosoteamsappapi.

  4. Final parameter file is shown in the following snippet:

    {
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "provisionParameters": {
        "value": {
            "functionAppName": "contosoteamsappapi"
            ...
            }
        }
    }
}

To add other Azure resource or storage to the application, consider the following scenario:

Add Azure storage to your Azure function backend to store blob data. There's no auto flow to update the bicep template with the Azure storage support. However, you can edit the bicep file and add the resource. The steps are as follows:

  1. Create a tab project.

  2. Add function to the project. For more information, see add resources.

  3. Declare the new storage account in ARM template. You can declare the resource at templates/azure/provision/function.bicep directly. You can declare the resources in other places.

    var applicationStorageAccountName = 'myapp${uniqueString(resourceGroup().id)}'
resource applicationStorageAccount 'Microsoft.Storage/storageAccounts@2021-06-01' = {
    name: applicationStorageAccountName
    location: resourceGroup().location
    kind: 'Storage'
    sku: {
        name: 'Standard_LRS'
    }
}

  4. Update the Azure function app settings with Azure storage connection string in templates/azure/provision/function.bicep. Add the following snippet to functionApp resource's appSettings array:

    {
    name: 'MyAppStorageAccountConnectionString'
    value: 'DefaultEndpointsProtocol=https;AccountName=${applicationStorageAccount.name};AccountKey=${listKeys(applicationStorageAccount.id, '2021-06-01').keys[0].value}'
}

  5. You can update your function with Azure storage output bindings.

Provision using Teams Toolkit in Visual Studio

The following steps help you to provision cloud resources using Visual Studio:

Sign in to your Microsoft 365 account

  1. Open Visual Studio 2022.

  2. Open the Microsoft Teams app project.

  3. Select Project > Teams Toolkit > Prepare Teams App Dependencies.

    Prepare teams app dependencies

  4. Select Sign in... to sign in to your Azure account.

    Sign in to Microsoft 365

    Note

    If you are already singed in, your username displays, or you have an option to switch account.

  5. Your default web browser opens to let you sign in to the account.

  6. Select Continue after you've signed into your account.

    Confirm by selecting continue

Sign in to your Azure account

  1. Open Visual Studio 2022.

  2. Open the Teams App project.

  3. Select Project > Teams Toolkit > Provision in the cloud.

    Sign in to Azure account

  4. Select Sign in... to sign in to your Azure account.

    Sign in to your Azure account

    Note

    If you're already signed in, your username is displayed, or you have an option to switch account.

    After sign in to your Azure account using your credentials, the browser closes automatically.

To provision cloud resources

After you open your project in Visual Studio:

  1. Select Project > Teams Toolkit > Provision in the cloud.

    Provision in cloud

    Provision window appears.

  2. Enter the following details to provision your resources:

    1. Select your Subscription name from the dropdown list.

    2. Select your Resource group from the dropdown list.

    3. Select your Region from the dropdown list.

      Note

      You can create new Resource group by selecting New....

    4. Select Provision.

    Select resource group

  3. The dialog appears mentioning that charges may be added as per Azure usage. Select Provision.

    Provision warning

    The provisioning process creates resources in the Azure cloud. You can monitor the progress by observing the Teams Toolkit output window.

  4. You're prompted after provisioning is complete. Select View Provisioned Resources to view all the resources that were provisioned.

    View provisioned resources

Create resources

When you trigger provision command in Teams Toolkit or TeamsFx CLI, you can create the following resources:

  • Microsoft Azure Active Directory (Azure AD) application under your Microsoft 365 tenant.
  • Teams app registration under your Microsoft 365 tenant's Teams platform.
  • Azure resources under your selected Azure subscription.

When you create a new project, you also need to create Azure resources. The Azure Resource Manager (ARM) templates defines all the Azure resources and helps you to create required Azure resources during provision.

The following list shows the resource creation for different types of app and Azure resources:

Resource creation for Teams Tab application
Resource Purpose Description
App service plan Hosts your web app of tab Not applicable
App service Hosts your Blazor tab app Not applicable
Manage identity Authenticate Azure service-to-service requests Shares across different capabilities and resources

Resource creation for Teams message extension application
Resource Purpose Description
Azure bot Registers your app as a bot with the bot framework Connects bot to Teams
App Service plan Hosts your web bot app Not applicable
App Service Hosts your bot app Adds user assigned identity to access other Azure resources
Manage identity Authenticate Azure service-to-service requests Shares across different capabilities and resources

Resource creation for Teams command bot application
Resource Purpose Description
Azure bot Registers your app as a bot with the bot framework Connects bot to Teams
App service plan Hosts your web bot app Not applicable
App service Hosts your bot app Adds user assigned identity to access other Azure resources
Manage identity Authenticate Azure service-to-service requests Shares across different capabilities and resources

Resource creation for Teams notification bot with HTTP trigger (Web API server) application
Resource Purpose Description
Azure bot Registers your app as a bot with the bot framework Connects bot to Teams
App service plan Hosts your web bot app Not applicable
App service Host your bot app Adds user assigned identity to access other Azure resources
Managed Identity Authenticate Azure service-to-service requests Shares across different capabilities and resources

Resource creation for Teams notification bot with HTTP trigger (Azure function) application
Resource Purpose Description
Azure bot Registers your app as a bot with the bot framework Connects bot to Teams
Manage identity Authenticates Azure service-to-service requests Shared across different capabilities and resources
Storage account Helps to create function app Not applicable
App service plan Hosts the function bot App Not applicable
Function app Hosts your bot app - Adds user assigned identity to access other Azure resources
- Adds Cross-origin resource sharing (CORS) rule to allow requests from your tab app
- Adds authentication setting that only allows requests from your Teams app
- Adds app settings required by TeamsFx SDK

Resource creation for Teams notification bot with timer trigger (Azure function) application
Resource Purpose Description
Azure bot Registers your app as a bot with the bot framework Connects bot to Teams
Manage identity Authenticate Azure service-to-service requests Shares across different capabilities and resources
Storage account Helps to create function app Not applicable
App service plan Hosts the function bot app Not applicable
Function app Hosts your bot app - Adds user assigned identity to access other Azure resources
-Adds Cross-origin resource sharing (CORS) rule to allow requests from your tab app
- Adds authentication setting that only allows requests from your Teams app
- Adds app settings required by TeamsFx SDK

Resource creation for Teams notification bot with HTTP trigger + timer trigger (Azure function) application
Resource Purpose Description
Azure bot Registers your app as a bot with the bot framework. Connects bot to Teams.
Manage identity Authenticate Azure service-to-service requests. Shares across different capabilities and resources.
Storage account Helps to create function app. Not applicable
App service plan Hosts the function bot app. Not applicable
Function App Hosts your bot app. -Adds user assigned identity to access other Azure resources.
-Adds Cross-origin resource sharing (CORS) rule to allow requests from your tab app.
-Adds authentication setting that only allows requests from your Teams app.
-Adds app settings required by TeamsFx SDK.

Manage your resources

You can sign in to Azure portal and manage all resources created by Teams Toolkit.

  • You can select resource group from the existing list or the new resource group that you've created.
  • You can see the details of the resource group you've selected in the overview section of the table of content.

Customize resource provision

Teams Toolkit enables you to use an infrastructure for the code approach to define the Azure resources that you want to provision. You can change the configuration in Teams Toolkit as per your requirement.

Teams Toolkit uses ARM template to define Azure resources. The ARM template is a set of bicep files that defines the infrastructure and configuration for your project. You can customize Azure resources by modifying the ARM template. For more information, see bicep document.

Provision with ARM involves changing the following sets of files, parameters, and templates:

  • ARM parameter files (azure.parameters.{your_env_name}.json) located in .fx/configs folder, for passing parameters to templates.

  • ARM template files located in templates/azure folder contains following files:

    File Function Allow customization
    main.bicep Provide entry point for Azure resource. provision Yes
    provision.bicep Create and configure Azure resources. Yes
    config.bicep Add TeamsFx required configurations to Azure resources. Yes
    provision/xxx.bicep Create and configure each Azure resource consumed by provision.bicep. Yes
    teamsfx/xxx.bicep Add TeamsFx required configurations to each Azure resource consumed by config.bicep. No

Note

After you add resources or capabilities to your project, teamsfx/xxx.bicep is regenerated. To modify the bicep files, you can use Git to track your changes to teamsfx/xxx.bicep files. This doesn't make you lose any changes while adding resources or capabilities to your project.

The ARM template files use placeholders for parameters. The purpose of the placeholders is to ensure that new resources can be created in the new environment. The actual values are resolved from .fx/states/state.{env}.json file.

Parameter name Default value place holder Meaning of the place holder How to customize
Microsoft 365 ClientId {{state.fx-resource-aad-app-for-teams.clientId}} Your app's Azure AD app client ID created during provision. Use an existing Azure AD app for your Teams app
Microsoft 365 ClientSecret {{state.fx-resource-aad-app-for-teams.clientSecret}} Your app's Azure AD app client secret created during provision. Use an existing Azure AD app for your Teams app
Microsoft 365 TenantId {{state.fx-resource-aad-app-for-teams.tenantId}} Tenant ID of your app's Azure AD app. Use an existing Azure AD app for your Teams app
Microsoft 365 OAuthAuthorityHost {{state.fx-resource-aad-app-for-teams.oauthHost}} OAuth authority host of your app's Azure AD app. Use an existing Azure AD app for your Teams app
botAadAppClientId {{state.fx-resource-bot.botId}} Bot's Azure AD app client ID created during provision. Use an existing Azure AD app for your bot
botAadAppClientSecret {{state.fx-resource-bot.botPassword}} Bot's Azure AD app client secret created during provision. Use an existing Azure AD app for your bot

Reference environment variables in parameter files

When the value is secret, then you don't need to hardcode them in parameter file. The parameter files support referencing the values from the environment variables. You can use this syntax {{$env.YOUR_ENV_VARIABLE_NAME}} in the parameter values for Teams Toolkit to resolve from current environment variable.

The following example reads the value of the mySelfHostedDbConnectionString parameter from the environment variable DB_CONNECTION_STRING:

...
    "mySelfHostedDbConnectionString": "{{$env.DB_CONNECTION_STRING}}"
...

Customize ARM template files

If the predefined templates don't meet your application requirement, you can customize the ARM templates under templates/azure folder. For example, you can customize the ARM template to create some extra Azure resources for your app. You need to have basic knowledge of bicep language, which is used to author ARM template.

To ensure the TeamsFx tool functions properly, customize ARM template that satisfies the following requirements:

  • Ensure that the folder structure and file name remain unchanged. The tool may append new content to the existing files when you add more resources or capabilities to your project.
  • Ensure that the name of auto-generated parameters and its property names remain unhanged. The auto-generated parameters may be used when you add more resources or capabilities to your project.
  • Ensure that the output of auto-generated ARM template is unchanged as well. You can add more outputs to ARM template. The output is .fx/states/state.{env}.json and can be used in other features such as deploy and validate manifest files.

Customize Teams app

You can customize your bot or the Teams app by adding configuration snippets to use an Azure AD app created by you. Perform in the following ways to customize the Teams app:

Use an existing Azure AD app for your Teams app

You can add the following configuration snippet .fx/configs/config.{env}.json to use an Azure AD app created by you for your Teams app. To create an Azure AD app, follow the link https://aka.ms/teamsfx-existing-aad-doc.

"auth": {
    "clientId": "<your Azure AD app client id>",
    "clientSecret": "{{$env.ENV_NAME_THAT_STORES_YOUR_SECRET}}",
    "objectId": "<your Azure AD app object id>",
    "accessAsUserScopeId": "<id of the access_as_user scope>"
}

After adding the snippet, add your client secret to the related environment variable for Teams Toolkit to resolve the actual client secret during provision.

Note

Ensure not to share the same Azure AD app in multiple environments. If you don't have permission to update the Azure AD app, you get a warning with instructions to manually update the Azure AD app. Follow these instructions to update your Azure AD app after provision.

Use an existing Azure AD app for your bot

You can add the following configuration snippet to .fx/configs/config.{env}.json to use the Azure AD app created for your bot:

"bot": {
    "appId": "<your Azure AD app client id>",
    "appPassword": "{{$env.ENV_NAME_THAT_STORES_YOUR_SECRET}}"
}

After adding the snippet, add your client secret to the related environment variable for Teams Toolkit to resolve the actual client secret during provision.

Skip adding user for SQL database

If you get an insufficient permission error when Teams Toolkit tries to add user to SQL database, add the following configuration snippet to .fx/configs/config.{env}.json to skip adding SQL database user:

"skipAddingSqlUser": true

See also