“Bring your AI to work” is here: Microsoft edition - What Multiple Account Access to Copilot means

on
Multiple Account Access to Copilot On October 1. 2025 Microsoft released a blog post explaining how employees now can use Copilot from their personal 365 plans to work on organizational data. This is of course, an extension of the already existing "Multi account" feature that was released for corporate accounts a "couple of months" ago. In other words, “bring your own Copilot” is now a real thing in Word, Excel, PowerPoint, Outlook, and OneNote on desktop and mobile, with enterprise protections intact. “Bring your AI to work” is an important topic, and banning AI altogether might not be the answer. Whether sanctioned or shadow, AI has already entered everyday knowledge work. Microsoft’s new multi‑account access offers a safer path where employees can use Copilot from their personal Microsoft 365 subscriptions on work files, while the file’s access, auditing, and compliance still flow through the work identity and tenant. That’s better than users copy‑pasting sensit...

Regaining Control Over Unmanaged GenAI Apps: New Microsoft Purview Enhancements in Edge

on

Many organizations are growing increasingly concerned about the widespread use of unsanctioned Generative AI (GenAI) tools. These apps, often accessed through unmanaged browsers, pose significant risks to data security and compliance. To help with this, Microsoft is now updating some features in  Microsoft Purview that will enhance policy enforcement for unmanaged cloud apps accessed via the Edge browser. 

What’s Changing?

Previously, enforcing Purview Data Loss Prevention (DLP) and Collection policies required manual creation of Edge configuration policies. These policies were often complex and needed to be scoped correctly to block unsupported browsers or apply protections. With this update, Microsoft automates much of that process:

  • Collection Policies now apply directly within Edge without needing a separate blocking configuration.
  • DLP Policies automatically generate Edge configuration policies that align with the scope of the DLP rules.

DLP policies can operate in two modes:

  • Audit Mode: Policies are logged, but browser blocking is optional.
  • Block Mode: Enforces browser blocking based on policy scope.

In order to implement the new feature when they are enabled, organizations should review existing Edge configuration policies. If there are manually scoped policies, you should consider disabling or deleting them.

Update your Purview DLP policies to trigger the new automated behavior. You car read the step by step guide from Microsoft Learn here.

This update is associated with Microsoft 365 Roadmap ID 486368. It is available in preview, but will hopefully be rolling out later this fall.

If you found this update helpful, consider subscribing to my blog or following me on LinkedIn for more insights and practical guidance on Microsoft 365 and enterprise IT.