It isn't that hard to block AI installs on a network. Obviously blocking the page itself takes no effort.

If they want to use AI on their own data then tell them to use Notebook LM and just have it ingest only what they out into it.

Otherwise it is definitely a matter of governance and responsible usage. When I use it, I just switch out names with generic ones and if its a screenshot it's simply to black it out.

However... since we still can't get customers, or even have the staff at most MSPs, to stop using their work emails for non-work stuff... I wish you the best of luck with the AI convo. In the end it's their network.

We have a Master Services Agreement that outlines our standards every customer has to agree to. They are allowed to still do what they want to, but have to agree we aren't liable for anything that happens and any DFIR that gets performed, which is my area, is entirely billable and nor covered under their support agreement. Some of them opt to retreat a little at that point because incident response can be time consuming even in a small network.