Rolling out Agent Builder before Copilot Studio: how are you gating access without breaking your Citizen Dev environment?
We want Agent Builder broadly available but Copilot Studio limited to a smaller, trained cohort (possibly long-term). The catch is an existing Citizen Development program running in its own default environment that we don't want to disturb.
Has anyone done this cleanly and consistently? Security groups, environment routing, DLP, licensing. What's worked?
Background: when we gave end users the full PP experience out of the gate, adoption and support became a real burden. Trying not to repeat that.
u/DevelopmentVast819 — 2 days ago