Add Submit to your org catalog content for Agent Builder

docs/TOC.yml

@@ -180,6 +180,10 @@ items:
         href: agent-builder-add-knowledge.md
       - name: Share and manage agents
         href: agent-builder-share-manage-agents.md
+      - name: Submit to your org catalog
+        href: agent-builder-submit-to-org-catalog.md
+      - name: Privacy statement and terms of use
+        href: agent-builder-publication-privacy-terms-of-use.md
       - name: Availability and language support
         href: agent-builder-regional-availability.md
       - name: Copy your agent to Copilot Studio

docs/agent-builder-publication-privacy-terms-of-use.md

@@ -0,0 +1,42 @@
+---
+title: Privacy statement and terms of use for agents
+description: Provide valid privacy statement and terms of use URLs when you submit an agent from Agent Builder to your org catalog.
+author: sophie-roy3
+ms.author: sophieroy
+ms.localizationpriority: medium
+ms.date: 05/04/2026
+ms.topic: article
+ms.service: copilot-studio
+ms.subservice: agent-builder
+---
+
+# Privacy statement and terms of use
+
+When you [submit an agent from Agent Builder to your org catalog](agent-builder-submit-to-org-catalog.md), you must provide links to your organization's privacy statement and terms of use. These URLs appear in the agent details pane in the Agent Store, where users can review them before they install the agent.
+
+## Get your URLs
+
+Privacy statement and terms of use URLs are specific to your organization. Work with your IT department or legal team to get:
+
+- Your organization's **privacy statement** URL, which explains how your agent collects, uses, and protects user data.
+- Your organization's **terms of use** URL, which describes the conditions under which users can interact with your agent.
+
+Both URLs must be:
+
+- Valid, resolvable HTTPS URLs.
+- Accessible to all users in your organization who might install the agent.
+
+Default placeholder URLs aren't suitable for production submissions. Agent Builder shows a warning on these fields if the URL matches a default link.
+
+## Impact on the shared version of your agent
+
+The privacy statement and terms of use URLs apply to both the shared version of your agent and the Agent Store version. When you save these URLs, either in the submission dialog or in the **About this agent** dialog, both versions are updated.
+
+> [!NOTE]
+> To update these URLs after approval, resubmit your agent for admin review. Changes to the version you share directly in Agent Builder apply immediately. Changes to the Agent Store version apply only after admin approval.
+
+## Related content
+
+- [Submit agents from Agent Builder to your org catalog](agent-builder-submit-to-org-catalog.md)
+- [Share and manage agents](agent-builder-share-manage-agents.md)
+- [Publish agents in the Microsoft 365 admin center](/microsoft-365/admin/manage/agent-registry#publish-agents)

docs/agent-builder-share-manage-agents.md

@@ -4,7 +4,7 @@ description: Learn how to share and manage agents built with Microsoft 365 Copil
 author: jasonxian-msft
 ms.author: jasonxian
 ms.localizationpriority: medium
-ms.date: 04/17/2026
+ms.date: 05/05/2026
 ms.topic: article
 ms.service: copilot-studio
 ms.subservice: agent-builder
@@ -16,22 +16,6 @@ You can share the agents you create using Microsoft 365 Copilot with users in yo
 
 This article describes how to share and manage the agents you build using the Agent Builder feature in Microsoft 365 Copilot. To publish an agent across multiple channels, you need to use Copilot Studio. For more information, see [Publish and deploy your agent](/microsoft-copilot-studio/publication-fundamentals-publish-channels).
 
-## Differences between sharing and publishing agents
-
-Sharing an agent is intended for limited, direct access to it. This approach is ideal for collaborating or getting feedback as you create your agent, but can't be used for formal deployment or integration.
-
-The following table highlights the key differences between publishing and sharing your declarative agents.
-
-|         | Sharing | Publishing |
-| ------- | ------- | ------- |
-| **Purpose** | Collaboration, feedback, testing, or limited access for specific individuals or groups. | Formal deployment for broad use, integration, scaled across specified channels (for example, Teams, Copilot) or the entire organization. |
-| **Mechanism** | Owner/co-owners use **Manage Sharing** to specify individuals, groups, or teams by name or email. The specified recipients receive direct access, but the agent remains private and not broadly discoverable. | Owner/co-owners select **Publish** in Copilot Studio, select the target channel (Teams, Copilot, and more), and complete any required approval flows. The agent becomes discoverable and accessible to the intended audience. |
-| **Audience** | Named users (individuals, groups, or teams). | Organization-wide or channel-specific. |
-| **Discoverability** | Private; only visible to specified recipients. | Public (within the chosen scope); appears in the Agent Store and specified channels. |
-| **Governance** | Minimal governance; no approval flows. | Might require approval flows, versioning, and lifecycle management. |
-| **Permissions** | Specified users can interact with, but not manage or publish, the agent. | Owner/co-owners manage publishing, updates, and lifecycle. |
-| **Integration** | Not integrated; sharing is only available via direct access. | Can be integrated into Teams, Copilot, or other Microsoft 365 surfaces. |
-
 ## Share an agent
 
 To share your agent, after you [build and test](agent-builder-build-agents.md) it in Microsoft 365 Copilot, choose **Create**. After your agent is created, a confirmation message indicates that the agent is private and only available to you. To share the agent with others, select the **Share** button and choose who should have access.
@@ -102,6 +86,34 @@ You can select which SharePoint folders and files to share. Sharing only works w
 
 When a user's access to the agent is removed, it doesn't affect their access to the shared file or folders. Manage user permissions to access file and folders directly through SharePoint.
 
+## Update your agent's About information
+
+Use the **About this agent** dialog to update the metadata that's visible in the Agent Store and in your agent's About information in Microsoft 365 Copilot. You can open this dialog for any agent you own, whether or not it's shared or submitted to your org catalog.
+
+To open the dialog, select the **More** ellipses (**...**) in the agent authoring header, and then select **About this agent**.
+
+The following fields are available.
+
+| Field | Required or optional | Maximum length | Description |
+| --- | --- | --- | --- |
+| **Short description** | Required | 80 characters | A concise summary of what the agent does. Shown in the Agent Store and in the agent's About information. Default: *Built using Microsoft 365 Copilot Agent Builder*. |
+| **Creator website** | Optional | 2,048 characters | A link to more information about you or your team, such as your profile page, your team's SharePoint site, or an internal support page. Opens when users select the creator's name in the agent details pane. Must be a valid HTTPS URL. |
+| **Privacy statement** | Optional | 2,048 characters | A link to your organization's privacy statement. Must be a valid HTTPS URL. |
+| **Terms of use** | Optional | 2,048 characters | A link to your organization's terms of use. Must be a valid HTTPS URL. |
+
+A default placeholder URL is provided for **Creator website**, **Privacy statement**, and **Terms of use**. Replace each placeholder with a URL that's appropriate for your agent; otherwise, Agent Builder shows a warning on the field.
+
+> [!NOTE]
+> Values you save in **About this agent** prepopulate the corresponding fields in the submission dialog when you submit your agent to your org catalog. For more information, see [Privacy statement and terms of use](agent-builder-publication-privacy-terms-of-use.md).
+
+## Submit an agent to your org catalog
+
+The shared version of your agent and the Agent Store version are managed separately. You manage the shared version and can continue iterating on it, changing who it's shared with, or keeping it private for testing, at any time. Your admin manages the Agent Store version after you submit the agent for review.
+
+To make your agent broadly discoverable in your organization, submit it to your org catalog. An admin reviews the submission in the [Microsoft 365 admin center](/microsoft-365/admin/manage/agent-registry#publish-agents) and, if approved, publishes the agent in the **Built by your org** section of the Agent Store.
+
+For the submission flow, required fields, approval status tracking, and post-approval updates, see [Submit agents from Agent Builder to your org catalog](agent-builder-submit-to-org-catalog.md).
+
 ## Manage agents
 
 You can access the agent management features in Microsoft 365 Copilot:
@@ -169,7 +181,10 @@ When sharing an agent and its knowledge sources, you might encounter the errors
 
 ## Related content
 
+- [Submit agents from Agent Builder to your org catalog](agent-builder-submit-to-org-catalog.md)
+- [Privacy statement and terms of use](agent-builder-publication-privacy-terms-of-use.md)
 - [Publish agents for Microsoft 365 Copilot](publish.md)
+- [Manage agent requests in the Microsoft 365 admin center](/microsoft-365/admin/manage/agent-requests)
 - [Publish and deploy your agent](/microsoft-copilot-studio/publication-fundamentals-publish-channels)
 - [Upload into Microsoft Teams](/microsoftteams/platform/concepts/deploy-and-publish/apps-upload)
 - [Reassign an agent's owner with PowerShell](/power-platform/release-plan/2025wave2/microsoft-copilot-studio/reassign-agents-owner-powershell)

docs/agent-builder-submit-to-org-catalog.md

@@ -0,0 +1,146 @@
+---
+title: Submit agents from Agent Builder to your org catalog
+description: Learn how to submit agents built with Agent Builder to your organization's catalog for admin review and publication in the Microsoft 365 Copilot Agent Store.
+author: sophie-roy3
+ms.author: sophieroy
+ms.localizationpriority: medium
+ms.date: 04/21/2026
+ms.topic: article
+ms.service: copilot-studio
+ms.subservice: agent-builder
+---
+
+# Submit agents from Agent Builder to your org catalog
+
+You can submit agents you build with Agent Builder in Microsoft 365 Copilot to your organization's catalog for broader use. When you submit your agent, an admin reviews it in the Microsoft 365 admin center and, after they approve, publishes it to the Agent Store under **Built by your org**. From there, the agent is available as a trusted, organization-approved solution for users across your tenant.
+
+This article describes how to submit an agent, track its approval status, and manage its Agent Store listing after approval. For details about the admin actions, see [Publish agents in the Microsoft 365 admin center](/microsoft-365/admin/manage/agent-registry#publish-agents).
+
+## Sharing and the Agent Store
+
+Agents built with Agent Builder can reach other users through two separate paths:
+
+- **Share your agent** with specific people or groups. You manage the shared agent, including its sharing settings and updates. Changes you publish are visible to shared users right away.
+- **Submit your agent to your org catalog.** An admin reviews and publishes the agent to the Agent Store. The admin manages the Agent Store listing, including availability. Changes apply to the Agent Store listing only after an admin approves a resubmission.
+
+The shared version and the Agent Store version are tracked as two separate entries. You can continue iterating on your shared agent at any time, including changing who it's shared with or keeping it private for testing, without affecting the Agent Store version. When you're ready to roll a meaningful update into the Agent Store, resubmit the agent for admin review.
+
+The following table highlights the key differences between the two paths.
+
+| | Sharing | Submit to your org catalog |
+| --- | --- | --- |
+| **Managed by** | The maker | The maker authors the agent; an admin manages the Agent Store listing. |
+| **Audience** | Named users, groups, or teams | Anyone in your organization, based on admin availability settings. |
+| **Review** | None | Admin review in the [Microsoft 365 admin center](/microsoft-365/admin/manage/agent-registry#publish-agents). |
+| **Distribution** | Shareable link | Agent Store, under **Built by your org**. |
+| **Update cycle** | Changes apply immediately when you publish | Changes apply only after admin approval of a resubmission. |
+| **When to use** | Iterating, piloting, or distributing to a known audience | Broad organizational availability for a production-ready agent. |
+
+> [!NOTE]
+> Sharing limits set by your admin apply only to the shared version. They don't restrict who can install the Agent Store version. Admin availability settings in the Microsoft 365 admin center control who sees the Agent Store version.
+
+## What admins review
+
+When you submit your agent, your admin reviews the following to validate security, compliance, and data access behavior:
+
+- The agent's display name and short description
+- Configured capabilities and knowledge sources
+- The agent's sensitivity label
+- Developer information (developer name, creator website, privacy statement, terms of use)
+- Metadata about the underlying declarative agent
+
+For details, see [Publish agents in the Microsoft 365 admin center](/microsoft-365/admin/manage/agent-registry#publish-agents).
+
+## Before you submit
+
+Make sure that your agent is ready for organizational use before you submit.
+
+### Prerequisites
+
+- Your agent is published. The **Submit to your org catalog** menu item is disabled until the agent is published at least once.
+- Your agent is complete, production-ready, and compliant with your organization's standards, rules, and policies.
+- Users who install the agent have access to the knowledge sources it uses.
+
+### Best practices
+
+- **Use governed knowledge sources.** Prefer SharePoint sites and other shared sources that your intended audience can access.
+- **Disclose personal knowledge usage.** If your agent uses personal Work IQ knowledge sources, such as Microsoft Teams meetings, chats, or emails, mention this in the short description so users know the agent might reference their personal work data.
+- **Design for organizational scale.** Use neutral, professional language in the agent's description and starter prompts. Test with sample users before you submit.
+- **Provide complete metadata.** Include accurate developer information and links to your organization's privacy statement and terms of use. For more information, see [Privacy statement and terms of use](agent-builder-publication-privacy-terms-of-use.md).
+
+## Submit an agent to your org catalog
+
+1. In Microsoft 365 Copilot, go to **All agents**, select the agent you want to submit, and then select **Edit**.
+
+1. If your draft contains unpublished changes, select **Update** to publish them. Submission uses the latest published version of your agent.
+
+1. In the agent authoring header, select the **More** ellipses (**...**), and then select **Submit to your org catalog**.
+
+   You can also start submission from:
+
+   - The share dialog, by selecting the **Submit to your catalog** link.
+   - The publish success dialog, by selecting the **Submit to your catalog** link.
+
+1. In the submission dialog, provide the following information. All fields are required.
+
+   | Field | Max length | Description |
+   | --- | --- | --- |
+   | **Display name** | 30 characters | The name that appears in the Agent Store. |
+   | **Short description** | 80 characters | A concise summary of what the agent does. Default: *Built using Microsoft 365 Copilot Agent Builder*. |
+   | **Developer name** | 32 characters | Your name or your team's name. |
+   | **Creator website** | 2,048 characters | A link to more information about you or your team, such as your profile page, your team's SharePoint site, or an internal support page. Opens when users select the creator's name in the agent details pane. Must be a valid HTTPS URL. Replace the default placeholder link with your own. |
+   | **Privacy statement** | 2,048 characters | A link to your organization's privacy statement. Must be a valid HTTPS URL. Replace the default placeholder link with your organization's URL. For details, see [Privacy statement and terms of use](agent-builder-publication-privacy-terms-of-use.md). |
+   | **Terms of use** | 2,048 characters | A link to your organization's terms of use. Must be a valid HTTPS URL. Replace the default placeholder link with your organization's URL. |
+
+   > [!TIP]
+   > **Short description**, **Creator website**, **Privacy statement**, and **Terms of use** are prepopulated from your agent's **About this agent** settings. To set these values without starting a submission, use **About this agent** from the agent authoring header. For more information, see [Update your agent's About info](agent-builder-share-manage-agents.md#update-your-agents-about-information).
+
+1. Select **Continue**. Agent Builder saves your changes, publishes the updated version, and submits it for admin review.
+
+After you submit, the dialog shows **Submitted for admin approval** along with next steps.
+
+## Track submission status
+
+To check status at any time, open the agent, select the **More** ellipses (**...**), and then select **Submit to your org catalog**. The dialog shows the current state.
+
+| Status | Meaning |
+| --- | --- |
+| **Waiting for approval** | Your submission is pending admin review. |
+| **Approved** | Your admin approved the submission. The agent is available in the Agent Store under **Built by your org**. |
+| **Rejected by your admin** | Your admin rejected the submission. The banner includes the reviewer's comment so you know what to fix before resubmitting. |
+
+An agent can have only one active pending submission. If you resubmit while a submission is pending, the new submission replaces the existing one.
+
+## Update an approved agent
+
+Changes you publish in Agent Builder don't automatically flow through to the Agent Store. Resubmit the agent when you want your updates reviewed and published to the Agent Store.
+
+1. Make your changes in Agent Builder and select **Update** to publish.
+1. On the publish success dialog, select the **Submit to your catalog** link.
+1. Complete the submission dialog as described in [Submit an agent to your org catalog](#submit-an-agent-to-your-org-catalog).
+
+After approval, subsequent submissions are reviewed as updates to the same agent, not as new submissions. Admins see incremental changes to facilitate faster review.
+
+> [!IMPORTANT]
+> Changes published in Agent Builder update the shared version immediately. The Agent Store version doesn't update until an admin approves your resubmission. Until then, users who install the agent from the Agent Store continue to see the last approved version.
+
+## Find your agent in the Agent Store
+
+After your agent is approved, you can open its Agent Store listing to share the URL with users. Use either of the following methods.
+
+**From the submission dialog:**
+
+1. Open the agent and select the **More** ellipses (**...**) > **Submit to your org catalog**.
+1. On the **Approved** banner, select **Go to Agent Store**.
+
+**From All agents:**
+
+1. In Microsoft 365 Copilot, select **All agents**.
+1. Under **Built by your org**, find your agent. To locate it quickly, use the search.
+1. Select the agent to open the agent details pane, and then select the link icon to copy the agent's URL.
+
+## Related content
+
+- [Privacy statement and terms of use](agent-builder-publication-privacy-terms-of-use.md)
+- [Share and manage agents](agent-builder-share-manage-agents.md)
+- [Manage agent requests in the Microsoft 365 admin center](/microsoft-365/admin/manage/agent-requests)