Skip to main content

Deploying and publishing

The generated flow lives in your folder. Two steps make it usable from a real bot: deploy it to Production, and publish a Trigger that maps natural-language requests to the flow.

Make the flow top-level​

Only top-level flows can be attached to triggers. Open the flow's settings with the pencil icon next to its name and set Is Top-Level Flow? to Yes (a WorkSpace assignment appears); then Update. If you skip this, the flow will not appear in the trigger's flow list.

Edit Flow drawer with Label "Add User to Security Group", Is Top-Level Flow? set to Yes, Expose to Ticketing? No, and a WorkSpace picker

Deploy​

Click Deploy Flow in the editor toolbar. Creator Studio saves all components, publishes them to Production, and confirms with a deployment report. If a previous version already exists in Production, choose Overwrite to replace it. Re-deploy after any change you want live - including the top-level setting above.

Deployment Successful screen confirming the flow has been deployed to Production, with Close and Go To Production Folder buttons

Create and publish a trigger​

Triggers map natural-language requests to your flow. Open Manage Triggers from the Creator Studio header to see every trigger, its sample queries, and its status.

Triggers page listing several published triggers with their associated flows, trigger names, sample queries, flow descriptions, created-on dates, and status badges

Click Create Trigger and fill the form:

  1. Associate Flow - pick your flow. Only deployed, top-level flows are listed.
  2. Trigger Name - a short label, e.g. Add User to Security Group.
  3. Flow Description - one or two sentences the intent engine uses to understand what the flow does.
  4. Sample Queries - three or more phrases users would actually type ("i need to add a user to a security group", "add someone to an entra security group"…). Remove any empty rows; blank queries block publishing.
  5. Audience - optionally restrict who can use the trigger.

Create Trigger form filled out with the Associate Flow, Trigger Name, Flow Description, three Sample Queries, and Audience permit dropdown

Click Publish Trigger. Publishing is asynchronous - a request ID is shown while it processes, and the list may show Draft until you refresh the page, after which the trigger shows Published.

Triggers list after refresh, with the new trigger row showing the Published status badge

What's next​

With the flow deployed and the trigger published, you are ready to test the whole experience in Microsoft Teams.