Merge pull request #15468 from MicrosoftDocs/main

Publish main to live, Monday 5 PM IST, 08/26

Teams/manage-power-platform-apps.md

@@ -8,7 +8,7 @@ ms.tgt.pltfrm: cloud
 ms.service: msteams
 ms.subservice: teams-apps
 audience: Admin
-ms.date: 06/27/2023
+ms.date: 08/26/2024
 ms.collection: 
 - M365-collaboration
 appliesto: 
@@ -22,7 +22,7 @@ description: Learn how to manage access to custom apps built using Microsoft Pow
 
 # Manage Microsoft Power Platform apps in the Teams admin center
 
-This article gives you an overview of how to manage custom apps created using the [Microsoft Power Platform](https://powerplatform.microsoft.com/) apps in the Microsoft Teams admin center. Custom apps are created by developers within your organization for internal users.
+This article gives you an overview of how to manage custom apps created using the [Microsoft Power Platform](https://powerplatform.microsoft.com/) apps in the Microsoft Teams admin center. Custom apps are Teams apps that you use within your organization and are available to your org users only. Custom apps are not available on Teams app store.
 
 > [!NOTE]
 > This article doesn't apply to the `Power Apps` app or `Power Virtual Agents` app that are installed from the app store or pinned to Teams through an app setup policy. You can manage the Store apps using [app permission policies](teams-app-permission-policies.md) and [app setup policies](teams-app-setup-policies.md).
@@ -39,22 +39,22 @@ Users see an app in **Built with Power Platform** if the app meets one of the fo
 
 |Power Apps |Power Virtual Agents |
 |---------|---------|
-|<ul><li>The user created the app.</li><li>The app was shared directly with the user.</li><li>The user recently used the app. </li></ul>| <ul><li>The user created the bot.</li><li>The bot is owned by a team the user is a member of. </li></ul> |
+|<ul><li>The user created the app.</li><li>The app was shared directly with the user.</li><li>The user recently used the app. </li></ul>| <ul><li>The user created the bot.</li><li>The team, that a user is a member of, owns a bot. </li></ul> |
 
 Users install Microsoft Power Platform apps in the same way they install any other Teams app. Keep in mind that users can only install apps to the context to which they have permissions. For example, a team that a user owns, a chat that the user is a part of, or their personal scope.
 
 ## Manage access to Microsoft Power Platform apps in the Teams admin center
 
 As an admin, you can control whether Microsoft Power Platform apps are listed in **Built with Power Platform** on the Apps page in Teams. You can collectively block or allow all apps created in Power Apps or all apps created in Power Virtual Agents at the org level on the [Manage apps](manage-apps.md) page or for specific users using [app permission policies](teams-app-permission-policies.md).
 
-The **Shared Power Apps** and **Shared Power Virtual Agent Apps** apps in your organization's app store represent all apps created on that particular platform. If you block one or both these apps for entire org or for specific users, the users can't install them in Teams. The users cannot request admin approval to allow apps.
+The **Shared Power Apps** and **Shared Power Virtual Agent Apps** apps in your organization's app store represent all apps created on that particular platform. If you block one or both these apps for entire org or for specific users, the users can't install them in Teams. The users can't request admin approval to allow apps.
 
-Keep in mind that you can control access to all apps created in Power Apps and Power Virtual Agents but you can't allow or block individual apps. The app creator decides who can access the apps they create through the sharing feature from within Power Apps and Power Virtual Agents. If a maker shared an app they created in Power Virtual Agents with a user and you blocked **Shared Power Virtual Agents Apps** for that user, the user won't be able to see or install any apps from that platform in Teams.
+Keep in mind that you can control access to all apps created in Power Apps and Power Virtual Agents but you can't allow or block individual apps. The app creator decides who can access the apps they create through the sharing feature from within Power Apps and Power Virtual Agents. If a maker shared an app they created in Power Virtual Agents with a user and you blocked **Shared Power Virtual Agents Apps** for that user, the user can't view or install any apps from that platform in Teams.
 
 If a user is allowed to access apps from Power Apps or Power Virtual Agents, and you then block the user from accessing apps from one or both these platforms, the user can still access and use Microsoft Power Platforms apps that they installed before you blocked the app or apps. However, the user can no longer install any apps from those platforms in **Built with Power Platform**.
 
 > [!NOTE]
-> The **Upload custom apps for personal use** org-wide app setting on the [Manage apps](manage-apps.md) page applies to everyone in your organization and governs whether they can upload custom apps or not. Org-wide app settings govern the behavior for all users but don't override any app setup policies assigned to users. If this setting is turned off, users in your organization can't upload any custom apps, including Microsoft Power Platform apps. To learn more, see [Manage org-wide app settings](manage-apps.md#manage-org-wide-app-settings).
+> The setting named **Let users interact with custom apps in preview**, in the Org-wide app setting on the [Manage apps](manage-apps.md) page, applies to everyone in your organization and governs whether they can use custom apps or not. Org-wide app settings govern the behavior for all users but don't override any app setup policies assigned to users. If this setting is turned off, users in your organization can't upload any custom apps, including Microsoft Power Platform apps. To learn more, see [Manage org-wide app settings](manage-apps.md#manage-org-wide-app-settings).
 
 ### Allow or block Microsoft Power Platform apps for your organization
 

Teams/teams-custom-app-policies-and-settings.md

@@ -8,7 +8,7 @@ ms.tgt.pltfrm: cloud
 ms.subservice: teams-apps
 ms.service: msteams
 audience: Admin
-ms.date: 08/01/2024
+ms.date: 08/26/2024
 ms.reviewer: mhayrapetyan
 ms.collection: 
  - M365-collaboration
@@ -27,16 +27,16 @@ ms.custom:
  - seo-marvel-mar2020
 ---
 
-# Manage custom apps in Teams admin center
+# Manage custom apps in Microsoft Teams admin center
 
 Your organization can commission creation of Teams apps that work only within your organization. Such apps are available within your organizations or tenant but aren't available on the Teams store. Users can discover and use such apps from Teams client and admins can govern such apps from the admin centers, but such apps aren't available on [AppSource](https://appsource.microsoft.com/). Such apps are called custom apps.
 
 As a Teams Administrator or a Global Administrator, you use various settings to control the following scenarios:
 
-* Who can upload custom apps to Microsoft Teams for their personal use
-* Which custom apps you allow for all org users that developers submit for your approval
-* Whether users can use custom apps or not
-* Allow or disallow upload of custom apps to a particular team
+* Let users add custom apps to their Teams client for their personal use.
+* Let users use specific custom apps from amongst all the custom apps available in your org.
+* Disallow all users to not use custom apps.
+* Allow or disallow team users to add custom apps to a particular team.
 
 :::image type="content" source="media/upload-custom-apps.png" alt-text="Overview of a custom app from development to deployment.":::
 
@@ -51,7 +51,7 @@ Your organization can commission the creation of custom apps for your org-specif
 The following are the methods to make custom apps available in your organization's store, in a team, or for a few users.
 
 | Method to upload custom app | Who uploads and how | Scope of app availability | Who controls the upload option | Potential use case |
-|-----------------------------|-------------|---------------------------|---------------------------|---------------------------|
+|-----------------------------|---------------------|---------------------------|--------------------------------|--------------------|
 | **Custom app submission by user** | [Any user using Teams client](/microsoftteams/platform/concepts/deploy-and-publish/apps-upload) | Available to entire org after an admin approves | Submit option is available to all users and can't be turned off. Admins can disapprove any submission. | User wants to make a custom app available to their entire org, after admin approval. |
 | **Custom app submission by user using API** | [Any user using Teams App Submission Graph API](submit-approve-custom-apps.md) | Available to entire org after an admin approves | Submit option is available to all users and can't be turned off. Admins can disapprove any submission. | User wants to make a custom app available to their entire org, after admin approval. |
 | **Custom app upload by admin** | [Global or Teams administrators using Teams admin center](#upload-a-custom-app-using-teams-admin-center) or using Teams client | Available to entire org; no approval required | Available to all admins; can't disable. | Admins upload custom apps for entire org. Custom app is received as zip package. |
@@ -64,13 +64,13 @@ As Teams administrator, you have the following controls on upload and use of cus
 | Allow or disallow specific users from uploading custom apps | Use [app setup policy](#allow-users-to-upload-custom-apps) | You apply app setup policy to specific users to allow or disallow them from uploading custom app in personal context or in a team. Users can still submit custom apps for your approval. |
 | Allow or disallow all users from uploading custom apps | Use [custom app setting in Org-wide app settings](manage-apps.md#manage-org-wide-app-settings) | Users can't upload custom apps even in their personal context. Users can still submit custom apps for your approval. |
 | Restrict app access for a few users | Use [app permission policy](teams-app-permission-policies.md) | You granularly control which users have access to what particular custom app (also applies to third-party apps). |
-| Delete a custom app | [Delete an app](#delete-custom-apps-from-your-organizations-catalog) | The deleted app isn't available in your org. It's removed for existing users too. |
+| Delete a custom app | [Delete an app](#delete-custom-apps-from-your-organizations-catalog) | The deleted app isn't available in your org. Existing app users also can't use it anymore. |
 
 If you disallow custom app upload, app developers can [create a separate test tenant to test apps](/microsoftteams/platform/concepts/build-and-test/prepare-your-o365-tenant). Once custom app development is complete, app creators request admins to distribute their custom app. For details, see [how to publish a custom app](/microsoftteams/upload-custom-apps). As an admin, you allow or block the use of a custom app for all users or for specific users.
 
 ## Upload a custom app using Teams admin center
 
-To make the app available to users in your organization's app store, follow these steps:
+To make a custom app available to users in your organization's app store, follow these steps:
 
 1. Access Teams admin center and go to **Teams apps** > **[Manage apps](https://admin.teams.microsoft.com/policies/manage-apps)**.
 
@@ -79,31 +79,33 @@ To make the app available to users in your organization's app store, follow thes
  * Select **Upload new app**, select **Upload**, and select the app package that the developer provided to you.
  * Select **Actions** > **Upload new app** and upload the app.
 
+ :::image type="content" source="media/custom-app-upload-option.png" alt-text="Screenshot showing the option for admins to upload a custom app from Teams admin center.":::
+
 The uploaded app is available to the org users after a few hours.
 
 ## Update a custom app using Teams admin center
 
-To update an existing custom app, follow these steps:
+Just like third-party apps in the Teams store get updates, developers update custom apps. You can update a custom app in your org catalog to a newer version by uploading a new version of the app. To update, select **Upload file** from the app details page.
 
-1. Access Teams admin center and go to **Teams apps** > **[Manage apps](https://admin.teams.microsoft.com/policies/manage-apps)**.
+:::image type="content" source="media/update-custom-app-version.png" alt-text="Screenshot showing the option to upload a new version of a custom app in admin center.":::
 
-1. Select the name of the existing custom app to open its app details page.
+When a new version of an app is published, the existing policies that applied to the previous version of the app continue to be in effect for the updated version.
 
-1. On the banner of the app, select **Upload file**, and provide the updated app package.
+Alternatively, an org user can submit an updated custom app for your approval. When you approve the app, the newer version is available in the org catalog.
 
 ## Allow users to upload custom apps
 
 Microsoft Teams provides granular control over who can add custom apps to a team. To control if custom apps can be added to a team or not, admins and team owners use the following settings. These settings don't affect the ability to block third-party apps.
 
-* [**Org-wide app settings**](manage-apps.md#manage-org-wide-app-settings) for custom app: The setting named **Upload custom apps for personal use** lets you either allow or disallow all your users to upload custom apps. Users can upload custom apps only for their personal use or in their teams.
+* [**Org-wide app settings**](manage-apps.md#manage-org-wide-app-settings) for entire organization: The setting named **Let users interact with custom apps in preview** lets you either allow or disallow all your users across the organization to upload custom apps. Users can upload custom apps only for their personal use or within their teams.
 
  :::image type="content" source="media/teams-custom-app-policy-and-settings-org-wide.png" alt-text="Screenshot showing the org-wide custom app settings.":::
 
-* [**App setup policy**](#app-setup-policy-settings-for-custom-apps): The setting named **Upload custom apps** in the app setup policy determines which users in an organization are allowed to upload custom apps.
+* [**App setup policy**](#app-setup-policy-settings-for-custom-apps) for specific users: The setting named **Upload custom apps** in the app setup policy lets assigned users upload custom apps. You can use this setting to allow specific users in your org to upload custom apps.
 
  :::image type="content" source="media/upload-custom-app-setup-policy.png" alt-text="Screenshot showing the custom app option available in an app setup policy.":::
 
-* [**Allow members to upload custom apps**](#team-setting-for-custom-app): This setting in each team determines if users of a team can upload custom apps or not. Team owners and admins can modify this setting.
+* [**Allow members to upload custom apps**](#team-setting-for-custom-app) at team level: This setting in each team determines if users of a team can upload custom apps or not. Team owners and Teams admins can modify this setting. Using this setting, team owners can prevent custom app upload to a specific team even if the users are allowed to upload custom apps.
 
 If an admin uploads a custom app, it's available in the organization's catalog in the store without requiring any approval. You can allow some org users using app permission policy to use such an app. The impact of team setting and app setup policy on user's ability to upload custom apps is summarized in the following table.
 
@@ -114,16 +116,6 @@ If an admin uploads a custom app, it's available in the organization's catalog i
 | On | Off | No user | Any user |
 | On | On | Anybody | Any user |
 
-## Update a custom app to a new version
-
-Just like third-party apps in the Teams store get updates, developers update custom apps. You can update a custom app in your org catalog to a newer version by uploading a new version of the app. To update, select **Upload file** from the app details page.
-
-:::image type="content" source="media/update-custom-app-version.png" alt-text="Screenshot showing the option to upload a new version of a custom app in admin center.":::
-
-When a new version of an app is published, the existing policies that applied to the previous version of the app continue to be in effect for the updated version.
-
-Alternatively, a user can submit an updated custom app for your approval. When you approve the app, the app updates to a newer version in the organization catalog.
-
 ### App setup policy settings for custom apps
 
 You can use a setting in the app setup policy to allow or disallow users from uploading custom apps. This setting is useful when you want to allow only specific users in the organization to upload custom apps. To [allow all users to upload custom apps](#allow-users-to-upload-custom-apps), use the custom app setting in Org-wide app settings.
@@ -153,7 +145,7 @@ To configure the custom apps related setting in a team, follow these steps as a
 
 1. Select **Settings** and expand **Member permissions**.
 
-1. Select or clear the **Allow members to upload custom apps** check box.
+1. Select or clear the **Allow members to upload custom apps** option.
 
  :::image type="content" source="media/teams-custom-app-policy-and-settings-team-trim.png" alt-text="Screenshot showing the team custom app setting." lightbox="media/teams-custom-app-policy-and-settings-team.png":::
 
@@ -182,19 +174,19 @@ This table summarizes the custom app settings and how the settings work together
 
 To allow only a few selected users or groups to upload and use custom apps, follow these steps:
 
-1. Turn on the **Upload custom apps for personal use** option in Org-wide app setting in admin center.
+1. Turn on the **Let users interact with custom apps in preview** option in Org-wide app setting in admin center.
 1. Turn off the **Upload custom apps** setting in the global [app setup policy](#app-setup-policy-settings-for-custom-apps).
 1. Create a new app setup policy that allows uploading custom apps and [assign the policy to the selected users or groups](policy-assignment-overview.md#ways-to-assign-policies).
 
 Consider a scenario where you want to allow only team owners to upload custom apps to specific teams. To accomplish this result, implement the following settings:
 
-* Turn on the **Upload custom apps for personal use** option in the Org-wide app setting in admin center.
+* Turn on the **Let users interact with custom apps in preview** option in the Org-wide app setting in admin center.
 * Turn off the **Allow members to upload custom apps** for every team to which you want to restrict access.
 * Create and assign a custom policy in app setup policy in admin center with the **Upload custom apps** setting turned on and assign the policy to the team owners.
 
 ## Custom apps in 21Vianet and air-gapped cloud environments
 
-You can [upload custom apps](#upload-a-custom-app-using-teams-admin-center) in Microsoft 365 operated by 21Vianet and air-gapped cloud environments by using the Teams apps > Manage apps page. Also, you can [update your existing custom app](#update-a-custom-app-to-a-new-version) from the app details page.
+You can [upload custom apps](#upload-a-custom-app-using-teams-admin-center) in Microsoft 365 operated by 21Vianet and air-gapped cloud environments by using the Teams apps > Manage apps page. Also, you can [update your existing custom app](#update-a-custom-app-using-teams-admin-center) from the app details page.
 
 ## Related article