Hi Eric_VanAelstyn , thanks for replying.
Do we still need the HTTP injections in place for copilot.microsoft.com and bing.com/chat? We don't want our users to have any access to copilot/bing chat unless they are signed in and therefore receive Enterprise Data Protection (previously CDP). The way we did this for CDP was by applying the HTTP headers to these requests.
I appreciate you say to pin the Copilot app or direct them to microsoft.com/copilot, however our users are used to accessing via copilot.microsoft.com and bing.com/chat so are more likely to continue with this regardless of how we advise them.
I also read online that students under age 18 aren't yet eligible for Enterprise Data Protection . Could I enquire how you're identifying whether a user account belongs to a student and if they are under 18.