Wes Spencer explains how MSPs can improve security without frustrating users. Start with low-friction controls like requiring managed devices, then layer in stricter policies like Intune compliance enforcement once you've built trust.
I see it all the time where, you know, we're trying to be seen as the hero, not the, you know, the provider that creates a lot of frustration in the organization. And that's why with everything I've tried to create, I've tried to create progression paths. And largely this is what CIS does with the implementation groups. But I think it, you know, we're going to try to break it down in this series in an even more granular layer. A great example of this is saying, "Hey, we want to require, you know, managed devices." A lot of organizations, can fulfill that. There's not much of a gap, if any, to say that we could start fulfilling that today and not create a bunch of friction versus if we said, "We're going to roll out compliance policies with Intune and require that your device is compliant. And if you don't have a compliant device or it falls out of compliance, you won't have access to your data." That actually creates a lot of friction, right? So it's trying to get quick security wins, you know, that won't create that buffer of frustration,
