Thanks Greg_C_Gilbert picking up the distinction.
And TranissaCreme_PMM thanks for that clarification.
I'd strongly recommend that it is set out clearly in a single page in the documentation. I think most people won't note the distinction, or understand implementation.
The only place where the comparison between "Commercial Data Protection" and "Enterprise Data Protection" is clarified is here in your comment - there doesn't appear to be any official documentation with both terms on it.
As a customer, it was already very difficult to read the tea leaves for how CDP worked on its own
- vaguely contradictory statements in different places
- alarming DNS-based implementation
- pieces of information spread between InTune, Windows, Edge, Copilot, Copilot M365 and Purview documentation
Then by adding EDP over the top - I think most people won't even quite realise those are two mechanisms, and when they do, it's hard to understand the differences.
I think it will really help customers if that's all laid out on a single page, for clarity, with a table setting out differences between treatment for
- non-M365 customers
- non-Copilot-for-M365 customers
- M365 customers with CDP DNS hackaround implemented
- M365 customers with EDP implemented (are implementation steps even required?)
with ticks and crosses for what & what doesn't happen in each scenario.
The clarifying what's needed for implementation:
- does EDP require the CDP implementation steps
- if not, what is CDP on its own
- do users need to be told to log in, for it to even take effect
- etc
That would make a world of difference for customers. Thanks for your consideration.