MicrosoftMicrosoftAwesome to see the recommendation on Ingite! :) cu guys there!!
Regarding DFI v3.x.
Its a little misleading with the "1 click deployment" as basically that was the case even in the Standalone. (Downloading and then installing the agent, two click :)).The real "work" with onboarding DFI is configuration such as setting up the GPO's for auditing, the correct 'logon as a service' and 'retriev password' for gMSA account configs (but also nailing those for Entra and CA servers, this is a very common step missed that we have to correct in environments, as its not mentioned in the onboarding guides). I notice in the guide for v3.x those GPO configuration steps are still mentioned, but not all (now im getting my hopes up!) - does that mean we getting closer to a v4.x or even 5.x that does not require the GPO/config part? -cross fingers- , that would be a massive leap in streamlining the onboarding.
Also, i love that we start to see the license requirement - but is there an official statement on how it needs to be covered?
https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#how-can-the-service-be-applied-only-to-users-in-the-tenant-who-are-licensed-for-the-service-3 is not giving much answers, only referring to vaguely formatted "Product Terms" which does not mention DFI specifically and speaks broadly.
Do i need to cover all my accounts in Active Directory (as DFI does look at all objects). Or is it enough for me to just cover those i want to cover? (even if DFI can not limit to licensed users only). (Example: a tenant with 12.000 accounts in Active Directory, they have 2000 E5 licenses. They need to acquire 10.000 additional DFI licenses even if those 10.000 are disabled, not used or even have a PC. But as long as the user object exists in AD, they need coverage - correct?).
Thanks !! greatly appreciated.
