-| Property name | Purpose |

- "externalResourceUrl": "https://teams.microsoft.com/l/bubble/APP_ID?url=<url>&height=<height>&width=<width>&title=<title>&completionBotId=BOT_APP_ID"

-| Property name | Purpose |

-| Property name | Purpose |

-| Property name | Purpose |

->

-> * Add app option for Teams meeting extension tab app is not supported in Teams web client.

-* [Azure bot service](#azure-bot-service)

-## Azure bot service

-The Azure bot service, along with the Bot Framework, provides tools to build, test, deploy, and manage intelligent bots, all in one place. You can also create your bot in Azure bot service.

-> [!IMPORTANT]

-> Bot applications within Microsoft Teams are available in GCC-High through [Azure bot Service](/azure/bot-service/channel-connect-teams).

-> [!NOTE]

->

-> * Bots in GCCH only support up to manifest version v1.10.

-> * Image URL's in Adaptive Cards are not supported in GCCH environment. You can replace an image URL with Base64 encoded DataUri.

-> * Bot channel registration in Azure Government will provision web app bot, app service (app service plan), and application insights also but it doesn't support to provision the azure bot service only (no app service).

-> <details>

-> <summary><b>If you want to do bot registration only</b></summary>

->

-> * Go to the resource group and manually delete the unused resources. Such as the app service, app service plan (if you created during bot registration), and the application insights (if you choose to enable it during bot registration).

-> * You can also use az-cli to do bot registration:

->

-> 1. Sign into azure and set the subscription <br>

-> &nbsp; az cloud set ΓÇôname "AzureUSGovernment" <br>

-> &nbsp; az account set ΓÇôname "`subscriptionname/id`".<br>

-> 1. Create app registration

-> &nbsp; az ad app create --display-name "`name`" <br>

-> &nbsp; --password "`password`" --available-to-other-tenants.<br>

-> Your app id would be created here.<br>

-> 1. Create bot resource <br>

-> &nbsp; az bot create ΓÇôresource-group "`resource-group`"<br>

-> &nbsp; --appid "`appid`"<br>

-> &nbsp; --name "`botid`"<br>

-> &nbsp; --kind "registration".<br>

->

-> </details>

-For GCCH environment, you need to register a bot using [Azure Government portal](https://portal.azure.us).

-<br>

-<br>

-The following changes are needed within the bot for GCC-High environment:

-<br>

-<br>

-<details>

-<summary><b>Configuration changes</b></summary>

-As the bot registration occurs in Azure Government portal, ensure to update the bot configurations to connect to Azure govermnet instances. Following are the configuration details:

-| Configuration Name | Value |

-|-|-|

-| ChannelService | `https://botframework.azure.us` |

-| OAuthUrl | `https://tokengcch.botframework.azure.us` |

-| ToChannelFromBotLoginUrl | `https://login.microsoftonline.us/MicrosoftServices.onmicrosoft.us` |

-| ToChannelFromBotOAuthScope | `https://api.botframework.us` |

-| ToBotFromChannelTokenIssuer | `https://api.botframework.us` |

-| BotOpenIdMetadata | `https://login.botframework.azure.us/v1/.well-known/openidconfiguration` |

-</details>

-<br>

-<details>

-<summary><b>Update to appsettings.json & startup.cs</b></summary>

-1. **Update appsettings.json:**

- * Set `ConnectionName` to the name of the OAuth connection setting you added to your bot.

- * Set `MicrosoftAppId` and `MicrosoftAppPassword` to your bot's app ID and app secret.

- Depending on the characters in your bot secret, you may need to XML escape the password. For example, any ampersands (&) need to be encoded as `&amp;`.

- ```json

- {

- "MicrosoftAppType": "",

- "MicrosoftAppId": "",

- "MicrosoftAppPassword": "",

- "MicrosoftAppTenantId": "",

- "ConnectionName": ""

- }

- ```

-2. **Update Startup.cs:**

- To use OAuth in *non-public Azure clouds*, like the government cloud, or in bots with data-residency, you must add the following code in the **Startup.cs** file.

- ```csharp

- string uri = "<uri-to-use>";

- MicrosoftAppCredentials.TrustServiceUrl(uri);

- OAuthClientConfig.OAuthEndpoint = uri;

- ```

- Where \<uri-to-use\> is one of the following URIs:

- |**URI**|**Description**|

- |||

- |`https://europe.api.botframework.com`|For public-cloud bots with data residency in Europe.|

- |`https://unitedstates.api.botframework.com`|For public-cloud bots with data residency in the United States.|

- |`https://apiGCCH.botframework.azure.us`|For United States government-cloud bots without data residency.|

- |`https://api.botframework.com`|For public-cloud bots without data residency. This is the default URI and does not require a change to **Startup.cs**.|

-3. The redirect URL for app registration from Azure should be updated to `https://tokengcch.botframework.azure.us/.auth/web/redirect`.

-</details>

-> Currently, bots are available in Government Community Cloud (GCC) and GCC-High but not in Department of Defense (DOD).

-> Bot applications within Microsoft Teams are available in GCC-High through [Azure bot Service](/azure/bot-service/channel-connect-teams).

-You can enable this feature in the [Developer Portal for Teams](https://dev.teams.microsoft.com/home). This configures `configurableProperties`, which isn't available in versions before 1.10 of the Teams app manifest.

-* [Customize apps in the Teams admin center](/MicrosoftTeams/customize-apps)

-description: Learn how to update search-based Teams message extension to run in Outlook by updating app manifest, adding an outlook channel, and sideloading updated app.

-description: Learn how to extend a Teams personal tab app across Microsoft 365 by updating personal tab to run in both outlook and office.

-description: Learn how to build and update your Teams app experiences to other high-usage areas of Microsoft 365.

-With the latest releases of [Microsoft Teams JavaScript client SDK](../tabs/how-to/using-teams-client-sdk.md) (version 2.0.0), [Teams App manifest](../resources/schem), you can build and update Teams apps to run in other high-usage Microsoft 365 products and publish them to the Microsoft commercial marketplace ([Microsoft AppSource](https://appsource.microsoft.com/)).

-For guidance about the Teams app manifest and SDK versioning guidance, as well as further details about current Teams platform capability support across Microsoft 365, see the [Teams JavaScript client SDK overview](../tabs/how-to/using-teams-client-sdk.md).

-Join the growing number of production Teams apps in the [Microsoft AppSource](https://appsource.microsoft.com/) store with expanded support for Outlook and Office preview (Targeted Release) audiences. The app [submission process for Teams apps enabled for Outlook and Office](../concepts/deploy-and-publish/appsource/publish.md) is the same as for traditional Teams apps; the only difference is you'll use Teams app manifest [version 1.13](../tabs/how-to/using-teams-client-sdk.md) in your app package, which introduces support for Teams apps that run across Microsoft 365.

-description: Learn about the prerequisites required to run preview builds for extending your Teams apps across Microsoft 365.

-description: Learn how to make your Microsoft 365-enabled Teams apps discoverable to users in Teams, Outlook, and Office.

-Moodle integration in Microsoft Teams is powered by the open source [Microsoft 365 Moodle plugins set](https://github.com/Microsoft/o365-moodle).

- > In addition, the [Microsoft 365 Teams Theme](https://moodle.org/plugins/theme_boost_o365teams) plugins is highly recommended.

-1. Sign in to your Moodle server as an administrator and select **Site administration** from the [Settings block](https://docs.moodle.org/22/en/Settings_block) located in the left navigation panel.

-1. Select the **Plugins** tab, and then select **Install plugins**.

-1. From the **Install plugins from ZIP file** section, select **Choose a file**.

-1. Select **Upload a file** option from the left navigation panel, browse for the file that you downloaded, and select **Upload this file**.

-1. Select **Site administration** from the left navigation panel to return to your admin dashboard. Scroll down to the **Local plugins** and select the **Microsoft 365 Integration** link.

-> * The PowerShell script is not updated with the latest configuration items, therefore, you must complete the configuration manually following the steps outlined in the Moodle [3.8.0.4 and 3.9.1](https://docs.moodle.org/39/en/Office365#3.8.0.4_and_3.9.1_release) and [3.8.0.5 and 3.9.2](https://docs.moodle.org/39/en/Office365#3.8.0.5_and_3.9.2_release) release pages.

->

-> * For more information on registering your Moodle instance manually, see [Register your Moodle instance as an application](https://docs.moodle.org/34/en/Office365#Register_your_Moodle_instance_as_an_Application).

-1. Synchronize users between your Moodle server and Azure AD. Depending on your environment, you can select different options during this stage. To get started:

- 1. The **User Field Mapping** section allows you to customize the Azure AD to Moodle User Profile field mapping.

- 1. In the **Teams Sync** section, you can select to automatically create Groups, such as teams for some, or all, of your existing Moodle courses.

-13. To validate [cron](https://docs.moodle.org/310/en/Cron) jobs and run them manually for the first run, select the **Scheduled tasks management page** link in the **Sync users with Azure AD** section. This takes you to the **Scheduled Tasks** page.

-1. On the **Teams Settings** page, configure the required settings to enable the Teams app integration.

- 1. To enable **OpenID Connect**, select the **Manage Authentication** link, and select the eye icon on the **OpenId Connect** line if it is unavailable.

- 1. To enable frame embedding, select the **HTTP Security** link, and then select the checkbox next to **Allow frame embedding**.

- 1. To enable web services, which enable the Moodle API features, select the **Advanced Features** link, and then ensure the checkbox next to **Enable web services** is selected.

- 1. To enable the external services for Microsoft 365, select the **External services** link, and then:

- Γ£ö Select **Edit** on the **Moodle Microsoft 365 Webservices** row.

- Γ£ö Select the checkbox next to **Enabled**, then select **Save Changes**

- 1. Edit your authenticated user permissions to allow them to create web service tokens.

- Γ£ö Select the **Editing role Authenticated user** link.

- Γ£ö Scroll down and find the **Create a web service token** capability and select the **Allow** checkbox.

-After your bot deployed to Azure and configured to talk to your Moodle server, you must deploy your Microsoft Teams app. To do this you must load the app manifest file that you downloaded from the Microsoft 365 Moodle Plugins Team Settings page in the previous step.

-1. Select the **App** icon on the lower-left area of the navigation bar.

-1. Select the **Upload a custom app** link from the list of options.

-1. Open Microsoft Teams.

-1. Select the Apps icon from the lower-left pane.

-1. Locate the uploaded **Moodle app** > select the **options** icon > select **copy link**.

-1. In a text editor, paste the copied content. It must contain a URL such as `https://teams.microsoft.com/l/app/00112233-4455-6677-8899-aabbccddeeff`. Copy the last part of the URL, such as `00112233-4455-6677-8899-aabbccddeeff`, which is the ID of the Microsoft Teams app.

-1. Paste the ID of the Microsoft Teams app into the Moodle app ID field, and save changes.

-* [Moodle documentation](https://docs.moodle.org/34/en/Installing_plugins).

-An optional list of commands that your bot can recommend to users. The object is an array (maximum of two elements) with all elements of type `object`; you must define a separate command list for each scope that your bot supports. For more information,see [Bot menus](~/bots/how-to/create-a-bot-commands-menu.md).

-> `isFullScreen` works only for apps published to your organization.