Intune and NinjaOne integration expands endpoint management
No-Faffing Managed IT Support & Cyber Security Support. Made in Yorkshire, built for the UK.
Jonathan Edwards’ Short points to a NinjaOne–Intune integration, but its supplied transcript does not explain what changed.
Key insights
- The supplied Short transcript contains no feature details beyond identifying it as a YouTube Short.
- Research notes describe Intune as the identity, device registration and compliance layer.
- The notes describe NinjaOne as handling endpoint monitoring, patching, automation and remote support.
- The material does not confirm rollout, licensing, or the specific change shown in the Short.
Jonathan Edwards published a 48-second YouTube Short titled “NinjaOne have never done this before.” The supplied transcript contains only the words “You Tube Short Video,” so it does not establish what Edwards showed or when within the clip he showed it. Research notes supplied with the page describe a NinjaOne integration with Microsoft Intune, but the specific novelty implied by the title cannot be confirmed from the transcript.
What's new
The background notes characterize the integration as pairing Intune’s identity, device registration and compliance capabilities with NinjaOne’s operational endpoint management. They describe NinjaOne tasks including monitoring, patch management, automated maintenance, troubleshooting and remote support. In that account, Intune remains in place rather than being replaced.
The notes also describe an end-to-end device lifecycle approach, including device discovery and ongoing management. They mention NinjaOne Network Discovery and a capability in version 14.0 to install the NinjaOne agent from the discovery view on eligible Windows devices. However, those details are not present in the supplied Short transcript, and the supporting material does not provide a verifiable source URL for that version-specific claim.
Why it matters
For IT administrators, the proposed division of responsibilities could preserve Intune for identity, enrollment and compliance while assigning day-to-day endpoint operations to NinjaOne. That distinction may be relevant to teams assessing whether their current tools cover both policy governance and ongoing device maintenance. The notes say this approach is intended to reduce disconnected management steps, but they do not quantify time savings or describe a measured outcome.
For endpoint teams, monitoring, patching and remote troubleshooting are the operational areas identified in the notes. They do not explain what changes for end users, which organizations can use the integration, or whether extra licenses are required. The material also does not specify a rollout stage.
How it works
As described in the research notes, Intune provides the identity, registration and compliance context, while NinjaOne performs operational management. A separate discovery workflow is said to identify network-connected devices and, for eligible Windows devices, allow an agent installation from the discovery view. The notes do not provide configuration steps or explain prerequisites, so administrators should not treat this as a complete deployment guide.
Limitations and open questions
The Short transcript supplied for this article has no substantive narration or demonstration details. We could not verify from it what NinjaOne has “never done before,” nor confirm the integration’s technical mechanics, licensing, availability or rollout. The research notes offer context, but do not resolve those gaps; the precise announcement should be checked against fuller product documentation before making deployment decisions.
Sources
Frequently asked questions
What did Jonathan Edwards show in the Short?
The supplied transcript includes no demonstration or explanation, so the specific action shown cannot be established from the available material.
How are Intune and NinjaOne described as working together?
The research notes describe Intune as covering identity, registration and compliance, while NinjaOne handles endpoint operations such as monitoring and patching.
Is the integration available, and what licenses does it require?
The supplied material does not state availability, rollout stage or licensing requirements.