+> * `SuggestedActions` are only supported for one-on-one chat bots with both text based messages and Adaptive Cards.

+> * `SuggestedActions` aren't supported for chat bots with attachments for any conversation type.

+### Example channelData object

+The following code shows an example of channelData object (channelCreated event):

+You must have a short and long description of your app. App description helps improve app discoverability in the Teams store.

+During submission, you're asked to categorize your app. App category helps improve your app discoverability in the Teams store. You can categorize your app based on the following categories:

+You must have a short and long description for your app. App description helps improve your app discoverability in the Teams store. The descriptions in your app configuration and Partner Center must be the same.

+ 1. You've correctly mentioned the `subscriptionOffer` details in your [app manifest](../../../resources/schem#subscriptionoffer) (previously called Teams app manifest) in the format `publisherId.offerId`.

+## Teams store search experience

+After an app is published to the Teams store, users can find apps by going to the **Apps** icon from the left pane in Teams. Users can use the search box in the upper left corner or browse by category to see if a particular app or program has a version for Teams.

+Teams provides intelligent search experience by matching the user input to the fields provided by the developer across appName, publisher name, short description, long description, specific keywords and category names in app manifest or Partner Center. The search results display apps that are closest match to the user's specified characters.

+ Title: Request device permissions for your Microsoft Teams app

+ :::image type="content" source="../../assets/images/tabs/device-permissions-new.png" alt-text="Screenshot shows the device permissions." lightbox="~/assets/images/tabs/device-permissions-new.png":::

+**Add a Teams channel**

+1. Select **Home**.

+1. Go to **Resources** > **Recent**. Select your bot from the list of available resources.

+1. In the left pane, select **Channels**. Under **Available Channels**, select **Microsoft Teams**.

+ :::image type="content" source="../../assets/images/include-files/channels-teams.png" alt-text="Screenshot shows the selection of Teams in channels.":::

+1. Select the checkbox to accept the **Terms of Service**.

+1. Select **Agree**.

+ :::image type="content" source="../../assets/images/include-files/terms-service.png" alt-text="Screenshot shows the acceptance of terms of service.":::

+1. Select **Apply**.

+ :::image type="content" source="../../assets/images/include-files/teams-apply.png" alt-text="Screenshot shows the Microsoft Teams as messaging to apply.":::

+**Add a scope**

+1. Select **+ Add a scope**.

+ :::image type="content" source="../../assets/images/include-files/select-add-scope.png" alt-text="Screenshot shows the selection to Add a Scope.":::

+1. Enter **access_as_user** as the **Scope name**.

+1. Under **Who can consent?**, select **Admins and users**.

+1. Update the values for the rest of the fileds as follows:

+ * Enter **Teams can access the userΓÇÖs profile** as **Admin consent display name**.

+ * Enter **Allows Teams to call the appΓÇÖs web APIs as the current user** as **Admin consent description**.

+ * Enter **Teams can access the user profile and make requests on the userΓÇÖs behalf** as **User consent display name**.

+ * Enter **Enable Teams to call this appΓÇÖs APIs with the same rights as the user** as **User consent description**.

+ Ensure that **State** is set to **Enabled**.

+1. Select **Add scope**.

+ The following image shows the fields and the values:

+ :::image type="content" source="../../assets/images/include-files/set-add-scope.png" alt-text="Screenshot shows the values filled in the field to Add a scope.":::

+ > [!NOTE]

+ > The **Scope name** must match with the **Application ID** URI with `/access_as_user` appended at the end.

+ <!-- `api://d4b8****.ngrok.io/00000000-0000-0000-0000-000000000000/access_as_user`-->

+ :::image type="content" source="../../assets/images/include-files/add-scope.png" alt-text="Screenshot shows the details in Scopes.":::

+**API Permission**

+1. In the left pane, select **API permissions**.

+ > [!NOTE]

+ > Users need to consent to the API permissions only if the Azure AD app is registered in a different tenant.

+1. Select **+ Add a permission**.

+ :::image type="content" source="../../assets/images/include-files/add-permission.png" alt-text="Screenshot show the option to select Add permission.":::

+1. Select **Microsoft Graph**.

+1. Select **Delegated permissions**.

+1. Select the following permissions:

+ * **OpenId permissions** > **email**, **offline_access**, **openid**, **profile**.

+ * **User** > **User.Read**.

+1. Select **Add permissions**.

+ :::image type="content" source="../../assets/images/include-files/select-add-permission.png" alt-text="Screenshot show the option to select permissions.":::

+**Azure app registration**

+1. Go to the [Azure portal](https://portal.azure.com/).

+1. Select **Azure Active Directory**.

+1. In the left pane, select **App registrations**.

+1. Under **Owned applications**, select your bot from the list of available applications.

+ :::image type="content" source="../../assets/images/include-files/app-registrations.png" alt-text="Screenshot shows the selection of App registration and bot created in Azure portal.":::

+1. In the left pane, under **Manage**, select **Expose an API**.

+1. Next to **Application ID URI**, select **Add**.

+ :::image type="content" source="../../assets/images/include-files/expose-api-add.png" alt-text="Screenshot shows the Application ID URI add option.":::

+1. Update the **Application ID URI** in the `api://your-devtunnel-domain/{AppID}` or `api://your-ngrok-domain/{AppID}`format and select **Save**.

+ :::image type="content" source="../../assets/images/include-files/app-id-uri.png" alt-text="Screenshot shows the option to add redirect uri and save.":::

+ The following image shows the domain name:

+ :::image type="content" source="../../assets/images/include-files/app-id-uri-output.png" alt-text="Screenshot shows the redirect uri":::

+ <!--

+ > [!NOTE]

+ > If you're using a tunneling service such as ngrok, ensure you update the value whenever your ngrok subdomain changes.

+ > For example: `api://f631****.ngrok.io/92c11075-c629-4a1e-ab58-02b4fd4204c2`, where `f631****.ngrok.io` is the new ngrok subdomain name.

+ -->

+**Create an Azure bot resource**

+1. Go to the [Azure portal](https://portal.azure.com/).

+1. Select **Create a resource**.

+1. In the search box, enter **Azure Bot**.

+1. Select **Enter**.

+1. Select **Azure Bot**.

+1. Select **Create**.

+ :::image type="content" source="../../assets/images/include-files/azure-bot.png" alt-text="Screenshot shows the creation of Azure bot.":::

+1. Enter the bot name in **Bot handle**.

+1. Select your **Subscription** from the dropdown list.

+1. Select your **Resource group** from the dropdown list.

+ :::image type="content" source="../../assets/images/include-files/create-azure-bot.png" alt-text="Screenshot shows the option resource group and subscription in the Azure portal.":::

+

+ If you don't have an existing resource group, you can create a new resource group. To create a new resource group, select **Create new** > enter the resource name > select **OK**. Select a location from **New resource group location** dropdown list.

+

+ :::image type="content" source="../../assets/images/include-files/new-resource-location.png" alt-text="Screenshot shows the new resource group option in Azure portal.":::

+1. Under **Microsoft App ID**, select **Type of App** as **Multi Tenant**.

+1. In the **Creation type**, by default, **Create new Microsoft App ID** is selected.

+ You can also select **Use existing app registration** and enter existing **App ID**, **App tenant ID**, and **MSI resource ID**.

+ > [!NOTE]

+ > You can't create more than one bot with the same **Microsoft App ID**.

+1. Select **Review + create**.

+ :::image type="content" source="../../assets/images/include-files/review-create-app-id.png" alt-text="Screenshot shows the creation of new bot.":::

+1. If the validation passes, select **Create**.

+ The bot takes a few minutes to provision.

+1. Select **Go to resource**.

+ :::image type="content" source="../../assets/images/include-files/resource-deployment.png" alt-text="Screenshot shows the Go to resource option in the Azure portal.":::

+

+ You have successfully created your Azure bot.

+ :::image type="content" source="../../assets/images/include-files/azure-bot-created-output.png" alt-text="Screenshot shows the output of a bot.":::

+**Client Application**

+Under **Authorized client applications**, identify the applications that you want to authorize for your appΓÇÖs web application.

+1. Select **+ Add a client application**.

+ :::image type="content" source="../../assets/images/include-files/add-client-application.png" alt-text="Screenshot shows the option to Select client application.":::

+1. Add Teams mobile or desktop and Teams web application.

+ 1. For Teams mobile or desktop: Enter the **Client ID** as `1fec8e78-bce4-4aaf-ab1b-5451cc387264`.

+

+ :::image type="content" source="../../assets/images/include-files/client-id-mobile-desktop.png" alt-text="Screenshot shows the mobile or desktop Client ID application.":::

+

+ 1. For Teams web: Enter **Client ID**: `5e3ce6c0-2b1f-4285-8d4b-75ee78787346`.

+

+ :::image type="content" source="../../assets/images/include-files/client-id-web.png" alt-text="Screenshot shows the web Client ID application.":::

+1. Select the **Authorized scopes** checkbox.

+1. Select **Add application**.

+ :::image type="content" source="../../assets/images/include-files/authorized-scope-add.png" alt-text="Screenshot shows the option to select authorized scopes and add application.":::

+ The following image displays the **Client Id**:

+ :::image type="content" source="../../assets/images/include-files/add-client-application-output.png" alt-text="Screenshot shows the output of Client applications.":::

+**Update the manifest and OAuth service connection**

+1. In the left pane, select **Manifest**.

+1. Set the value for the `accessTokenAcceptedVersion` to `2` and select **Save**.

+ :::image type="content" source="../../assets/images/include-files/manifest-token.png" alt-text="Screenshot shows the manifest option and accesstoken details in Azure portal.":::

+ > [!NOTE]

+ > If you're already testing your bot in Teams, sign out of this app and Teams. To see this change, sign in again.

+1. Select **Home**.

+1. Go to **Resources** > **Recent**. Select your bot from the list of available resources.

+1. In the left pane, select **Configuration**.

+1. Select **Add OAuth Connection Settings**.

+1. Under **New Connection Setting**, update the following details:

+ * **Name**: Enter **name** for your new connection setting. You can use the name in the settings of your bot service code.

+ * **Service Provider**: From the dropdown list, select **Azure Active Directory V2**.

+ * **Client ID**: Update your **Microsoft App ID**.

+ * **Client secret**: Update the client secret **Value**.

+ * **Token Exchange URL**: Update the **Application ID URI**.

+ * **Tenant ID**: Enter **common**.

+ * **Scopes**: Enter **User.Read**.

+1. Select **Save**.

+ :::image type="content" source="../../assets/images/include-files/new-connection-setting.png" alt-text="Screenshot shows the values added to set OAuth connection.":::

+**Add a web authentication**

+1. In the left pane, select **Authentication**.

+ > [!NOTE]

+ > If an app isn't granted IT admin consent, users must provide consent the first time they use an app.

+

+1. Select **Add a platform** > **Web**.

+ :::image type="content" source="../../assets/images/include-files/platform-web.png" alt-text="Screenshot shows the selection of web authentication.":::

+1. Enter the redirect URI for your app by appending `auth-end` to the fully qualified domain name. For example, `https://your-devtunnel-domain/auth-end` or `https://your-ngrok-domain/auth-end`.

+1. Under **Implicit grant and hybrid flows**, select the **ID tokens** and **Access tokens** checkboxes.

+1. Select **Configure**.

+ :::image type="content" source="../../assets/images/include-files/configure-web.png" alt-text="Screenshot shows the option to add redirect uri and select implicit grant and hybrid flows.":::

+1. Open [Microsoft-Teams-Samples](https://github.com/OfficeDev/Microsoft-Teams-Samples).

+1. Select **Code**.

+1. From the dropdown menu, select **Open with GitHub Desktop**.

+ :::image type="content" source="../../assets/images/include-files/clone-repository.png" alt-text="Screenshot show the option to clone repository in local.":::

+1. Select **Clone**.

+**Create a client secret**

+The following steps are applicable only if you've created a new **Microsoft App ID**. To create client secret, follow these steps:

+1. In the left pane, select **Configuration**.

+ > [!TIP]

+ > Save the **Microsoft App ID** or **Client ID** for future reference.

+1. Next to **Microsoft App ID**, select **Manage Password**.

+ :::image type="content" source="../../assets/images/include-files/manage-bot-label.png" alt-text="Screenshot show the manage password option.":::

+1. Under **Client secrets**, select **+ New client secret**.

+ :::image type="content" source="../../assets/images/include-files/new-client-secret.png" alt-text="Screenshot show the selection of new client secret.":::

+ The **Add a client secret** window appears.

+1. Enter **Description**.

+1. Select **Add**.

+ :::image type="content" source="../../assets/images/include-files/add-client-secret.png" alt-text="Screenshot show the client secret description option to add.":::

+1. Under **Value**, select **Copy to clipboard** to save the client secret value for your reference.

+ :::image type="content" source="../../assets/images/include-files/client-secret-value.png" alt-text="Screenshot show the option to copy the client secret ID value to copy value to clipboard.":::

+1. Open Visual Studio.

+1. Select **Create a new project**.

+

+ :::image type="content" source="../../assets/images/include-files/create-new-project.png" alt-text="Screenshot shows the selection to create a new project.":::

+1. In the search box, enter **ASP.NET**. From the search results, select **ASP.NET Core Web App**.

+1. Select **Next**.

+ :::image type="content" source="../../assets/images/include-files/template-search.png" alt-text="Screenshot shows the search and selection of the template.":::

+1. Enter **Project name** and select **Next**.

+ :::image type="content" source="../../assets/images/include-files/project-name.png" alt-text="Screenshot shows the project name to enter.":::

+1. Select **Create**.

+ :::image type="content" source="../../assets/images/include-files/additional-information.png" alt-text="Screenshot shows the project additional information.":::

+ An overview window appears.

+ :::image type="content" source="../../assets/images/include-files/asp-net-output.png" alt-text="Screenshot shows the overview window.":::

+1. In the debug dropdown, select **Dev Tunnels (no active tunnel) > Create A Tunnel...**.

+ :::image type="content" source="../../assets/images/include-files/create-tunnel.png" alt-text="Screenshot shows the dropdown to select the dev tunnels.":::

+ A pop-up window appears.

+1. Update the following details in the pop-up window.

+ 1. **Account**: Enter a Microsoft or GitHub account.

+ 1. **Name**: Enter a name for your tunnel.

+ 1. **Tunnel Type**: From the dropdown, select **Temporary**.

+ 1. **Access**: From the dropdown, select **Public**.

+1. Select **OK**.

+ :::image type="content" source="../../assets/images/include-files/create-tunnel-details.png" alt-text="Screenshot shows the details to update for creation of tunnel.":::

+ A pop-up window appears showing that dev tunnel is successfully created.

+1. Select **OK**.

+ :::image type="content" source="../../assets/images/include-files/tunnel-created.png" alt-text="Screenshot shows the pop-up message that the tunnel is created.":::

+ You can find the tunnel you've created in the debug dropdown as follows:

+ :::image type="content" source="../../assets/images/include-files/tunnel-active.png" alt-text="Screenshot shows the tunnel is active and selected.":::

+

+1. Select **F5** to run the application in the debug mode.

+1. If a **Security Warning** dialog appears, select **Yes**.

+ :::image type="content" source="../../assets/images/include-files/security-warning.png" alt-text="Screenshot shows the dialog box to accept the security warning.":::

+ A pop-up window appears.

+1. Select **Continue**.

+ :::image type="content" source="../../assets/images/include-files/developer-tunnel.png" alt-text="Screenshot shows the url for the tunnel.":::

+ The dev tunnel home page opens in a new browser window and the dev tunnel is now active.

+ :::image type="content" source="../../assets/images/include-files/developer-tunnel-web.png" alt-text="Screenshot shows the dev tunnel welcome page in browser.":::

+1. Go to Visual Studio, select **View > Output**.

+1. From the output console dropdown menu, select **Dev Tunnels**.

+ The output console shows the dev tunnel URL.

+

+ :::image type="content" source="../../assets/images/include-files/output-console-url.png" alt-text="Screenshot shows the url in the Visual Studio output console.":::

+

+**To add a messaging endpoint**

+# [dev tunnel](#tab/dev)

+

+1. Use the dev tunnel URL in the output console as the messaging endpoint.

+ :::image type="content" source="../../assets/images/include-files/output-console-url.png" alt-text="Screenshot shows the url in the Visual studio output console.":::

+1. Go to Azure portal and select the bot that you've created. In the left pane, under **Settings**, select **Configuration**.

+1. Update the **Messaging endpoint** in the format `https://your-devtunnel-domain/api/messages`.

+ :::image type="content" source="../../assets/images/include-files/devtunnels-messaging-endpoint.png" alt-text="Screenshot shows the messaging endpoint adding api.":::

+1. Select **Apply**.

+ You have successfully set up a bot in Azure Bot service.

+# [ngrok](#tab/ngrok)

+1. From ngrok, copy the HTTPS URL.

+ :::image type="content" source="../../assets/images/include-files/ngrok-url.png" alt-text="Screenshot shows the ngrok HTTPS URL.":::

+

+ > [!NOTE]

+ > The HTTPS URL in your ngrok is your fully qualified domain name.

+ > The `WebAppDomain` is a fully qualified domain name that doesn't include `https://` in it.

+1. Go to the Azure bot you've created in Azure portal. In the left pane, under **Settings**, select **Configuration**.

+1. Update the **Messaging endpoint** in the format `https://your-ngrok-domain/api/messages`.

+ :::image type="content" source="../../assets/images/include-files/ngrok-messaging-endpoint.png" alt-text="Screenshot shows the messaging endpoint adding api.":::

+1. Select **Apply**.

+ You have successfully set up a bot in Azure Bot service.

+

+Use ngrok or Command Prompt to create a tunnel to your locally running web server's publicly available HTTPS endpoints. Run the following command in ngrok:

+```bash

+ngrok http --host-header=localhost 3978

+```

+> [!TIP]

+> If you encounter **ERR_NGROK_4018**, follow the steps provided in the Command Prompt to sign up and authenticate ngrok. Then run the `ngrok http --host-header=localhost 3978` command.

+The window shows the HTTPS URL.

+ :::image type="content" source="../../assets/images/include-files/ngrok-url.png" alt-text="Screenshot shows the ngrok HTTPS URL.":::

+Specifies information about your company. For apps submitted to the Teams store, these values must match the information in your store listing. For more information, see the [Teams store publishing guidelines](~/concepts/deploy-and-publish/appsource/publish.md). Developer name helps improve your app discoverability in the Teams store.

+The name of your app experience, displayed to users in the Teams experience. For apps submitted to AppSource, these values must match the information in your AppSource entry. The values of `short` and `full` must be different. App name helps improve your app discoverability in the Teams store.

+Describes your app to users. For apps submitted to AppSource, these values must match the information in your AppSource entry. App description helps improve your app discoverability in the Teams store.

+The Classic Teams client is represented using the `teams` field and the new Teams client is represented using the `teamsModern` field.

+* ***August 29, 2023***: [Use Teams store with intelligent search experience to display apps that are closest match to the user's specified characters.](concepts/deploy-and-publish/appsource/publish.md#teams-store-search-experience)