Reducing risk of Bing Chat for Enterprise

Copper Contributor

Hi Everyone


With the release of copilot/Bing chat for enterprise, it has come with some headaches, mainly around the use of the public vs enterprise versions of Bing chat for Enterprise


I have researched as much as I can and tested just about everything I can, but I cannot find any way of enforcing the combination of Bing Chat for Enterprise with protection, or not allowing users to use Bing chat at all, but it seems this cannot be done, due to a combination of how Microsoft host and operate the service as well as other third party browsers not enforcing sso using the windows account signed in (Chrome admx does not work either)


Is Microsoft developing any tools or ways to enforce the use of protected work accounts and not allowing the use of any public or unlicensed versions (personal Microsoft accounts)?

I see even the DNS cname records workaround does not even work anymore either.


I am curious to know how others are managing this in their organisation without resorting to extreme measures such as forcing a large organisation over to Edge immediately or straight up blocking the use of Bing chat entirely?

1 Reply

Hi @Brent_Prince,


This solution might not be a perfect fit for you, but it could spark some ideas.

In Microsoft Edge, I alternate between my professional and personal profiles by logging in with the corresponding accounts.





This way, my activities are protected when using a work account, while a personal account offers no restrictions.

Work account:



Personal account:



Moreover, both profiles can be conveniently pinned to the taskbar in Windows 11.



However, like any significant modification, it’s important to implement change management with users.


Kind regards,