How Microsoft Purview DLP currently can help you protect confidential data in Copilot.

Organizations today face a difficult balancing act. Business leaders are eager to adopt tools like Microsoft Copilot to unlock productivity and innovation. Meanwhile, IT and security teams are concerned about safeguarding sensitive information, especially as AI-driven features process vast amounts of organizational data. This tension is real: enabling advanced capabilities without compromising compliance or data protection is a challenge every modern enterprise must solve. Microsoft Purview Data Loss Prevention (DLP) is a key solution to this problem. It provides mechanisms to prevent confidential data from being exposed or misused, even in scenarios involving AI. I want to highlight two features designed to help organizations in controlling what is being processed by Copilot. Blocking Documents Based on Sensitivity Labels One of the foundational features of Purview DLP is its ability to enforce policies based on Microsoft Information Protection sensitivity labels. If your organization...

Copilot Pay-As-You-Go has been made easier

Microsoft has begun rolling out a change that simplifies how organizations set up Pay-as-you-go billing for Microsoft Copilot Chat and Agent. Starting in October, 2025, all new Pay-AsYou-Go configurations can and should be done through the Microsoft 365 admin center, as the previous method via the Power Platform admin center is being phased out. 

This shift not only streamlines billing management but also makes it easier for admins to get started without needing a Copilot license. 

If your organization is planning to set up new billing plans, now’s the time to make sure your team is familiar with the updated process. Everything you need to know is documented at Microsoft Learn.

Here is a short summary for your convenience:

To enable pay-as-you-go billing for Microsoft 365 Copilot, an admin with the right roles (Global, Billing, or AI Admin) must first create a billing policy. This involves linking an Azure subscription and resource group, selecting a region, and defining the user scope. Optional: You can set a budget to trigger alerts but it will not cap spending.

Once the policy is created, connect it to the desired service: Copilot Chat or SharePoint agents. Policies can be disconnected or deleted at any time. 

Important: If Power Platform billing policies exist, they can coexist, though unified management is recommended.