Forum Discussion
Copilot Query History + Standalone Copilot
Hi LeifB,
Great follow-up, thanks for clarifying.
The key detail is that the September 5 rollout only flips the setting on by default for the whole tenant if it’s not already explicitly managed. If you turn it on, then off before that date, your tenant is considered “opted out,” so Microsoft will not override your choice.
After that, you are free to turn it back on for specific security groups whenever you are ready. In that case, it will respect the group-scoped configuration you apply it won’t force it tenant-wide just because you toggled it back on.
You do not need to keep it “off” until after rollout. Once you have opted out, you can safely re-enable it for a limited security group, and that setting will stick.
For reference, here’s the Microsoft announcement that explains how the automatic enablement works and how opting out preserves your settings:
https://powerbi.microsoft.com/en-us/blog/the-standalone-copilot-in-power-bi-will-be-turned-on-by-default-in-september/Hope this clears things up. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.
Thank you for using the Microsoft Community Forum.
Thanks for the detailed response. We already have reporting on report usage; it sounds like we'll need to work with our M365 admin to get that separate usage report set up.
Regarding Standalone Copilot, if we turn it on, off, and then back on but set to just one security group, will this maintain the setting before the rollout? Or do we need to leave it off until the rollout?
Hi LeifB,
Great follow-up, thanks for clarifying.
The key detail is that the September 5 rollout only flips the setting on by default for the whole tenant if it’s not already explicitly managed. If you turn it on, then off before that date, your tenant is considered “opted out,” so Microsoft will not override your choice.
After that, you are free to turn it back on for specific security groups whenever you are ready. In that case, it will respect the group-scoped configuration you apply it won’t force it tenant-wide just because you toggled it back on.
You do not need to keep it “off” until after rollout. Once you have opted out, you can safely re-enable it for a limited security group, and that setting will stick.
For reference, here’s the Microsoft announcement that explains how the automatic enablement works and how opting out preserves your settings:
https://powerbi.microsoft.com/en-us/blog/the-standalone-copilot-in-power-bi-will-be-turned-on-by-default-in-september/
Hope this clears things up. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.
Thank you for using the Microsoft Community Forum.
Hi LeifB,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.Thank you.
Hi LeifB,
Hope you had a chance to try out the solution shared earlier. Let us know if anything needs further clarification or if there's an update from your side always here to help.Thank you.