Event banner
Deploy Copilot for Microsoft 365: setup, admin controls, and more
Event Ended
Wednesday, Feb 28, 2024, 08:00 AM PSTEvent details
When it comes to deployment, efficiency is king. See how our setup guide offers you the step-by-step guidance you need to set up Copilot for Microsoft 365, then learn about the admin controls that he...
Heather_Poulsen
Updated Dec 27, 2024
JasonSypkens
Feb 28, 2024Copper Contributor
You mentioned and showed controls (about 7 minutes in) about ensuring people only use Copilot with commercial data protection "whenever they're connected to your organization's network" to update your DNS records.
Do you have any solutions (now, or planned) to address this when users are not connected to the organization's network? With the modern workplace, many people are working remote, and are not always on the corporate network. We need a way to ensure commercial data protection even off our network, as long as they're corporate devices. Without this, a user could think they're using the protected Copilot, and inadvertently send sensitive data to the version without commercial data protection.
Bipin-prakash
Feb 28, 2024Brass Contributor
As long as you are authenticated using your Entra ID, CDP should be in place... https://learn.microsoft.com/en-us/copilot/privacy-and-protections
- JasonSypkensFeb 28, 2024Copper ContributorThe challenge is when you're not authenticated. On a corporate device, if you're not logged in, you end up hitting the version without CDP in place, and the only counter measures that Microsoft has offered require you to be on the corporate network. If you're working from home, these DNS entries would not work.