For step by step guidance please refer to the NHS.net Intune Operations Guide used to support Intune Local Administrators (Intune LAs) and Onboarding Managers to implement Intune as an MDM solution within their organisation for corporate fully managed iOS/iPadOS, Android, Windows10/11 and HoloLens 2 devices.
For an overview of Intune please refer to Intune Overview Article.
To register your interest for onboarding to NHS.net Intune, please nominate a PLA/LA from your organisation to complete the Intune Registration Form.
Register for IntunePreparation
Enrolment Prerequisites
Licensing – As part of the new licensing agreement with Microsoft, Enhanced organisations now have access to NHSmail Intune as a standard offering.
Devices & users – Devices meet minimum platform requirements:
- Android – 10+
- Apple – 16+
Support – All onboarding requests , service requests, and Level 3 incidents will need to be raised as tickets via Helpdesk Self-Service (HSS) on the NHS.net Portal.
Custom configuration requests – Most configuration in Intune is self serve, however all onboarded organisations are able to request for custom configuration where necessary. To request this, organisations will need to raise a service request via Helpdesk Self-Service.
Service Responsibilities – Intune LAs are responsible for the enrolment, unenrolment and the management of all devices. Please refer to section 3.6 in the NHSMail Intune Operations Guide.
Terms of reference (add link)
Offboarding from Intune existing MDM in the source tenant
Organisations currently using Intune or other MDM in their legacy environment will need to offboard from their existing Intune setup and onboard into the NHS.net tenant. Please refer to section 16 of the Intune Operations Guide .
Onboarding to Intune
To start the onboarding process, please register for Intune using the link above.
Migration Steps
- Register for Intune: Fill out registration form above
- Inventory Devices and Policies: Start documenting the existing devices, configurations, and Intune policies in the source tenant.
- Plan for Migration: Identify which policies, apps, and configurations need to be recreated in the target tenant.
- Export Policies and Configurations (only for existing Intune Orgs): Manually export policies, compliance settings, and app configurations from the source tenant. Intune does not currently support automatic migration of these settings.
- Communicate with Users: Inform users about potential downtime and provide instructions for re-enrolling devices.
- Set Up Target Tenant Recreate policies, apps, and configurations in the new NHS.net tenant to mirror the source tenant. Assign user groups and ensure permissions align with the organisation’s requirements.
- Unenroll Devices: Devices need to be removed from the source tenant MDM or Intune service.
- Re-enroll in Target Tenant: Provide users with a step-by-step guide to enroll their devices into the NHS.net tenant using the Company Portal app or another enrollment method. Ensure users back up their data before unenrolling, as some settings or apps might need to be reconfigured.
- Validation and Testing: Test a pilot group of devices in the new tenant to confirm successful enrollment and policy application. Monitor for any issues and make necessary adjustments before rolling out to all users.
- Post-Migration Monitoring: Monitor compliance and device health in the target tenant. Ensure all devices meet compliance requirements in the NHS.net tenant. Test functionality by validating apps, emails and other configurations are functioning as expected.