Copilot with Safe Search through DNS CNAME

Good afternoon,

We're looking at implementing Copilot and was looking over the MSFT Learn page.

The Manage section references 'Prevent use of Copilot without commercial data protection: Update your DNS configuration by setting the DNS entry for http://www.bing.com to be a CNAME for nochat.bing.com'

However, within the FAQ section it talks about Copilot working with safe search if you've implemented proxy redirection https://learn.microsoft.com/en-us/copilot/faq#:~:text=If%20my%20company%20blocked%20access%20to%20adult%20content%20by%20implementing%20SafeSearch%20with%20a%20proxy%20redirect%2C%20will%20Copilot%20still%20be%20accessible%20to%20users%20in%20my%20organization%3F . With the subsequent link to https://support.microsoft.com/en-au/topic/blocking-adult-content-with-safesearch-or-blocking-chat-946059ed-992b-46a0-944a-28e8fb8f1814 saying ' If you want to guarantee Chat is turned off for all users on your network plus all users are set to strict SafeSearch, in our router or proxy server map http://www.bing.com to nochatstrict.bing.com.'

We want to block access to Copilot for all unlicensed users and force all licensed users to use Copilot with commerical data protection. We also want to ensure all users have Bing SafeSearch enabled.

If we use DNS to redirect http://www.bing.com to nochatstrict.bing.com, will we achieve our goals? The articles I've referenced don't seem to directly answer the question and the way I'm reading the them, they seem to conflict each other.