Publish and validate in channels
After the agent passes your tests, publish it and configure how users or events invoke it. Validate the live version under the identities and conditions it supports.
Distinguish channels, triggers, and hooks
Channels, triggers, and hooks describe different parts of agent execution. They aren't alternative names for the same feature.
| Concept | Purpose | Example |
|---|---|---|
| Channel | Provides the surface through which a user or client interacts with the agent | An employee chats with the support policy agent in Microsoft Teams |
| Trigger | Defines what invokes the agent and provides input for the run | A new email, a SharePoint item, or a schedule starts an autonomous run |
| Hook | Runs a bound workflow automatically at a defined point during agent execution | A workflow checks a proposed tool call before the tool runs |
These features can work together. An agent can support chat interactions, have event triggers, and use hooks during execution. The trigger experience also includes chat and Copilot and Teams triggers, so a trigger doesn't always mean an external business event.
Unlike a workflow exposed as a tool, which the agent chooses when relevant, a hook invokes its workflow whenever its configured lifecycle event occurs. Hooks can add context when a conversation starts, check or block tool calls, process tool results, or handle errors. Here, hook means an agent lifecycle hook, not an inbound webhook endpoint.
Note
Event triggers for autonomous agents and hooks are preview capabilities. Confirm availability in your environment. For details, see Add triggers to an agent and Hooks overview.
Priya's support policy agent uses conversational channels. She configures Microsoft Teams and Microsoft Copilot distribution, tests with typical employee permissions, and follows her organization's approval process. An event-driven agent also needs activation, while an agent with hooks needs validation of the configured lifecycle events.
Publish to Teams and Microsoft Copilot
Select Publish on the Build tab to open the Publish agent dialog. Review and configure the channels in that dialog before you confirm publication. Publishing creates a live version of the saved draft. Later draft edits don't affect users until you publish again.
Before you publish, confirm:
- You've completed evaluation and addressed known quality issues.
- All required knowledge sources, tools, and workflows are correctly configured.
- You understand what permissions your users need to access the knowledge sources and tools the agent calls.
- You know your organization's policies for channel availability and administrator approval.
If your design requires an agent account, configure it before the agent's first publication. For requirements, see Give your agent an account (Frontier).
Use the publishing flow for agents powered by the Microsoft Copilot harness:
- Save the agent changes that you want to release.
- Select Publish.
- In the Publish agent dialog, review the agent details and select and configure Microsoft Teams and Microsoft Copilot as the intended channels.
- Resolve any readiness issues, such as a missing name, description, or instructions. If a channel is unavailable because of authentication settings or data policies, review the restriction with your administrator.
- Select Publish to confirm, and wait for publication to finish.
- Use the confirmation options to share the agent or add it to the organization catalog, following your organization's approval process.
Publishing and distribution are separate checks. A successful publish creates the live version; users still need access through a configured channel and an allowed sharing or catalog path. Follow the installation or access steps presented for that channel, and verify availability in Teams and Microsoft Copilot separately if both are intended.
When you update the agent, select Publish, review the Publish your changes dialog, and confirm publication. Test the updated live version in its intended channels.
Note
Channel configuration and distribution options can vary by experience and tenant policy. Don't assume that standard-harness controls such as Availability options or Built with Power Platform discovery are present in this experience. Follow the options shown in your environment and contact your administrator to confirm the distribution path.
The built-in test channel that powers Preview is distinct from distribution channels. In the current public preview behavior, a data-policy violation affecting only that test channel doesn't block publication. It doesn't grant access to blocked connectors or endpoints either. Distribution-channel restrictions still apply. Neither a successful preview nor a successful publish proves that every channel and connector combination is allowed.
Release autonomous agents and hook changes
Activate an agent with event triggers
An agent with event triggers needs activation as well as publication. Before you publish, test each trigger with a matching event or a previous trigger event. Confirm that the event details lead to the intended actions.
After you publish the agent with its triggers:
- Choose whether to activate it for yourself or share it for others to use.
- For your own use, follow the activation option to Agent management, and turn on the agent. It runs on your behalf using your authenticated connections.
- For other users, configure triggers and tools for user authentication, share the agent, and send recipients the setup link. Recipients complete required connections and activate the agent for themselves.
Publishing or sharing alone doesn't complete a recipient's setup. Users can change only the trigger options you permit. Republish after you change triggers, instructions, or tools, and confirm that affected users accept updates when prompted. For setup details, see Add triggers to an agent.
Save and publish hook changes
To configure hooks, select the three dots (...) on the command bar, and then select Hooks, rather than looking for them in the Build tab's component list. Each hook binds a supported lifecycle event to a workflow with matching inputs and outputs.
Selecting Done in the hook dialog adds the change to the draft but doesn't save it. Save the agent, then publish it to apply the hook for users. Save and republish edits or removals too. For configuration details, see Hooks overview.
Validate after publishing
Publishing doesn't prove that the agent works for everyone. Test it with an account that has the same permissions as its intended users.
Sign in with an account that has the same access level as a standard employee and test the following:
| Validation area | What to confirm |
|---|---|
| Authentication | The agent loads and responds without sign-in errors or access-denied messages |
| Knowledge retrieval | The agent retrieves content from knowledge sources and returns accurate answers |
| Citations | Knowledge sources are cited correctly and links resolve to accessible content |
| Tool and workflow execution | Tools and workflows run without errors when the agent invokes them |
| Scope and boundaries | The agent declines out-of-scope requests as configured in its instructions |
| Escalation | The agent provides specific escalation contacts or paths when the user requests them |
If the agent uses event triggers or hooks, also perform the applicable checks:
| Configuration | What to confirm |
|---|---|
| Event trigger | A matching event invokes the activated agent under the intended identity and produces the expected result |
| Shared autonomous agent | The recipient completes required connections and activation, and the agent uses that recipient's credentials |
| Lifecycle hook | The configured event invokes the bound workflow and its response has the intended effect |
| Blocking hook | A disallowed tool call is blocked, while an allowed call still succeeds |
For example, if a pre-tool hook checks whether a proposed update meets a business rule, test both a permitted update and a prohibited one. A successful conversation alone doesn't prove that the hook enforces the rule.
Most post-publish failures fall into one of three categories:
- Permission failures: The published user can't access a SharePoint site, Dataverse table, or other resource the agent queries. Review and update the resource permissions for the users who need access.
- Connection failures: A connector authenticates as the maker during authoring but requires re-authentication when invoked for a different user identity in a published channel. Review the connection reference and reconfigure authentication if needed.
- Configuration gaps: A tool or workflow functions in the maker's environment but fails for users in a different configuration, such as a different environment, data region, or licensing tier.
Important
If your organization's tenant policy prevents you from installing the agent or submitting it to the catalog, don't treat the publish action as confirmation that the agent is available to users. Work with your administrator to understand the approval path. Complete channel validation only after the agent is accessible under a representative user account. For autonomous runs, verify activation and connections for the intended user as well.
For more information, see Publish an agent, Available channels, and Share agents with other users and makers.