A maker adds a Twitter/X connector action inside a cloud flow used by a Copilot Studio agent. Saving the flow fails after a tenant DLP policy update. SharePoint remains usable in other flows. What is the most likely DLP-related explanation?
Select an answer to reveal the explanation.
Short Explanation
DLP is the workplace rule that says don't pour customer files into public social networks. If Twitter/X is blocked or non-business while SharePoint is business, mixing them in one flow gets the red stamp.
Full Explanation
Power Platform data loss prevention (DLP) policies classify connectors into Business, Non-business, and Blocked groups. Flows cannot mix Business with Non-business connectors, and blocked connectors cannot be used. The explanation that the DLP policy blocks the Twitter/X connector or prevents combining it with Business-group connectors in the same flow is correct because a new DLP classification that blocks Twitter/X or places it in a conflicting group with other connectors in the flow explains save or runtime enforcement failures while SharePoint-only flows still work. The claim that DLP policies only apply to canvas apps and never evaluate Power Automate flows called by Copilot Studio is wrong because DLP applies to flows and impacts agents that depend on those flows. The claim that DLP always requires that Twitter/X be paired with SharePoint in the same flow to be allowed is wrong; DLP does not require social plus SharePoint pairing. The claim that Copilot Studio automatically exempts all social connectors from tenant DLP for agents is wrong; agents are not exempt from tenant DLP. Exam tip: When a connector suddenly disappears or a flow won't save after governance changes, check DLP connector groups first.