[EN] Intune (Endpoint Manager) - How to start the implementation and what to pay attention to.
Why I write this article
This guide is create to help other IT pros that are starting with Office 365 / Intune services to help with base configuration of Intune and don’t make the same mistake. Follow this guide you will have global configuration of Intune ready.
Whats is Intune or with new name Endpoint Manager
Intune is a 100% cloud-based mobile device management (MDM) and mobile application management (MAM) provider for your apps and devices. It lets you control features and settings
Devices and Operating System that can be controlled by Intune (Endpoint Manager)
Apple
- Apple iOS 12.0 and later
- Apple iPadOS 13.0 and later
- Mac OS X 10.13 and later
- Android 5.0 and later (including Samsung KNOX Standard 2.4 and higher)
- Android enterprise
Microsoft
- Surface Hub.
- Windows 10 (Home, S, Pro, Education, and Enterprise versions).
- Windows 10 Enterprise 2019 LTSC.
- Windows 10 IoT Enterprise (x86, x64).
- Windows Holographic for Business.
- Windows 10 Teams (Surface Hub).
- Windows 10 1709 (RS3) and later,
- Windows 8.1 RT, PCs running Windows 8.1 (Sustaining mode)
Choosing license
Intune as a part of M365 is added to licensing bundles allowing organization manager whole platform and devices connected.
List of licences bundles that contain Intune (Endpoint Manager) User License.
- Microsoft 365 Bussines Premium
- Microsoft 365 E3 and E5
Extension bundle for Office 365 pack that can be bought separately.
- Enterprise Mobility Suite E3 and E5
Standalone Intune (Endpoint Manager) licences
- User licenses in Microsoft Intune
- Device licenses in Microsoft Intune
Note: Device licenses limits
Limits: Intune app protection policies
Limits: Conditional access
Limits: User-based management features, such as email and calendaring.
Bundle licences are more cost effective and give additional features like Azure AD P1, Azure Information Protection and more…
Example base on price found on Microsoft sites that showing difference on costs:
Type | EMS - E3 | User licenses in Microsoft Intune |
---|---|---|
Cost | 8.80 $ | 8 $ |
Pricing and features of EMS can be found on website: Enterprise Mobility + Security
Note: If your company won't buy bundle license please consider buying Azure Active Directory Premium 1 to enabled "Conditional access features" and auto enrollment to Intune (Endpoint Manager) devices when they join Azure Active Directory
Steps for first configuration
DNS configuration in Office Admin Panel
Note: To perform this task you need to have access to DNS Server.
Step 1: Create DNS entries on DNS Server
Type | Name | Value | TTL |
---|---|---|---|
CANME | EnterpriseEnrollment.CustomDomainName.com | EnterpriseEnrollment.manage.microsoft.com | 3600 |
CANME | EnterpriseRegistration.CustomDomainName.com | EnterpriseRegistration.windows.net | 3600 |
EnterpriseEnrollment - To simplify enrollment, create a domain name server (DNS) alias (CNAME record type) that redirects enrollment requests to Intune servers. Otherwise, users trying to connect to Intune must enter the Intune server name during enrollment.
EnterpriseRegistration- Azure Active Directory has a different CNAME that it uses for device registration for iOS/iPadOS, Android, and Windows devices. Intune conditional access requires devices to be registered, also called “workplace joined”.
Example:
Step 3: Log on to Office 365 admin center by URL: https://admin.microsoft.com
Step 4: On left navigation menu go to: Setup –> Domains
Edit existing Custom Domain Name and follow wizard
Add NEW Custom Domain Name and follow wizard
Azure Active Directory configuration
Step 1: Log on to Azure Active Directory admin center by URL: https://aad.portal.azure.com/
Step 2: On left navigation menu go to “Azure Active Directory”
Step 3: In options navigate to “Mobility (MDM and MAM)”
Step 4: Select “Microsoft Intune”
Step 5: Select “Microsoft Intune configuration MDM and MAM”
Prerequisites
- Azure Active Directory Premium mini Plan 1
- Microsoft Intune subscription
Note: Microsoft 365: Premium, E3, E5 and Enterprise Mobility Suite E3 and E5 contian Azure Active Directory Premium 1
MDM user scope
This section have set of options to configure auto enrollment registered devices to Intune (EndPoint Manager). Auto Enrollment will be run in background task if:
- Users add their work account to their personally owned devices
- Users join corporate-owned devices to Azure Active Directory
- Setup on first (delivery from shop) run Windows 10 organization join is selected
Note: Windows 10: Professional and Enterprise can enroll to Azure Active Directory
None - MDM automatic enrollment disabled
Some - Select the Groups for Azure Active Directory (Synchronized groups from local Active Directory) that can automatically enroll their Windows 10 devices
All - All users can automatically enroll their Windows 10 devices
Note: Pilot implementation limit enrollment to group of users by choosing option "Some"
Note: Azure AD join in hybrid model require additional configuration
Important and when use the same group for MDM and MAM
If both the MAM user scope and the MDM user scope (automatic MDM enrollment) are enabled for all users (or the same groups of users). The device will not be MDM enrolled, and Windows Information Protection (WIP) Policies will be applied if you have configured them.
If your intent is to enable automatic enrollment for Windows BYOD devices to an MDM: configure the MDM user scope to All (or Some, and specify a group) and configure the MAM user scope to None (or Some, and specify a group – ensuring that users are not members of a group targeted by both MDM and MAM user scopes).
For corporate devices, the MDM user scope takes precedence if both MDM and MAM user scopes are enabled. The device will get automatically enrolled in the configured MDM.
What is MAM - Mobile Application Management
Intune (Endpoint Manager) Console
To access Intune (Endpoint Manager) web console you will need support browser (Edge, FireFox, Chrome … not Internet Explorer) and we have 3 options to navigate:
- In web browser typ URL: https://endpoint.microsoft.com/
- Office 365 Admin Center: https://admin.microsoft.com, on left navigation menu choose “Endpoint Manager” and you will be redirected to option 1.
- Portal Azure: https://portal.azure.com in global search field type “Intune” and you will be redirected to option 1.
Tenant Administration - Customization
Step 1: Go to Tenant Administration in Endpoint Manager web console
Step 2: On navigation menu go to “Customizations”
In this section we will configure user experience in “Company Portal” on Web / Mobile or Desktop. In section customization we have options to adjust look up to our company layout. We can also customize settings and display information:
- Organization name
- Theme color
- Support information
- Configuration allowed by “Company Portal”
Note: This is the default customization that's applied to all users and devices. It can be edited, but not deleted
To check how end user see information and customizations go to URL: https://portal.manage.microsoft.com/.
On “Company Portal” End user have access to informatio:
- List of all devices and settings
- Access to application
- Notifications
- HelpDesk contact information
Tenant Administration – Connectors and tokens
Intune (Endpoint Manager) configuration can be extend by integration of with other partners to deliver better business solution and value for end user experience and allow IT pros to setup as secure and protected environment.
Key benefits of those integrations:
- Applications - This integration allow to deliver for example delivre applications directly from partner store, so all updates of this application will be delivre automatically the same way. So end user experience is the same as on personal device.
Partners:- Apple Business Store (Apple VPP Tokens)
- Google Managed Play Store
- Microsoft Business Store
- Certificate connectors - Install on your on-premises server to connect you local “Certificate Authority”, with this integration we can use our own certificates templates on mobile devices and desktop devices that are not connected over any VPN to local datacenter. Certificates will be delivre by Intune.
Why use this integration:
- ADFS authentication with certificates.
- RADIUS / NPS server authentication with certificates.
- Secure access to servers that use oure CA for HTTPS.
- TeamViewer connector - With this connection you user will be prompt in “Company Portal” to allow remote access to devices, no other software is required. With this integration you have remote access to mobile and dekstop devices. For integration follow this article TeamViewer User Guide for Intune
Prerequisites:- Valid TeamViewer account with eligible license. To sign up, please visit: https://login.teamviewer.com
- Intune product license assigned to Intune administrator account.
Enrollment restrictions - who can enroll devices to Intune
Intune (Endpoint Manager) administrator, can create and manage enrollment restrictions that define what devices can enroll into management with Intune with options and lmitations.
- Number of devices.
- Operating systems and versions.
Note: You can create multiple restrictions and apply them to different user groups
Step 1: Go to Devices –> Enrollment restrictions
By default all operating systems are allowed to be enrolled and all types of devices.
- Personal
- Corporated Owned
So IT pros need to change with operationg systems are allowed.
Step 2: Edit: Default Device type restrictions that is assigned for “All devices” and block all types.
Best practice: Action in step
Step 3: Edit: Default Device limit restrictions that is assigned for “All devices” and change to 1.
Best practice: Action in step
Step 4: Create: new Device type restrictions that is assigned for dedicated group of users or devices “All devices” and allow operating system that you will be using in organization.
Best practice: Windows 10 need to have option personal “Allow” even for “Corporate” enrollment, this can be block if organization is using Auto Pilot in other wise enrollment of Windows 10 devices will faild with error 0800***.
Step 5: Create: new Device limit restrictions that is assigned for dedicated group of users or devices “All devices” with allowed number of devices.
Best practice: Number of devices is setup 5
Device clean-up rules - remove devices that are not used any more
Intune (Endpoint Manager) create new device object with new GUID number each enrollment event if is the same devices after wipe after some time organization can have many devices that are
- not used
- stole
- wpied and enroll
- user of devices change
In this scenrios we will have dubel or triple number of devices with the same IMEI or SN. To handle this scenarios we don’t have write PowerShell scripts or do it manually by review IT pros need to Enable auto cleaning rules for devices that did not connect over period of time.
Step 1: Go to Devices –> Device clean-up rules
Step 2: Enable feature and setup number of days for devices taht didn’t checked.
Best practice: set number of days to 90
Next part … Compliance policies and Configuration profiles
-
Compliance policies Policies -
Devices Configuration profiles
Leave a comment