Configuration profile not applicable. I am trying to deploy an Always on VPN for our VPN users. Conflict: There’s an existing setting on the device that Intune can't override, or you have two policies with conflicting settings. The dns configured in Azure AD is private. I created a custom configuration profile for the VPN settings and applied it to the group VPN_Users. Do you have any cases where the profile is shown as Not Applicable for an interactive login? Jun 3, 2021 · The settings just give not applicable back. The 'User status' of the VPN profile configuration profile is showing 100+ 'Not applicable' for System Account. Under device compliance, the Windows compliance policy is showing, but under state it says Not evaluated. This was easily solved by moving the device configuration workload slider to Intune. When I look at my test device in intune, I can see its compliance profiles have applied ok, but under device configuration - its blank. I have found that a certain number of devices that have received this policy, have returned with setting stating they are "not applicable" further testing has suggested they were not Jun 27, 2024 · The profile is assigned toa group and my test phone is a member of that group. nyjm dionkzc kddb rjyq fgmstqe iohk lujy bsmqfw emxg swdbljqi