So now that we've completed our validation testing,
we can move on to provisioning our endpoints using
Intune. Now, with Intune provisioning, we have, again,
a variety of different scenarios that we can support. And in this course, I'm
focusing on the hybrid Azure AD join scenario, mostly because it's probably
one of the most common. Most organizations are there. Organizations are
quickly moving to native Azure AD join, but today it's predominantly hybrid
Azure AD join, so we're going to focus on that. In a hybrid Azure AD join
scenario, the assumption here, of course, is that your devices are joined to
an on‑premises domain, that your computer accounts and user accounts are
synchronized with Azure AD, and that your devices are enrolled for Intune
management.
Now, all of those things are easy to say, but they are not trivial to do.
And unfortunately, during this course, it's not something that we cover.
There are plenty of courses on Pluralsight that cover Intune
management. We'd encourage you to check those out because there's a
lot of things that you have to do to get all of this working and
running, and our module or our course here assumes that all of that
is already in place.
And the last piece is that we assume that you're deploying, at least at
this point, you're deploying your certificates using Active Directory
and Group Policy. So when we create our device configuration profiles in
Intune, these are all of the things that are already assumed to be in
place and configured.
So when we set up our Intune device configuration profiles,
we're going to create two of them.
We're going to create the first one for the user
tunnel or the user‑based connection.
And typically, I will deploy my user settings towards user groups, right?
So I'm going to target the VPN profile for the user
tunnel towards a group of VPN users.
Conversely, for the device‑based connection or the device tunnel,
I'm going to apply the device configuration profile
and target a group of devices.
And once again,
the assumption here is that all of this is already configured, so you should
already have those Active Directory groups synchronized with Azure AD, and everything should be in place, and we're ready to go.