3 ms·
Must be disabled here using organizational policies then cause I see nothing of the sort. To be fair, I also did run into something like this with Outlook. With
by perching_aix 1y ago
Must be disabled here using organizational policies then cause I see nothing of the sort. To be fair, I also did run into something like this with Outlook. With that I knew that there were integrations though, so I knew to search for it and could confirm it's disabled. Didn't occur to me to search for this regarding Teams, but it makes sense. Pretty strange though, cause we do have Copilot working in Edge, I use it all the time. And it's not the el cheapo free version.
Closely related, all this session management crap is what drives me personally insane, not the presence of AI. Might again be just the organizational policies making things fall apart though. But my expected experience would be to just log in to Windows, and have Copilot just working everywhere. Not log into Copilot in Edge, log into Copilot in VS Code, log into Copilot in (...). So annoying.
- vel0city 1y agoYeah, my employer seems to have the mindset if we don't bother trying to standardize and enable AI tools people are just going to end up quietly using other tools in more questionable and far less DLP-compliant ways, so you might as well get ahead of it and say if you want to use AI tools here are the allowed ways and tools. Microsoft seems to have pretty good DLP kind of tooling around Copilot. And I do agree, I feel like Microsoft has regressed about linking sessions to your desktop session. If I'm already logged in on the desktop session just auth with that. Instead I have to login to all the various tools. Sure, maybe throw a "Log in with your account?" prompt or something to confirm I want to use it or re-auth a passkey or whatever, but annoying I need to resupply a password. And that's not just some way IT has things configured, same kind of thing on my personal devices.