Managed Intune
The fake helpdesk is calling
Your access policies require verified devices. How confident are you that the verification actually holds? In Intune, a device without a compliance policy is compliant by default. And whoever set up their own laptop is a local admin.
Read-only, in the browser, in two minutesTuesday, 9 a.m., in accounting
A company with 600 employees. The Windows laptops are enrolled in Intune, but compliance policies exist only for smartphones. Whoever set up their laptop is a local admin. None of this is a gap someone deliberately created. It's just the state no one ever changed.
- 9:00 a.m.What happens
The inbox floods
Hundreds of newsletters and spam emails in one hour. The accountant can no longer get any work done and waits for someone to help.
What helpsThe pattern is known: employees have been forewarned, the CSOC recognizes the wave and reports it through the shared channel.
- 9:20 a.m.What happens
Support gets in touch
Via Teams, from an external tenant, friendly and fast. They know about the mail flood because they triggered it.
What helpsExternal Teams contacts limited to known domains, a warning on external chats, and support requests verified through a known channel.
- 9:25 a.m.What happens
The code is read out
She opens Quick Assist and reads out the code. The attacker sees her screen and takes control of the mouse. To her, it looks like help.
What helpsQuick Assist has been removed. Remote access is available exclusively through Remote Help, provided by your own support team, who sign in with their corporate account.
- 9:40 a.m.What happens
Tools are downloaded
A script downloads software. Because the accountant is a local admin, the software installs itself persistently and survives a reboot.
What helpsNo local admin rights. App Control and ASR rules block downloaded programs before they can run.
- MiddayWhat happens
Access to company data
The attacker accesses company data from her laptop. Conditional Access lets them through because a device without a policy is considered compliant.
What helpsWithout a policy, the device is treated as non-compliant. When an alert fires, it gets isolated, and the chain ends there.
A fictional scenario built from documented components: Microsoft Security Blog, September 2 and October 30, 2026; Microsoft Learn (Intune compliance default, local admins on Entra Join, Quick Assist); patterns observed in our CSOC since June 2026. Intune does not prevent the first two steps.
The device pushes back at every stage
The employee opens the door to their own machine. What happens after that is determined by the device. Click through the four stages and see how we break the chain.
Limit external Teams contacts to known domains, enable warnings for external chats, and verify support requests through a known channel.
Teams configuration and process, not Intune
Intune does not prevent the initial contact. What it does determine is how far an attacker gets after that. The rest comes from Teams hardening, Entra, and the CSOC.
Sources: Microsoft Security Blog, September 2, 2026 (attack flow) and October 30, 2026 (two cases involving AD CS, ESC1 and ESC8); Microsoft Learn on Quick Assist and Remote Help.
Users contacted across two Teams waves
privileged accounts for which the attacker obtained certificates
isolated device stopped the second case, following a Defender alert
What applies to your devices when no one does anything
Four Microsoft defaults. None of them is a mistake. Each is a decision no one at your organization has made. And Conditional Access relies on them: a device no one has checked still counts as checked.
A device without a compliance policy is considered compliant
Intune marks devices that no policy applies to as compliant. Conditional Access lets them through as if they had been verified.
Whoever enrolls a device in Entra becomes a local admin
On Entra Join, the user who sets up the device becomes a local administrator. Any software downloaded afterward installs itself persistently.
Quick Assist requires no roles and no sign-in
Anyone can start Quick Assist and read out a code. Microsoft recommends removing it when it is not needed.
Without App Control, nothing governs what runs
Every program a user launches runs. Including whatever a script just downloaded.
What Managed Intune delivers
Managed Intune has been running in customer production since October 2025, covering Windows, macOS, iOS, and Android. It also includes the Intune Health Check, a six-episode webcast series, and an on-site kickstarter.
Compliance as code
A device is only considered compliant when it meets the security baseline. If it deviates, it is non-compliant, and Conditional Access knows it.
Endpoint Security from the blueprint
Endpoint Security profiles are part of the blueprint. Additional profiles for ASR, EDR, and firewall are available as Extended Services.
Autopilot instead of images
Enrollment profiles, the status page, and restrictions all come from the blueprint. No local admin rights from the very first boot.
Evergreen
We review new Intune features and incorporate them. Changes with no adverse impact are pre-approved; you'll be notified.
Monitoring
Device compliance is monitored centrally, and logs are stored in your Log Analytics workspace. The CSOC picks up on anything unusual.
One model with Entra
The same blueprint approach, the same code, the same release process as Managed Entra. One point of contact for identity and device.
Operations as Code
What a change looks like with us
No clicking around in the portal, no ticket with a description someone has to reconstruct. Every change is a file, a plan, an approval, and a rollout you know about before it happens. The example here: a device without a compliance policy is now treated as non-compliant, as Microsoft recommends whenever Conditional Access is in play.
compliance_settings {- device_without_policy = "compliant"+ device_without_policy = "not_compliant" }+policy "Windows - Baseline" { bitlocker = true, local_admin = false }
- Compliance and configuration policies
- App protection and app configuration
- Enrollment, connections, and tokens
- Target groups, filters, and RBAC
- read-only
- in the browser
- two minutes
- Windows, macOS, iOS, Android
- free
The First Step
Measure first, then talk
The Intune Health Check reads your tenant in two minutes, read-only, in the browser. It shows which compliance policies actually reach which devices, how enrollment, connections, and certificates are faring, and where your client concept falls short of what Intune can do. For Windows, macOS, iOS, and Android, or just the platform you're focused on right now.
The analysis runs in your browser, and the data stays in the open tab. The export only comes to us if you send it with your meeting request.
Three perspectives, one question
If the fake helpdesk calls tomorrow: what should be allowed to happen on the machine after that?
What comes next
- Run the Health CheckRun the Health CheckYou check your own Intune tenant, read-only, in the browser. Policies, assignments, enrollment, connections. The export stays with you.
- Book a callBook a callFifteen minutes for an initial read, thirty for a full review. Bring the export or a specific question.
- Review the assessmentReview the assessmentWe place your tenant side by side with our blueprint, setting by setting, and show which stage of the scenario chain breaks where.
- Get a proposalGet a proposalKickstarter with two days on-site, Hosted Setup in two to four weeks, Managed Intune as an ongoing service with a base fee and user fee.
Schedule a Call with the Workplace Team
A Conversation with the Workplace Team
A quick check or a full consultation, fifteen or thirty minutes in Microsoft Teams with the colleagues who run Entra and Intune for our customers. Pick a duration, tell us what it's about and when works for you, and we'll send the invite.
30 minutes in Microsoft Teams
What it's about
When the admin is the tool
On March 11, 2026, a group used Intune to wipe devices across 79 countries. All it took was one compromised admin account. Here's what happened and which two architectural gaps made it possible.
Read the postEntra and Intune
Identity and device belong together
Entra handles who is working. Intune handles what they're working on. Conditional Access checks both on every sign-in, and the answer to the second question comes from Intune. We run both on the same blueprint, as code, with the same release process and a single point of contact for both.
Entra: Who is working
Employees, guests, apps, and agents with their sign-ins. Passkeys, Conditional Access, a lifecycle for everything without an HR record.
To the Entra storyIntune: What they're working on
Laptop, smartphone, shared device, and whether it's checked and protected. Compliance, Autopilot, Endpoint Security.
Questions that come up in the first conversation
Answer first, reasoning after.
Would Intune have prevented the call?
No. The external Teams chat and the spam flood are not an Intune problem; they call for Teams hardening, mail protection, and a helpdesk process your employees actually know. What Intune does determine is everything from step three onward: whether Quick Assist exists at all, whether downloaded software can run, whether the device counts as compliant. That's where the chain breaks.
Our devices are in Intune. Isn't that enough?
Enrolled is not the same as verified. A device without a compliance policy is considered compliant in Intune by default, and Conditional Access trusts that assessment. The real question is not whether your devices are in Intune, but whether every platform has a policy that actually reaches them. The Health Check shows you exactly that.
Can we just remove Quick Assist?
Yes, Microsoft recommends doing so when it isn't needed. Remote access then runs through Remote Help: the helper signs in with their corporate account, the session is logged, and an external caller no longer has a tool to work with. Whether Remote Help is part of your package depends on your license; we'll work that out in conversation.
What about employees who need local admin rights?
They exist, and they get them on a time-limited, documented basis, for example through Endpoint Privilege Management or a recorded exception in the repository. The default stays: no local admin. The exception is visible and expires, rather than silently appearing when someone sets up their laptop.
We already have a SOC. Do we still need Intune as a managed service?
The SOC sees the attack; Intune determines how far it gets. In the case Microsoft describes, a single isolated device stopped the second attack, following a Defender alert. Only someone who manages the device can isolate it. Both together is the norm for our customers: our CSOC flags the pattern, and the blueprint holds the line.
What does Managed Intune cost?
A monthly base fee plus a per-user fee. The starting point is the Kickstarter with two days on-site at a fixed price, followed by the Hosted Setup in two to four weeks and one day of onboarding. We discuss specific numbers in the conversation, since they depend on user count and platforms.
We already have Entra with you. What changes?
Not much in terms of how we work together, quite a lot in terms of impact. Entra and Intune run on the same blueprint, in the same repository, with the same release process and the same Technical Account Manager. Conditional Access then requires verified devices, and the verification behind it actually holds.

