{"id":4595,"date":"2025-04-17T12:43:41","date_gmt":"2025-04-17T12:43:41","guid":{"rendered":"https:\/\/davidpapkin.net\/?page_id=4595"},"modified":"2025-04-17T12:43:41","modified_gmt":"2025-04-17T12:43:41","slug":"microsoft-md-102-microsoft-365-endpoint-administrator","status":"publish","type":"page","link":"https:\/\/davidpapkin.com\/?page_id=4595","title":{"rendered":"Microsoft MD-102 Microsoft-365-Endpoint-Administrator by David Papkin"},"content":{"rendered":"\n

This David Mark Papkin page has course info on Microsoft MD-102 Endpoint Administrator<\/p>\n

Microsoft 365 Endpoint Administrator Courseware<\/a><\/p>\n

 <\/p>\n

Deployment<\/strong><\/p>\n

\"Generated<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Feature \/ Aspect<\/th>\nMicrosoft Deployment Workbench (MDT)<\/strong><\/th>\nWindows Autopilot<\/strong><\/th>\n<\/tr>\n<\/thead>\n
Deployment Type<\/strong><\/td>\nTraditional, image-based<\/td>\nModern, cloud-based<\/td>\n<\/tr>\n
Target Environment<\/strong><\/td>\nOn-premises (LAN)<\/td>\nCloud-native or hybrid<\/td>\n<\/tr>\n
Infrastructure Required<\/strong><\/td>\nRequires servers (WDS, MDT, file shares, possibly AD)<\/td>\nRequires Azure AD + Intune (Microsoft Endpoint Manager)<\/td>\n<\/tr>\n
Use Case<\/strong><\/td>\nCustom imaging, task sequences, heavy customization<\/td>\nProvisioning new devices with minimal IT interaction<\/td>\n<\/tr>\n
Network Dependency<\/strong><\/td>\nLocal network-dependent<\/td>\nInternet-capable (anywhere deployment)<\/td>\n<\/tr>\n
User Interaction<\/strong><\/td>\nTypically technician-driven (manual PXE boot or USB)<\/td>\nUser-driven, guided out-of-box experience (OOBE)<\/td>\n<\/tr>\n
Integration<\/strong><\/td>\nWorks with SCCM\/ConfigMgr<\/td>\nDeep integration with Azure AD, Intune, and Microsoft Store<\/td>\n<\/tr>\n
Customization Level<\/strong><\/td>\nHigh: scripting, app packages, GPOs, driver injection, etc.<\/td>\nModerate: profiles and policies set via Intune<\/td>\n<\/tr>\n
Ideal For<\/strong><\/td>\nRe-imaging existing hardware, complex deployments<\/td>\nProvisioning new devices from OEMs or zero-touch scenarios<\/td>\n<\/tr>\n
Device Ownership<\/strong><\/td>\nOften corporate-owned and fully managed<\/td>\nSupports corporate-owned, BYOD, and hybrid scenarios<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n

GitHub<\/a><\/p>\n

Intune Policies<\/strong><\/span><\/p>\n

1. Configuration Policies<\/strong><\/p>\n

Used to configure device settings<\/strong> (security, Wi-Fi, VPN, email, compliance baselines, etc.).<\/p>\n

Often include OMA-URI custom settings<\/strong> for advanced or unsupported configurations.<\/p>\n

Goal: ensure devices meet organizational setup requirements.<\/p>\n

2. Device Compliance Policies<\/strong><\/p>\n

Define rules a device must meet<\/strong> to be considered compliant (e.g., PIN required, encryption enabled, OS version).<\/p>\n

Devices that fail compliance can be blocked from accessing company resources.<\/p>\n

Typically paired with Conditional Access<\/strong>.<\/p>\n

3. Conditional Access Policies<\/strong><\/p>\n

Control user and device access to corporate resources<\/strong> (Office 365, company apps, VPN).<\/p>\n

Works with Azure AD and compliance results.<\/p>\n

Example: Only allow access if the device is compliant and<\/strong> the user passes MFA.<\/p>\n

4. Corporate Device Enrollment Policies<\/strong><\/p>\n

Define rules for enrolling corporate devices<\/strong> into Intune.<\/p>\n

Help ensure only authorized devices\/users can enroll.<\/p>\n

Can enforce automatic enrollment for Azure AD-joined devices.<\/p>\n

OMA-URI<\/strong> <\/span>stands for Open Mobile Alliance Uniform Resource Identifier<\/strong>.
It\u2019s a standardized way to reference and configure device settings through Mobile Device Management (MDM) systems like Microsoft Intune<\/strong>.
How it works:<\/p>\n