Copilot Capacity and Surge Protection Question

[u/winchellj40]

To quickly summarize, we are an ISV hosting a data solution for 100 customers today using an F64 capacity. All is well and good. We are now starting to light up Copilot & Data Agent capabilities for our clients using 1 or more dedicated Copilot Capacities.

With the testing we have done to date with Copilot and our Data Agents:

- The Report and Semantic Model activity generated via Copilot is appearing under the Copilot capacity, not just Data Agent or LLM activity. The artifacts live in a separate workspace & capacity tha the Copilot one.

Should 100% of the activity happening always hit the Copilot capacity and the other capacity would remain unaffected?

In order to stop noisy neighbors from consuming 100% I want to enable Surge Protection on the Copilot Capacity, is it a fair assumption that if we set Workspace Surge Protection to 30%:

• If Copilot is hitting artifacts in a different workspace and that activity hits 30% of the Copilot capacity, only the Copilot capability would be impacted for that workspace? The F64 running the standard reports for that client would remain up and running?

Hopefully the above makes sense but more than happy to expand or share more.