| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Bots Filesv4 | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/bots-filesv4.md | private static Attachment GetInlineAttachment() }ΓÇïΓÇïΓÇïΓÇïΓÇï ``` -### Basic example in C # +### Basic example in C# # The following code shows an example of how to handle file uploads and send file consent requests in the bot's dialog: |
| platform | Share To Teams From Personal App Or Tab | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/share-to-teams-from-personal-app-or-tab.md | After you enable share to teams button on personal app or tab, you can share the :::image type="content" source="../../assets/images/share-to-teams/add-recepient.PNG" alt-text="add-recipient"::: - > [!NOTE] - > You can add a note in **say something about this**. - 3. Select **Share**. :::image type="content" source="../../assets/images/share-to-teams/add-notes.PNG" alt-text="add-note"::: |
| platform | Enable App Customization | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/design/enable-app-customization.md | Title: Customize your Teams app + Title: Enable app customization and block apps till admin allows description: In this module, understand how Teams admins can customize your Teams app for their org and hide Teams app until admin approves. ms.localizationpriority: medium-# Customize your Teams app +# Enable app customization and block apps till admin allows -## Enable your Microsoft Teams app to be customized +Microsoft Teams lets admins customize Teams app to enhance store experience and adhere to their organization's branding. An app developer can allow their app to be customized by a Teams admin. For more information, see +[Customize apps in the Teams admin center](/MicrosoftTeams/customize-apps). ++## Enable customization for your Microsoft Teams app You can allow customers to customize some aspects of your Microsoft Teams app in the Teams admin center. This feature is supported only for apps published to the Teams store. Sideloaded apps and apps published for an org can't be customized. Some possible examples of this feature include: * Changing the app's accent color to match an org's brand.-* Updating the app name from *Contoso* to *Contoso Agent*, which is the name users in the org will see. +* Updating the app name from *Contoso* to *Contoso Agent*, which is the name users in the org will see. (Note: Users adding a connector to a chat or a channel will still see the original app name, *Contoso*.) You can enable this feature by defining the app properties that your customers can customize in the [`configurableProperties` section in the Teams app manifest](/microsoftteams/platform/resources/schema/manifest-schema#configurableproperties), starting with version 1.11. That can be done in the [Developer Portal for Teams](https://dev.teams.microsoft.com/home) if you've chosen to use the Developer Portal to edit the manifest of your app. -### Test your app --You can't test this feature during development. App customization isn't supported when sideloading or publishing to an org's app catalog. +> [!IMPORTANT] +> You can't test this feature during development. App customization isn't supported when sideloading or publishing to an org's app catalog. ### User considerations Provide guidelines for customers (specifically Teams admins) who want to customize your app. For more information, see [customize apps in Teams](/MicrosoftTeams/customize-apps). -## Hide Teams app until admin approves +## Block apps by default for users until an admin approves To enhance Teams app experience, you can hide an app from users by default until admin allows to unhide the app. For example, Contoso Electronics has created a help desk app for Teams. To enable appropriate functioning of the app, Contoso ElectronicsΓÇÖ wants the customers to first set up specific properties of the app. The app is hidden by default and is available to users only after the admin allows it. -> [!NOTE] -> Teams store has evolved: -> -> Previously, the LOB apps were updated by selecting the ellipses on the tile. With the updated Teams store experience, you can now update the LOB apps by logging in to the [Teams Admin Centre](https://admin.teams.microsoft.com). - To hide the app, in the app manifest file, set the `defaultBlockUntilAdminAction` property to `true`. When the property is set to `true`, in Teams admin center > **Manage apps**, **Blocked by publisher** appears in app's **Status**: The admin gets a request to take action before a user can access the app. Under **Manage apps**, the admins can select **Allow** to allow the app with **Blocked by publisher** status: - If by default, you don't want the app to be hidden, you can update the `defaultBlockUntilAdminAction` property to `false`. When the new version of the app is approved, by default the app will be allowed as long as the admin hasn't taken any explicit action. > [!NOTE]-> `defaultBlockUntilAdminAction` is not supported for LOB apps. If you upload an LOB app with this property then the app will not be blocked. +> For LOB apps, `defaultBlockUntilAdminAction` is not supported. The app is not blocked if you upload a LOB app with this property. ## See also |
| platform | Manifest Schema | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md | Enables your app in non-standard channels. If your app supports a team scope and **Optional** - Boolean -When `defaultBlockUntilAdminAction` property is set to **true**, the app is hidden from users by default until admin allows it. If set to **true**, the app is hidden for all tenants and end users. The tenant admins can see the app in the Teams admin center and take action to allow or block the app. The default value is **false**. For more information on default app block, see [Hide Teams app until admin approves](~/concepts/design/enable-app-customization.md#hide-teams-app-until-admin-approves). +When `defaultBlockUntilAdminAction` property is set to **true**, the app is hidden from users by default until admin allows it. If set to **true**, the app is hidden for all tenants and end users. The tenant admins can see the app in the Teams admin center and take action to allow or block the app. The default value is **false**. For more information on default app block, see [Block apps by default for users until an admin approves](../../concepts/design/enable-app-customization.md#block-apps-by-default-for-users-until-an-admin-approves) ## publisherDocsUrl |
| platform | Whats New | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/whats-new.md | Explore updates from the previous GA releases listed here. |10/20/2021| Meeting Details API and real-time Teams meeting events | Build apps for Teams meetings > [Get meeting details API](apps-in-teams-meetings/API-references.md#get-meeting-details-api) | |10/18/2021| Tabs link unfurling and stage view | Build tabs > [Tabs link unfurling and stage view](tabs/tabs-link-unfurling.md) | |10/08/2021| New best practices for designing Adaptive Cards | Design your app > UI components > [Designing Adaptive Cards for your Teams app](task-modules-and-cards/cards/design-effective-cards.md) |-|10/05/2021| Hide Teams app until Admin allows to un-hide the app | Design your app > [Hide Teams app until admin approves](concepts/design/enable-app-customization.md#hide-teams-app-until-admin-approves) | +|10/05/2021| Hide Teams app until Admin allows to un-hide the app | Design your app > [Block apps by default for users until an admin approves](concepts/design/enable-app-customization.md#block-apps-by-default-for-users-until-an-admin-approves) | |10/05/2021| Plan your apps for Teams mobile | App fundamentals > [Plan responsive tabs for Teams mobile](concepts/design/plan-responsive-tabs-for-teams-mobile.md) | |10/04/2021| New Developer Portal for Teams introduced for managing your Teams apps | Tools and SDK > [Developer Portal for Teams](concepts/build-and-test/teams-developer-portal.md) | |09/21/2021|Teams supports Azure AD Object ID and UPN in user mention for bots and Incoming Webhooks | ΓÇó Build cards and task modules > Build cards > [Azure AD Object ID and UPN in user mention](task-modules-and-cards/what-are-cards.md#support-for-azure-ad-object-id-and-upn-in-user-mention) </br> ΓÇó Build cards and task modules > Build cards > [Cards- Overview](task-modules-and-cards/cards/cards-format.md#format-cards-with-markdown) | |