Forum Discussion
Copilot Query History + Standalone Copilot
- 11 months ago
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.
LeifB If I am reading this correctly, it should retain its setting since they say that if you don't want it to enable it and then disable it, implying that it saves the state if you have specifically set it. Standalone Copilot in Power BI will be turned on by default in September | Microsoft Power BI Blog | Microsoft Power BI
But, I would double check it on Sept 7th and 8th if it were myself.