Skip to content
Back to overview Illustration: laptops, tablets and smartphones receive configuration from a central management hub, a path with milestones runs through the scene
Intune Endpoint Management Works Council

Rolling out Intune: project phases, effort, works council and common pitfalls

By , Security & Cloud Operations 9 min read

Key takeaways

  • An Intune rollout is an organisational project first: device inventory, ownership, apps and responsibilities need to be clear before the first policy is created.
  • The enrolment strategy determines the day-to-day effort: Windows Autopilot and Apple Automated Device Enrollment for company devices, a work profile or app protection policies alone for personal devices.
  • In Germany, you should expect the works council to have a co-determination right over Intune under § 87(1) no. 6 of the Works Constitution Act (BetrVG). If you have a works council, involve it before the pilot, not after.
  • Compliance policies only take effect in combination with Conditional Access. That link is the security-relevant part of the project and needs a careful pilot.

Microsoft Intune is already included in many licences, such as Microsoft 365 Business Premium and Microsoft 365 E3. Even so, many mid-sized companies still manage their devices through Group Policy, images and manual work, or not at all. For management this is a question of evidence: without central management you cannot show that every laptop is encrypted, up to date and running an endpoint protection product. We roll out Intune in customer environments and then operate it day to day. This article describes the approach that has worked for us and the points where projects typically stall.

What needs to be settled before the first device?

Inventory

Start with an honest inventory: which devices exist (Windows, macOS, iPhone, Android), who owns them, how Windows devices are joined today (local only, on-premises domain, already in Microsoft Entra ID), and which applications people actually need. The app list is almost always underestimated. Every line-of-business application that does not come from the Microsoft Store or as a ready-made package has to be packaged, tested and given a detection rule.

Also settle responsibilities. If an external IT provider looks after the devices, the contract should state who may change policies and who approves exceptions.

Licensing

Microsoft 365 Business Premium includes Intune Plan 1 and Microsoft Entra ID P1; Microsoft 365 E3 also includes Intune Plan 1. Entra ID P1 is not optional: according to Microsoft, you need it as soon as compliance rules are to be enforced through Conditional Access. Since July 2026, Microsoft has been gradually adding former Intune Suite capabilities to the enterprise plans: Microsoft 365 E3 gains Intune Plan 2, Remote Help and Advanced Analytics among others, and Microsoft 365 E5 additionally gains Endpoint Privilege Management and Microsoft Cloud PKI. Microsoft announces the change in the Microsoft 365 admin center 30 days in advance. Check what your tenant already has before buying add-on licences.

Which enrolment strategy suits which device?

Enrolment is the process of bringing a device under management. The method determines how much control you have over the device and how much manual work each new device costs.

Device typeRecommended methodWhat you manage
Company Windows laptopWindows Autopilot, Microsoft Entra joinThe whole device
Company-owned iPhone, iPad, MacApple Business (formerly Apple Business Manager) with Automated Device EnrollmentThe whole device, supervised
Personal Android phoneAndroid Enterprise, work profile for personally owned devicesThe work profile only
Personal iPhoneAccount-driven User Enrollment or app protection policies onlyWork partition or company apps only

For Windows there are two variants. Classic Windows Autopilot requires the reseller or IT to register devices in advance and supports Microsoft Entra hybrid join, pre-provisioning and self-deploying mode in addition to Entra join. Windows Autopilot device preparation is the newer architecture: no pre-registration, near real-time progress, but Entra join only, Windows 11 only, and up to 25 apps during initial setup. For companies without legacy domain dependencies, we recommend pure Entra join. Hybrid join prolongs the dependency on on-premises Active Directory and is the most common cause of sign-in problems that are hard to diagnose.

For personal devices, you often need less than enrolment. App protection policies (MAM, mobile application management) protect company data in Outlook, Teams and OneDrive without managing the device itself. Many employees find this more acceptable, and it avoids debates about private data.

What are the project phases?

  1. Baseline configuration: Apple MDM push certificate (must be renewed every year), connection to Apple Business and Managed Google Play, roles and scope tags in the Intune admin center, a naming convention for groups and policies.
  2. Security baselines: Under Endpoint security > Security baselines, Microsoft provides preconfigured settings for Windows, Microsoft Edge and Defender for Endpoint. Do not adopt them blindly. Compare them with your existing Group Policy and document every deliberate deviation.
  3. Compliance and Conditional Access: Compliance policies define what a healthy device is, for example BitLocker on, a minimum OS version, a Defender risk level. They only take effect once a Conditional Access policy requires a compliant device for access. In the Intune admin center, under Endpoint security > Device compliance > Compliance policy settings, set “Mark devices with no compliance policy assigned as” to Not compliant. The default is “Compliant”, which means any device without a policy is treated as fine.
  4. Apps: Microsoft 365 Apps, browser, line-of-business applications as Win32 packages. Every app needs a detection rule and a test on a freshly provisioned device.
  5. Pilot: A small group from IT, one business department and at least one manager. We recommend running Conditional Access in report-only mode first and reviewing the sign-in logs before you enforce.
  6. Rollout: In waves by department or site, with a named contact and a fixed date from which unmanaged devices lose access.

What drives the effort? Not so much the number of devices as the number of variants. Every additional platform, every line-of-business app without a ready-made installer, every department with special rules and every device that has to stay hybrid-joined adds testing and coordination. A company with many identical Windows laptops and a few standard apps finishes sooner than one with fewer devices but three platforms and many specialist applications.

What does the rollout mean for the works council and data protection?

For readers in Germany: § 87(1) no. 6 BetrVG gives the works council (Betriebsrat) a right of co-determination over “the introduction and use of technical devices designed to monitor the behaviour or performance of employees”. German labour courts interpret this broadly: what usually matters is whether a system is objectively capable of monitoring behaviour or performance, not whether that is the intention. Intune records device data, installed apps and check-in times, so you should expect co-determination to apply. The legal assessment of your specific case belongs with your legal advisers, not in an IT project.

In practice it has worked well to involve the works council before the pilot and to prepare a works agreement that settles three points in concrete terms: which data is collected, who may view it, and what it will not be used for. Microsoft publicly documents what an organisation can see on managed devices. Call history, browsing history, personal email, photos and document contents are not part of it. On personal devices the organisation only sees managed apps, and it cannot see the location of a personal device. That page works well as an annex for the works council and staff.

Under the Datenschutz-Grundverordnung (GDPR), Intune and the connected services belong in your record of processing activities under Art. 30 GDPR. Check with your data protection officer whether a data protection impact assessment under Art. 35 GDPR is needed, and use roles in the Intune admin center to limit read access to the people who need it.

What changes for employees?

New laptops ship straight from the reseller, employees sign in with their work account, and the device sets itself up. Updates arrive in controlled rings, and apps are available for installation in the Company Portal. What people notice most is access control: anyone trying to open Outlook or SharePoint on an unmanaged or non-compliant device is blocked or limited to the browser. Announce this in good time and explain why. In our operational experience, acceptance problems are rarely about the technology and more often about a block nobody knew was coming.

Which pitfalls most often delay Intune projects?

  • An incomplete app list. The specialist application used by only two people surfaces during rollout, not during planning.
  • Hybrid join out of habit. Many projects carry over the existing domain model even though the applications have long since moved to the cloud.
  • Group Policy and Intune at the same time. If both set the same setting, it is hard to tell which value applies.
  • Compliance without Conditional Access, or Conditional Access without a pilot. In the first case the policy protects nothing; in the second it locks out the managing director. Our article on rolling out Conditional Access without lockouts describes a step-by-step approach.
  • An expired Apple push certificate. If it expires, every Apple device loses its connection to management. A calendar entry with a named deputy prevents this.
  • Involving the works council too late. A pilot stopped for lack of approval costs more time than any technical problem.

Next step

Our endpoint security services cover the Intune project from inventory to rollout, including a works agreement template and pilot. We implement the link to Conditional Access together with our Conditional Access service. Afterwards you can take over operations yourself or hand them to us.

Book an introductory call

Frequently asked questions

Do we need an additional licence for Intune?

Usually not. Microsoft 365 Business Premium, Microsoft 365 E3 and E5 include Intune Plan 1. Enforcement through Conditional Access also requires Microsoft Entra ID P1, which these plans include. Add-on licences only become relevant for capabilities such as Endpoint Privilege Management or Cloud PKI, unless you use Microsoft 365 E5.

Do existing Windows devices have to be reinstalled?

Not necessarily. Existing devices can be brought into Intune without reinstalling them. For a clean switch from hybrid join to Entra join, a reset is usually the more reliable route. Many companies combine it with their regular hardware refresh.

Can we include personal smartphones without managing them?

Yes. App protection policies protect company data in Outlook, Teams and other supported apps without enrolling the device. Combined with a Conditional Access policy that requires protected apps, this is the best compromise for many companies.

Can Intune track employees’ location?

Not on personal devices. On company devices, the organisation can retrieve the location of a device reported as lost; on iPhone and iPad this uses managed lost mode, which locks the device and displays a message. Cover these cases explicitly in the works agreement.

Let's talk about your IT security

In the introductory call (30 minutes, no obligation) we clarify:

  • where your company stands today and what concerns you most
  • which next step makes sense for your organisation
  • what effort and price range to expect
Bastian Wenske

Bastian Wenske

Founder & Managing Director

Heidelberger Straße 15
12059 Berlin
Germany

Prefer to reach out directly? Send us an email at [email protected].