# Active Directory to Microsoft Entra ID and Intune

We move identity and device management to the cloud: Microsoft Entra ID instead of (or alongside) Active Directory, device management with Intune and zero-touch laptop setup with Windows Autopilot – no server in the office.

- **Options:** Cloud-only or hybrid
- **Devices:** Intune, Autopilot
- **Security:** MFA, conditional access
- **Outcome:** Laptops set up without an IT visit

## Hybrid or cloud-only?

- **Cloud-only**: When no on-premises apps still need a domain. No office server required.
- **Hybrid**: When local systems remain – AD and Entra ID work together while you move in stages.

- ✓ Assessment of AD, group policies and applications
- ✓ Entra ID configuration, MFA and conditional access
- ✓ Intune policies: security, updates, apps
- ✓ Windows Autopilot for new devices
- ✓ Staged device moves and user support
- …and more (not an exhaustive list)

## How we work

1. **Assessment**: AD, group policies, apps that still need the domain, and device condition.
2. **Design**: Cloud-only or hybrid, Intune policies, MFA and conditional access.
3. **Pilot group**: A few users and devices move first so we can check everything works.
4. **Staged move**: Group by group with user support; the old AD is retired once no longer needed.

## What you get

- **Users in Entra ID**: One secure sign-in to Microsoft 365 and connected apps.
- **Devices in Intune**: Security, update and app policies on every computer.
- **Windows Autopilot**: A new laptop sets itself up – your employee just switches it on.
- **A security baseline**: MFA, conditional access and BitLocker encryption.

## Indicative timeline

| Phase | Duration |
|---|---|
| Assessment and design | 1–2 weeks |
| Entra ID and Intune setup | 1–2 weeks |
| Pilot group | 1–2 weeks |
| Staged move | 2–6 weeks, depending on the number of devices |

Durations are indicative – you get an exact plan and dates in the proposal, after we have assessed your environment.

## What we need from you

To keep things moving, please have ready:

- admin access to Active Directory and Microsoft 365;
- a list of applications that still need the domain;
- Microsoft 365 licences that include Intune (e.g. Business Premium) – or we help you choose;
- a device list and which devices are due for replacement soon;
- users for the pilot group.

## A typical project: an office server kept only for users

**Situation.** The company kept an office server almost only for Active Directory and files. New laptops were set up by hand, and remote staff sometimes couldn’t sign in.

**What we do.** We moved files to SharePoint and users to Entra ID, enrolled computers in Intune, enabled MFA and conditional access, and set up Autopilot for new devices.

**Result.** The office server is no longer needed, new laptops ship straight to staff and configure themselves, and security policies apply to every device.

A composite example based on our most common projects.

**Do all computers need reinstalling?**

Not always. Devices can often be moved in stages; sometimes a fresh Autopilot setup is easier.

**Can we get rid of the office server?**

Yes, if no applications still require the domain. We check this in the first phase.

**Which licences do we need?**

Intune and conditional access are included in Microsoft 365 Business Premium and higher plans. We review your licences and suggest the best fit.

**Will our people have to change much?**

Not much: they sign in with the same Microsoft 365 account, and we explain the changes in a short guide. The pilot group catches any friction early.

- [Microsoft 365](https://ithink.lt/en/microsoft-365-administration/)
- [To Azure](https://ithink.lt/en/cloud-migration/azure/)
- [Endpoint protection & patching](https://ithink.lt/en/it-security/centralized-computer-protection/)

---
Source: https://ithink.lt/en/cloud-migration/entra-id-intune/
