Merge branch 'main' of https://github.com/MicrosoftDocs/microsoft-365-docs-pr into cz-10297224-taskbar

Author: aczechowski

copilot/copilot-agent-install.md

@@ -4,7 +4,7 @@ f1.keywords:
 ms.author: erikre
 author: ErikRe
 manager: dansimp
-ms.date: 06/25/2025
+ms.date: 07/10/2025
 audience: Admin
 ms.topic: concept-article
 ms.service: microsoft-365-copilot
@@ -54,6 +54,10 @@ Users can install agents that are available in Agent Store based on the policies
 
 Organizations can govern these agents in the Copilot Control System section of the Microsoft 365 admin center. Administrators have a full set of lifecycle management tools for these agents. Microsoft offers granular controls that enable administrators to install and block agents. Additionally, administrators can remove shared and custom agents for some or all of the users in their tenant.
 
+### Microsoft-built agent licensing 
+
+Some agents built by Microsoft, including Researcher and Analyst, are governed by [Supplementary Terms of Service](https://support.microsoft.com/office/supplementary-terms-of-service-for-teams-apps-powered-by-microsoft-365-services-and-applications-bc6027fe-68c3-4758-a70d-cfe97c43b4e2) which refers to the Microsoft 365 [Product Terms](https://www.microsoft.com/licensing/terms/productoffering/Microsoft365/all), and by reference, includes the Data Protection Addendum (DPA). The same Product Terms and DPA also govern the Microsoft 365 Copilot service. 
+
 ## Related content
 
 - [Manage agents for Microsoft 365 Copilot in the Microsoft 365 admin center](/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps)

copilot/employee-self-service/known-issues-limitations.md

@@ -54,7 +54,7 @@ Applies to:
 |-----|-----------|------------|----------------------|
 |Domain support |Limited to a single domain per environment (either HR or IT). |Multi-domain support within the same environment is planned for release in the second half of CY2025. |Begin with the domain that will deliver the most immediate value to your organization—either HR or IT. If you need both, consider creating separate Power Platform environments: one for HR and another for IT. |
 |Third-party connector setup |Power Platform connectors can’t be used with on-premises gateway connections at this time. |There are no plans to include this in the future roadmap. |If needed, consider moving your key content to a cloud platform like SharePoint or ServiceNow. |
-|Third-party connector setup |Hierarchical Permissions in ServiceNow Graph Connector doesn't work currently. |Support for hierarchical permissions is planned for release in the second half of CY2025. |If you need support for Hierarchical Permissions in ServiceNow Knowledge for ESS Agent, fill [this form](https://forms.office.com/r/BVvQktxXw1). This feature isn't Generally Available, and we're allowlisting tenants on request basis. |
+|Third-party connector setup |Hierarchical Permissions in ServiceNow Graph Connector doesn't work currently. |Support for hierarchical permissions is planned for release in the second half of CY2025. |If you need support for Hierarchical Permissions in ServiceNow Knowledge for ESS Agent, fill [this form](https://forms.office.com/r/Cu7DTDg0uz). This feature isn't Generally Available, and we're allowlisting tenants on request basis. |
 |Third-party connector setup |Third-party connector setup (like Workday, ServiceNow, or SuccessFactors) takes time, can be complex, and typically needs someone with deep technical expertise. |By design - there are no plans to include it in the future roadmap. |To work around this, carefully follow the setup documentation and involve someone with subject matter expertise in configuring third-party systems. Alternatively, consider starting with SharePoint as your initial knowledge source. You can add ISV connectors once your IT team has the necessary expertise and capacity to manage the integration effectively. |
 |Third-party connector setup |The ESS Agent only includes prebuilt 'read' scenarios for supported connectors. If you want to enable actions like time-off requests or approvals, wait for those to be supported |Support for more read/write scenarios is planned for release in the second half of CY2025. |Start with agent’s knowledge retrieval scenarios first. For advanced task completion scenarios, wait for those to be supported or set-up custom Topic workflows. |
 |Third-party connector setup |Only supports User Principal Name (UPN) based user mapping for third party integrations |Support for non-UPN based mapping is under evaluation and targeting for post-July 2025 |Work with the third party provider to have UPN based user-mapping for integrations |

microsoft-365/commerce/subscriptions/self-service-purchase-faq.yml

@@ -6,7 +6,7 @@ metadata:
   author: cmcatee-MSFT
   ms.author: cmcatee
   manager: scotv
-  ms.reviewer: sinakassaw, nicholak
+  ms.reviewer: nicholak
   audience: Admin
   ms.topic: faq
   ms.service: microsoft-365-business
@@ -25,7 +25,7 @@ metadata:
   search.appverid:
   - MET150
   description: "Find answers to commonly asked questions about self-service purchases."
-  ms.date: 01/06/2025
+  ms.date: 07/09/2025
 title: Self-service purchase FAQ
 summary: |
   Self-service purchase gives users a chance to try out new technologies and develop solutions that ultimately benefit their larger organizations. Central procurement and IT teams have visibility to all users who buy and deploy self-service purchase solutions through the <a href="https://go.microsoft.com/fwlink/p/?linkid=2024339" target="_blank">Microsoft 365 admin center</a>. Admins can turn off self-service purchasing on a per product basis via PowerShell. To learn more, see [Use AllowSelfServicePurchase for the MSCommerce PowerShell module](allowselfservicepurchase-powershell.md).