Hen David We were also in the proces to include DKE for some specific and highly confidential (GDPR) content.
Missing a clear direction makes it extremely hard to invest, specifically and because we use the guiding principle to not start/ invest in the deployment of software/ components that are already in 'maintenance'.
We are at the turning point and need clarification/ guidance/ directions within the next month, specifically, because we assumed DKE is soon supported by the build-in Office clients, based on the following two articles:
Through the Microsoft Purview documentation, we get mixed signals and need clarification on the 2 articles'
- The article https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-aip?view=o365-worldwide#feature-parity-for-built-in-labeling-and-the-aip-add-in-for-office-apps
It states; 'Double key encryption' 'In planning or development'. AllAIP add-in feature or capability that have this Built-in labeling description have a Microsoft 365 Roadmap planning, not DKE.
Question; Please clarify, is it under 'review' or 'in planning or development'? In the latter case, why is it not on the Microsoft 365 Roadmap?
- The article https://docs.microsoft.com/en-us/microsoft-365/compliance/double-key-encryption?view=o365-worldwide
Almost at the end of this article it states:
Enable DKE in your client
If you're an Office Insider, DKE is enabled for you. Otherwise, enable DKE for your client by adding the following registry keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSIPC\flighting]
"DoubleKeyProtection"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSIPC\flighting]
"DoubleKeyProtection"=dword:00000001
Question; Please clarif, is DKE already part of the Office Insider 'build-in client' or does this refer to something completely different?