Category | Microsoft Docs article | Related commit history on GitHub | Change details |
---|---|---|---|
admin | Manage Copilot Agents Integrated Apps | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps.md | + + Title: "Manage Copilot agents in Integrated Apps" +f1.keywords: +- NOCSH +++ Last updated : 9/17/2024+audience: Admin +++ms.localizationpriority: medium ++- Tier2 +- scotvorg +- M365-subscription-management +- Adm_O365 +- Adm_TOC +- m365copilot +- magic-ai-copilot ++- AdminSurgePortfolio +- AdminTemplateSet +search.appverid: +- BCS160 +- MET150 +- MOE150 +description: "Learn how to manage Copilot agents in the Integrated apps page in the Microsoft 365 admin center." +++# Manage Copilot agents in Integrated Apps ++> [!IMPORTANT] +> +> - You must have Microsoft 365 Copilot license to use Copilot agents. +> - The capability is enabled by default in all Microsoft 365 Copilot licensed tenants. +> - Admins can disable this functionality for a user or a group. Also, admins control how individual agents are approved for use and which agents are enabled. ++Microsoft 365 Copilot is a new experience in Microsoft 365 that combines the power of large language models with your data and apps in Microsoft 365 to capture natural language commands to produce content and analyze data. It enables access to and use of third-party apps, such as Jira, [Dynamics 365](/microsoft-365-copilot/extensibility/overview-business-applications), or Bing Web Search. Admins can manage Copilot agents in the same way as they manage any other app in the Integrated apps section of the Microsoft 365 admin center. Admins can enable, disable, assign, block, or remove Copilot agents for their organization, and manage Copilot capabilities and data privacy. ++## Overview ++Agents enhance the functionality of Copilot by adding search capabilities, custom actions, connectors, and APIs. Agents are custom versions of Microsoft 365 Copilot that combine instructions, knowledge, and skills to perform specific tasks or scenarios. ++Microsoft Copilot Studio is a low-code development platform that offers a graphical environment to build Copilot agents tailored to the internal needs of an organization. Copilot Studio enables developers and makers to create and test their applications in a user-friendly interface. ++However, before these agents can become available to users, the agents must undergo a streamlined process of submission and approval. To learn more, see [Publish Copilot agents](#publish-copilot-agents). ++When Copilot extensibility is enabled, users can see third party agents in Copilot that allows them to access the Copilot. The hub Copilot experience shows the list of agents that are available and deployed for the user. Users can toggle it on or off to restrict access of Copilot to any specific agents during the interaction. Users can also add or remove agents in their Copilot experience by right-clicking on the agents and selecting the appropriate option. Users can only access the agents that are allowed by the admin and that they have installed or been assigned to. ++## Manage Copilot agents in the Microsoft 365 admin center ++Admins can manage Copilot agents as apps in the Integrated apps section of the Microsoft 365 admin center, where they can see the list of available, deployed, or blocked apps for their organization. They are able to: ++- Enable or disable Copilot extensibility for the complete organization through Microsoft 365 admin center settings. +- Make a Copilot agent available to specific users or groups. +- Block or unblock Copilot agents for the complete organization. +- Deploy or remove Copilot agents for the complete organization or specific users or groups. ++Admins can view Copilot agents from the list of available, deployed, or blocked apps on the Integrated apps page by using the filter option of **Host products > Copilot**. ++You can also check if a specific app has Copilot support by selecting it from apps list and checking if the app overview mentions **Copilot** as a host product. ++## Enable or disable Copilot extensibility ++Admins can enable or disable Copilot extensibility for their org by using a setting in the tenant default options in the Integrated Apps section of the Microsoft 365 admin center. This setting lets you control who can access Copilot agents in their organization. The setting has three options: ++- **All Users**: This is the default option and it means that all users in the organization can access Copilot agents, subject to the existing app policies and user assignments. +- **No Users**: This option means that no users in the organization can access Copilot agents, and the third party agents are disabled in the Copilot agents flyout. This option also hides Copilot agents from the list of Available and Deployed apps on the Integrated Apps page. +- **Specific Users**: This option lets you select specific users or groups in your organization to have access to Copilot agents. So while all or specific users in your organization may have permissions to install and use apps from the Available apps and Deployed apps lists, only the users or groups you select in this setting can use Copilot agents. ++## Deploy or remove Copilot agents ++Admins can deploy or remove Copilot agents across the whole organization or for specific users or groups by using the same gestures and controls that work for any other app in the Microsoft 365 admin center. Admins can select a Copilot agent from the list of Available or Deployed apps and select **Deploy** or **Remove**. Admins can also choose to deploy or remove the agents for everyone or specific users or groups. Deploying or removing an agent affects its availability and functionality in Copilot and in the other host products, such as Outlook, Teams, or Microsoft 365. ++## Manage how users can install Copilot agents ++Admins can assign or unassign Copilot agents to specific users or groups by using the same gestures and controls that work for any other app in the Microsoft 365 admin center. Admins can select an app that has a plugin for Copilot from the Available apps or Deployed apps list and select the **Assign** or **Unassign** option. Admins can also choose to assign or unassign the app to everyone or specific users or groups. Assigning or unassigning an agent affects its availability and functionality in Copilot and in the other host products, such as Outlook, Teams, or Microsoft 365. ++> [!IMPORTANT] +> Developers can [update the existing apps](/microsoft-365-copilot/extensibility/) to work with Microsoft 365 Copilot. If the updated app was pre-approved or pre-installed by an admin, then it'll update for the assigned users and starts working with Copilot. If a developer updates a previously blocked app to work with Microsoft 365 Copilot and then the admins make the app available to the users, then such an app also works with Copilot. ++## Block or unblock Copilot agents ++Admins can block or unblock Copilot agents for the complete organization or specific users or groups by using the same gestures and controls that work for any other app in the Microsoft 365 admin center. Admins can select an app that has Copilot agent from the list of Available or Deployed apps and select the block or unblock option. Admins can also choose to block or unblock an agent for everyone or specific users or groups. Blocking or unblocking an agent affects its availability and functionality in Copilot as well as other host products, such as Outlook, Teams, or Microsoft 365. ++## View and consent to permissions and data access ++For detailed information about how Microsoft 365 Copilot uses, protects, and shares organizational information to power extensibility, see [Data, Privacy, and Security for Microsoft 365 Copilot](/microsoft-365-copilot/microsoft-365-copilot-privacy). ++## Publish Copilot agents ++The publishing process in the Microsoft 365 admin center for Copilot agents submitted via Copilot Studio is designed to ensure governance and quality of the custom applications. It also reduces manual work by automating the submission of manifests, freeing developers and admins from tedious tasks. The simplified approval process reduces the time it takes for you to approve apps, making it easier for you to manage custom applications in the Microsoft 365 admin center. ++The publishing process involves the following steps: ++1. Developers create and test Copilot agents in Copilot Studio, which provides a user-friendly interface for inputting the parameters and data for the applications. +1. Developers submit their Copilot agents for approval from within Copilot Studio to the Microsoft 365 admin center. +1. You can discover the apps with Copilot agents that are submitted but not yet approved in admin center under the **Requested Apps** tab in the Integrated Apps section. The tab shows the name, host products, status, and Copilot readiness of the applications. The status of a new app is `Publish pending` and of an update to an existing app is `Update pending`. +1. You can select a pending application to see more details and metadata, such as the description, requester, request date, and the status. These details help you to make an informed decision on whether to publish or reject the application. +1. You can approve or disapprove any pending application by selecting **Publish** or **Reject**. ++ 1. If the application is approved, it becomes available to the org users based on the org default settings and Copilot default settings. The application also becomes part of the `Available apps` list in the admin center, where admins can manage user assignments and other settings as any other app. ++ 1. If the application is disapproved, it is removed from the `Pending approval` list in the admin center, and the status is shared with Copilot Studio. The developer can make changes and resubmit the application for approval. ++1. If the developer publishes an update to an existing application, the update is also submitted for approval and follows the same workflow as a new application. The update is shown in the ΓÇÿPending approvalΓÇÖ list with the status `Update pending`. Until the update is approved, the previous version of the application remains available to the users. |
admin | Manage Deployment Of Add Ins | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/manage-deployment-of-add-ins.md | Before you begin, see [Determine if Centralized Deployment of add-ins works for 1. In the admin center, go to the **Settings** \> **Integrated apps** \> **Add-ins** page. > [!NOTE]-> You can also deploy add-ins in the admin center through [Integrated Apps](test-and-deploy-microsoft-365-apps.md). Integrated Apps is the recommended place for admins to deploy add-ins, and is available to Global Administrator, Azure Application Administrator and Exchange Administrator. +> You can also deploy add-ins in the admin center through [Integrated Apps](test-and-deploy-microsoft-365-apps.md). Integrated Apps is the recommended place for admins to deploy add-ins, and is available to Global Administrators and Exchange Administrators. > > If you still want to continue using Centralized Deployment for admin deployment of add-ins, navigate to **Settings**, then select **Integrated Apps**. On top of the Integrated Apps page, choose the **Add-ins** link. If Integrated Apps is not available for you, you should be able to navigate to Centralized Deployment from **Settings**, and then select **Add-ins**. |
admin | Manage Plugins For Copilot In Integrated Apps | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/manage-plugins-for-copilot-in-integrated-apps.md | - Title: "Manage extensions for Copilot in Integrated Apps"-- NOCSH--- Previously updated : 11/09/2023----- Tier2-- scotvorg-- M365-subscription-management-- Adm_O365-- Adm_TOC-- m365copilot-- magic-ai-copilot--- AdminSurgePortfolio-- AdminTemplateSet-- BCS160-- MET150-- MOE150 -description: "Learn how to manage extensions for Copilot in the Integrated apps page in the Microsoft 365 admin center." ---# Manage extensions for Copilot in Integrated Apps --> [!IMPORTANT] -> -> - You must be licensed with Microsoft 365 Copilot to use extensions for Microsoft 365 Copilot. -> - The capability is enabled by default in all Microsoft 365 Copilot licensed tenants. -> - Admins can disable this functionality on a user and group basis and control how individual extensions are approved for use, and which extensions are enabled. --Microsoft 365 Copilot is a new experience inside Microsoft 365 that combines the power of large language models with your data and apps in Microsoft 365 to capture natural language commands to produce content and analyze data. Extensions for Copilot are extensions that enable Copilot to access and use third-party apps, such as Jira, [Dynamics 365](/microsoft-365-copilot/extensibility/overview-business-applications), or Bing Web Search. Admins can manage extensions for Copilot in the same way as they manage any other app in the Integrated apps section of the Microsoft 365 admin center. This document explains how admins can enable, disable, assign, block, or remove extensions for Copilot for their organization, and about Copilot capabilities and data privacy. --## Overview --Extensions enhance the functionality of Copilot by adding search capabilities, custom actions, connectors, and APIs. *Declarative copilots* are custom versions of Microsoft 365 Copilot that combine instructions, knowledge, and skills to perform specific tasks or scenarios. --Microsoft Copilot Studio (MCS) is a low code development platform that offers a graphical environment to build declarative copilots and other extensions tailored to the internal needs of an organization. Copilot Studio enables developers and makers to create and test their applications in a user-friendly interface. --However, before these applications can become accessible to end users, they need to undergo a streamlined process of submission and approval. To learn more, see [Publish extensions for Copilot](#publish-extensions-for-copilot). --When Copilot extensibility is enabled, users can see 3P extensions in Copilot that allows them to access the plugin for Copilot. The plugin hub Copilot experience shows the list of extensions that are available and deployed for the user. Users can toggle it on or off to restrict access of Copilot to any specific plugin during the interaction. Users can also add or remove extensions in their Copilot experience by right-clicking on the plugin and selecting the appropriate option. Users can only access the extensions that are allowed by the admin and that they have installed or been assigned to. --## Manage extensions for Copilot in the Microsoft 365 admin center --Admins can manage extensions for Copilot as apps in the Integrated apps section of the Microsoft 365 admin center, where they can see the list of available, deployed, or blocked apps for their organization. They will be able to: --- Enable/disable Copilot extensibility for the whole organization through Microsoft 365 admin center settings.-- Make available an app with extensions for Copilot to specific users or groups.-- Deploy or remove apps with extensions for Copilot for the whole organization or specific users or groups.-- Block or unblock apps with extensions for Copilot for the whole organization.--Admins can view all apps that have Copilot support from the list of available, deployed, or blocked apps on the Integrated apps page by using the filter option of **Microsoft 365 Copilot support** and setting it to **Yes**. --You can also check if a specific app has Copilot support by selecting it from apps list and checking if the app properties contains a tag stating **Microsoft 365 Copilot plug in is disabled** or **Microsoft 365 Copilot plug in is enabled**. --## Enable or disable Copilot extensibility --Admins can enable or disable Copilot extensibility at the tenant level by using a new setting in the tenant default options in the Integrated Apps section of the Microsoft 365 admin center. This setting allows admins to control who can access Copilot extensions in their organization. The setting has three options: --- **All Users**: This is the default option and it means that all users in the organization can access Copilot extensions, subject to the existing app policies and user assignments.-- **No Users**: This option means that no users in the organization can access Copilot extensions, and the 3P extensions are disabled in the Copilot plugin flyout. This option also hides the apps that have Copilot extensions from the Available apps and Deployed apps lists in the Microsoft 365 admin center.-- **Specific Users**: This option allows you to select specific users or groups in your organization to have access to Copilot extensions. So while all or specific users in your organization may have permissions to install and use apps from the Available apps and Deployed apps lists, only the users or groups you select in this setting can use Copilot extensions within these apps.--## Deploy or remove extensions for Copilot --Admins can deploy or remove extensions for Copilot across the whole organization or for specific users or groups by using the same gestures and controls that work for any other app in the Microsoft 365 admin center. Admins can select an app that has a plugin for Copilot from the Available apps or Deployed apps list and select **Deploy** or **Remove**. Admins can also choose to deploy or remove the app for everyone or specific users or groups. Deploying or removing an app affects its availability and functionality in Copilot as well as other host products, such as Outlook, Teams, or Microsoft 365. --## Manage how users can install extensions for Copilot --Admins can assign or unassign extensions for Copilot to specific users or groups by using the same gestures and controls that work for any other app in the Microsoft 365 admin center. Admins can select an app that has a plugin for Copilot from the Available apps or Deployed apps list and click on the **Assign** or **Unassign** button. Admins can also choose to assign or unassign the app to everyone or specific users or groups. Assigning or unassigning an app affects its availability and functionality in Copilot as well as other host products, such as Outlook, Teams, or Microsoft 365. --> [!IMPORTANT] -> Developers can [update the existing apps](/microsoft-365-copilot/extensibility/) to work with Microsoft Copilot. If the updated extension was pre-approved or pre-installed by an admin, then it'll update for the assigned users and starts working with Copilot. If a developer updates a previously blocked extension to work with Copilot and then the admins make the extension available to the users, then such an extension also works with Copilot. --## Block or unblock extensions for Copilot --Admins can block or unblock extensions for Copilot for the whole organization or specific users or groups by using the same gestures and controls that work for any other app in the Microsoft 365 admin center. Admins can select an app that has a plugin for Copilot from the Available apps or Deployed apps list and click on the block or unblock button. Admins can also choose to block or unblock the app for everyone or specific users or groups. Blocking or unblocking an app affects its availability and functionality in Copilot as well as other host products, such as Outlook, Teams, or Microsoft 365. --## View and consent to permissions and data access --For detailed information about how Microsoft 365 Copilot uses, protects, and shares organizational information to power extensibility, see [Data, Privacy, and Security for Microsoft 365 Copilot](/microsoft-365-copilot/microsoft-365-copilot-privacy). --## Publish extensions for Copilot --The publishing process in the Microsoft 365 admin center for apps with Copilot extensions submitted via Copilot Studio is designed to ensure governance and quality of the custom applications. It also reduces manual work by automating the submission of manifests, freeing developers and admins from tedious tasks. The simplified approval process reduces the time it takes for you to approve apps, making it easier for you to manage custom applications in the Microsoft 365 admin center. --The publishing process involves the following steps: --1. Developers create and test their apps with Copilot extensions in Copilot Studio, which provides a user-friendly interface for inputting the parameters and data for the applications. -2. Developers submit their apps with Copilot extensions for approval from Copilot Studio to the Microsoft 365 admin center. -3. You can discover the apps with Copilot extensions that are submitted but not yet approved in admin center under the new Requested Apps tab in the Integrated Apps section. The tab shows the name, host products, status, and Copilot readiness of the applications. The status can be either ΓÇÿPublish pendingΓÇÖ or ΓÇÿUpdate pendingΓÇÖ, depending on whether the application is new or has been updated by the developer. -4. You can select on any pending application to see more details and metadata, such as the description, requester, request date, and the status. These details help you to make an informed decision on whether to publish or reject the application. -5. You can approve or disapprove any pending application by selecting **Publish** or **Reject**. -- a. If the application is approved, it becomes available to the end users based on the tenant default settings and Copilot default settings. The application also becomes part of the ΓÇÿAvailable appsΓÇÖ list in the admin center, where admins can manage user assignments and other settings as any other MOS app. -- b. If the application is disapproved, it is removed from the ΓÇÿPending approvalΓÇÖ list in the admin center, and the status is shared with Copilot Studio. The developer can then make changes and resubmit the application for approval. --6. If the developer publishes an update to an existing application, the update is also submitted for approval and follows the same workflow as a new application. The update is shown in the ΓÇÿPending approvalΓÇÖ list with the status ΓÇÿUpdate pendingΓÇÖ. Until the update is approved, the previous version of the application remains available to the end users. |
admin | Office Addins | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/office-addins.md | Add-ins are supported in three desktop platforms: Windows, Mac, and Online Offic It can take up to 24 hours for an add-in to show up for client for all users. -Currently, Exchange admins, Global admins, and Azure Application admins can deploy add-ins from Integrated apps. +Currently, Exchange admins and Global admins can deploy add-ins from Integrated apps. ## Deploy your Office add-ins |
admin | Teams Apps Work On Outlook And M365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365.md | f1.keywords: Previously updated : 09/05/2023 Last updated : 09/18/2024 audience: Admin The following sections tell you more about the management tools available for th ## Before you begin -The following controls on Integrated Apps in the Microsoft 365 Admin Center are only available to Global Admins and Azure Application Admins. Check your credentials before you proceed. +The following controls on Integrated Apps in the Microsoft 365 Admin Center are only available to Global Admins. Check your credentials before you proceed. ## Controls for managing Teams apps that work on Outlook and the Microsoft 365 App As an admin, you can manage Teams apps that work on Outlook and the Microsoft 36 As an admin, you can now deploy these apps on Outlook, and Microsoft 365 (formerly known as Office.com) to a specific set of users, the entire organization, or just to yourself from Integrated Apps on Microsoft 365 admin center. Deploying an app means that it is preinstalled for the selected users on the applicable hosts of the app. -1. Sign into Microsoft 365 admin center as a Global Administrator or Azure Application Admin. +1. Sign into Microsoft 365 admin center as a Global Administrator. 2. Select **Settings** and then select **Integrated Apps**. 3. Select **Get apps** in the **Deployed Apps** list. This action opens up AppSource in embedded form from where you can select the app that you want to deploy. 4. Next, you see the deployment screen where general information about the app is given and the applicable products on which the app is deployed. As an admin, you can now deploy these apps on Outlook, and Microsoft 365 (former 6. Next, accept permissions if there are any. Then select **Next**. 7. Review and finish the deployment of the app. This app is now preinstalled for all selected users in the applicable hosts. -As a Global Administrator or Azure Application Admin, you can also initiate deployment of an app from its overview pane in the Available Apps list on Integrated Apps. +As a Global Administrator, you can also initiate deployment of an app from its overview pane in the Available Apps list on Integrated Apps. 1. Select the app you wish to deploy from the **Available Apps** list on **Integrated Apps**. 2. Next, select **Deploy app** in the overview pane. 3. Complete the deployment steps as listed above. The following sections tell you more about the tools available for managing avai ### How to see the available and blocked apps in your organization -1. Sign into Microsoft 365 admin center as a Global Administrator or Azure Application Admin. +1. Sign into Microsoft 365 admin center as a Global Administrator. 2. Select **Settings**, then select **Integrated Apps**. 3. Select the **Available Apps** or **Blocked Apps** list. Here you can view the status of all apps in the public catalog, as well as any custom line-of-business apps uploaded from Teams admin center or Microsoft 365 admin center. 4. Select an app to view more details about the app, applicable host products, and availability status within your organization. When you choose to unblock an app, the app reverts to the last saved state of av As an admin, you can control which apps can be installed and used by which users in your organization. By changing the availability, you're deciding how end users in your organization can install these apps from the store and use them on Outlook and the Microsoft 365 App. Admins can edit the availability of all 1P and 3P store apps and LOB apps uploaded by them. -1. Sign into the Microsoft 365 admin center as a Global Administrator or Azure Application Admin. +1. Sign into the Microsoft 365 admin center as a Global Administrator. 2. Select **Settings**, then select **Integrated Apps**. 3. Select the **Available Apps** list. 4. Next, select the app you want to edit. This launches the appΓÇÖs overview pane. As an admin, you can control which apps can be installed and used by which users As an admin, you can control the default state of any new and incoming app in your organization. The default setting for any organization is set to **All users in the organization can install**. You can change this default setting on Integrated Apps in the Microsoft 365 admin center. -1. Sign into the Microsoft 365 admin center as a Global Administrator or Azure Application Admin. +1. Sign into the Microsoft 365 admin center as a Global Administrator. 2. Select **Settings**, then select **Integrated Apps**. 3. Select the **Available Apps** list. 4. Next, select the Settings icon to open the **Customize default settings** pane. You can also upload custom line of business apps and deploy/pre-install them for Whenever a custom line of business app is uploaded, it is made available to all users in the organization for installation and use by default. You can edit the availability of this custom line of business app from the Available apps list. For more information, see the section about [how to manage availability of an app in your organization](#how-to-manage-the-availability-of-an-app-in-your-organization). -As a Global Administrator or Azure Application Admin, you can also initiate deployment of a custom app (uploaded from Teams Admin Centre) from its overview pane in the Available Apps list on Integrated Apps. +As a Global Administrator, you can also initiate deployment of a custom app (uploaded from Teams Admin Centre) from its overview pane in the Available Apps list on Integrated Apps. 1. Once the app is uploaded from Teams Admin Center, it will show up in the **Available Apps** list on **Integrated Apps** with the availability status of **All users in the organization can install**. 2. Select the app from the **Available Apps** list on **Integrated Apps**. |
admin | Teams Apps Work Only On Teams | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/teams-apps-work-only-on-teams.md | f1.keywords: Previously updated : 05/11/2023 Last updated : 09/18/2024 audience: Admin In addition to the controls available to you in the Integrated Apps portal, admi ## How to block a Teams app on Teams -1. Sign into Microsoft 365 admin center as a Global Administrator or Azure Application Admin. +1. Sign into Microsoft 365 admin center as a global administrator. 2. Select **Settings**, and then select **Integrated Apps**. 3. Select the **Available Apps** list. 4. Select an app with the status **Some or all users in the organization can install** from the **Available Apps** list to open the overview pane. These apps will always have only Teams listed as host product. When the admin blocks such an app, it's blocked for all users in the organizatio ## How to unblock a Teams app on Teams? -1. Sign into Microsoft 365 admin center as a Global Administrator or Azure Application Admin. +1. Sign into Microsoft 365 admin center as a global administrator. 2. Select **Settings**, and then select **Integrated Apps**. 3. Select the **Blocked Apps** list. 4. Select an app from the **Blocked Apps** list to open the overview pane. |
admin | Test And Deploy Microsoft 365 Apps | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps.md | f1.keywords: Previously updated : 08/30/2023 Last updated : 09/18/2024 audience: Admin As an admin, the following app/add-in types can be managed from the Integrated a |Type|Supported Host Products (any or all)|What can admins control on Integrated Apps portal?|Which admins can access the controls on Integrated Apps portal?|Other admin centers & related actions| ||||||-|Add-in|Outlook<br/><br/><br/> Word, Excel, PowerPoint|[Deploy/Edit deployed users/Remove deployment](/microsoft-365/admin/manage/office-addins#deploy-your-office-add-ins)|Exchange Admin<br/><br/> Global Admin<br/><br/> Azure Application Admin| Exchange Admin Center for default role assignment policy.<br/><br/> Microsoft 365 Admin Center > Org Settings for Office Store setting| +|Add-in|Outlook<br/><br/><br/> Word, Excel, PowerPoint|[Deploy/Edit deployed users/Remove deployment](/microsoft-365/admin/manage/office-addins#deploy-your-office-add-ins)|Exchange Admin<br/><br/> Global Admin | Exchange Admin Center for default role assignment policy.<br/><br/> Microsoft 365 Admin Center > Org Settings for Office Store setting| |SPFx App|SharePoint|[Deploy/Remove deployment](/microsoft-365/admin/manage/office-addins#deploy-your-office-add-ins)|Global Admin|SharePoint Admin Center| |Web App|N/A|[Deploy/Edit deployed users](/microsoft-365/admin/manage/office-addins#deploy-your-office-add-ins) |Global Admin<br/><br/>Azure Application Admin|Microsoft Entra admin center| |Teams app (manifest version less than 1.13)|Teams|[Block & Unblock](/microsoft-365/admin/manage/teams-apps-work-only-on-teams)|Global Admin|Go to Teams admin center for default tenant setting, deployment and managing availability|-|Teams app (manifest version equal to or greater than 1.13)|Outlook<br/><br/> Microsoft 365 App<br/><br/> Teams| [Deploy/Edit deployed users/Remove deployment](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#deploy-a-teams-app-that-works-on-outlook-and-the-microsoft-365-app-via-the-integrated-apps-portal)<br/><br/> [Block & Unblock](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#manage-how-users-can-install-teams-apps-on-outlook-and-the-microsoft-365-app) <br/><br/> [Manage availability>Edit users](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#how-to-manage-the-availability-of-an-app-in-your-organization)<br/><br/> [Default setting for tenant](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#customize-default-settings-for-teams-apps-that-work-on-outlook-and-the-microsoft-365-app)|Global Admin<br/><br/>Azure Application Admin|Go to Teams admin center to manage how this app shows up in Teams for users in your organization.| +|Teams app (manifest version equal to or greater than 1.13)|Outlook<br/><br/> Microsoft 365 App<br/><br/> Teams| [Deploy/Edit deployed users/Remove deployment](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#deploy-a-teams-app-that-works-on-outlook-and-the-microsoft-365-app-via-the-integrated-apps-portal)<br/><br/> [Block & Unblock](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#manage-how-users-can-install-teams-apps-on-outlook-and-the-microsoft-365-app) <br/><br/> [Manage availability>Edit users](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#how-to-manage-the-availability-of-an-app-in-your-organization)<br/><br/> [Default setting for tenant](/microsoft-365/admin/manage/teams-apps-work-on-outlook-and-m365#customize-default-settings-for-teams-apps-that-work-on-outlook-and-the-microsoft-365-app)|Azure Application Admin|Go to Teams admin center to manage how this app shows up in Teams for users in your organization.| ## Other admin centers You can continue to manage access to Office add-ins and Teams apps via the follo You can continue to deploy [Deploy and manage Office Add-ins](/microsoft-365/admin/manage/office-addins) and [Teams Apps via Teams admin center](/microsoftteams/manage-apps). +## Find support information for apps ++In the Integrated Apps page, when evaluating an app, you can review the Terms of Use and Privacy Policy of the application before you make it available to your users. ++You can access this information in the following ways: ++- For publicly available Store apps, links to Terms of Use, Privacy Policy, and Support are available on [AppSource](https://appsource.microsoft.com). Search for an application and navigate to its **Details + Support** tab for the links. ++ :::image type="content" source="../../media/app-support-legal-info.png" alt-text="Screenshot to show how to find app support information on AppSource website."::: ++- For a custom app, contact the app developer who initiated the request to upload the custom app. For Copilot agents submitted via Microsoft Copilot Studio, Teams Toolkit, or any other source, requester's contact details are available in the app details pane in `Requested Apps` tab. ++- You can view the same information of an app in the Teams admin center as well. For details, see [how to find support information for an app](/microsoftteams/manage-apps#support-information-for-apps). + ## Frequently asked questions ### Which administrator role do I need to access Integrated apps? |
backup | Backup 3P Billing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/backup/storage/backup-3p-billing.md | - - essentials-overview ms.localizationpriority: medium description: Set up third-party billing for Microsoft 365 Backup Storage. |
backup | Backup 3P Lifecycle | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/backup/storage/backup-3p-lifecycle.md | - - essentials-overview ms.localizationpriority: medium description: Application lifecycle for Microsoft 365 Backup Storage. |
backup | Backup 3P Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/backup/storage/backup-3p-overview.md | - - essentials-overview ms.localizationpriority: medium description: Overview for third-party developers for Microsoft 365 Backup Storage. |