<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Purview on dp666</title><link>https://dp666.net/tags/purview/</link><description>Recent content in Purview on dp666</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Daniel Petri</copyright><lastBuildDate>Fri, 24 Apr 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://dp666.net/tags/purview/index.xml" rel="self" type="application/rss+xml"/><item><title>Copilot readiness starts with permissions, not licenses</title><link>https://dp666.net/blog/copilot-readiness-permissions-not-licenses/</link><pubDate>Fri, 24 Apr 2026 10:00:00 +0200</pubDate><guid>https://dp666.net/blog/copilot-readiness-permissions-not-licenses/</guid><description>Copilot readiness is not a license assignment problem. It is an access boundary problem. If the tenant already overshares, Copilot only makes the blast radius easier to query.
That is the part that gets lost in adoption decks.
A Copilot license enables the experience. It does not make SharePoint clean. It does not remove broad sharing links. It does not review stale guests. It does not make an app registration less terrifying.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://dp666.net/blog/copilot-readiness-permissions-not-licenses/cover.png"/></item></channel></rss>