-
Notifications
You must be signed in to change notification settings - Fork 198
Upgrade to support unify config and aad manifest
We will update the configuration files so that your project is compatible with the latest Teams Toolkit features, including a consistent configuration file schema, a single Teams app manifest template across local and remote environments, and an AAD manifest template file.
Important Notes: If you collaborate on this project with your co-workers, please ensure your team members update the Teams Toolkit extension to the latest version after committing the changes with this upgrade.
Teams Toolkit continues to improve your Teams application development experience. We are upgrading the Teams app project structure so that you can:
- Use a consistent schema to manage configuration settings for local and remote environments.
- Use a single Teams application manifest template across local and remote environments.
- Use AAD manifest template to customize your AAD app.
- Allow to add single sign-on (SSO) feature for Bot (hosting on Azure App Service), Static Launch Page, and Embed existing web App
After the project upgrade, the new file structure will consist:
-
localSettings.json
will be updated toconfig.local.json
to ensure consistency between local and remote environment configuration settings. -
manifest.local.template.json
andmanifest.remote.template.json
will be merged into a single manifest template file namedmanifest.template.json
to make managing manifest template files easy. - Update
.fx\configs\projectSettings.json
capabilities to include TabSSO and/or BotSSO based on original project capabilities. - AAD manifest template file will be added to
templates\appPackage\aad.template.json
- The required resource access information in
permissions.json
file will be merged intoaad.template.json
file andpermissions.json
file will be deprecated.
Your existing localSettings.json
, manifest.local.template.json
, manifest.remote.template.json
and projectSettings.json
files will be backed up in .backup
folder.
Since Teams Toolkit will use manifest.remote.template.json
as a single manifest template file after the upgrade, if you have customized the manifest.local.template.json
, you will need to update the manifest.template.json
to include your change.
If anything went wrong after the upgrade process, you could restore your old project configuration files by:
- Copy the .backup/.fx folder to your project root path.
- Copy the .backup/templates folder to your project root path.
- Delete
config.local.json
,manifest.template.json
andaad.template.json
if needed.
Build Custom Engine Copilots
- Build a basic AI chatbot for Teams
- Build an AI agent chatbot for Teams
- Expand AI bot's knowledge with your content
Scenario-based Tutorials
- Send notifications to Teams
- Respond to chat commands in Teams
- Respond to card actions in Teams
- Embed a dashboard canvas in Teams
Extend your app across Microsoft 365
- Teams tabs in Microsoft 365 and Outlook
- Teams message extension for Outlook
- Add Outlook Add-in to a Teams app
App settings and Microsoft Entra Apps
- Manage Application settings with Teams Toolkit
- Manage Microsoft Entra Application Registration with Teams Toolkit
- Use an existing Microsoft Entra app
- Use a multi-tenant Microsoft Entra app
Configure multiple capabilities
- How to configure Tab capability within your Teams app
- How to configure Bot capability within your Teams app
- How to configure Message Extension capability within your Teams app
Add Authentication to your app
- How to add single sign on in Teams Toolkit for Visual Studio Code
- How to enable Single Sign-on in Teams Toolkit for Visual Studio
Connect to cloud resources
- How to integrate Azure Functions with your Teams app
- How to integrate Azure API Management
- Integrate with Azure SQL Database
- Integrate with Azure Key Vault
Deploy apps to production