What was announced
The integration tracks Azure virtual machines and NinjaOne-managed endpoints in one place. NinjaOne's integrations page describes the same function in plainer terms. It says the integration lets you discover cloud workloads and add them to the discovered devices repository in NinjaOne.
NinjaOne gives three scenarios for the feature:
- Unified inventory. Organisations can discover and track Azure VMs alongside endpoints, reconciling gaps in asset inventories.
- Microsoft-centric environments. The company says the integration brings Azure workloads into the platform that organizations already use for endpoint management. It lists workloads across Microsoft 365, Intune, Entra ID and Azure VMs.
- Dev/test subscriptions. VMs pile up as projects evolve. The pitch is that technicians can spot them as soon as they exist and decide sooner which ones are still needed.
Matt Hastings, SVP of Product Management at NinjaOne, said the integration makes hybrid IT easier to manage for customers. That is a vendor executive's view, not customer evidence.
Not an entirely new idea
This is not NinjaOne's first mention of Azure discovery. The NinjaOne 16.0 release notes describe Early Access cloud visibility with AWS and Azure integrations. They say EC2 and Azure VMs come into NinjaOne as discovered devices that can be promoted to managed or unmanaged devices. The November 2026 announcement therefore looks like a formal launch of a capability that was already visible in the product. I could not confirm from the available material whether anything changed between the Early Access version and this announcement.
The "promote" step matters for admins. In the 16.0 description, a discovered VM is a record first. It becomes a managed device only when someone promotes it.
NinjaOne's integrations page also lists a separate AWS integration. It lists Microsoft Intune integration as well, aimed at unified visibility and management of endpoints. Those are existing, separate capabilities, and the Azure announcement should not be read as replacing or merging them.
What the announcement does not say
The press material is about visibility. Based on the sources I reviewed, it does not claim any of the following:
- That NinjaOne agents are deployed to Azure VMs.
- That VM configurations are managed or changed.
- That idle dev/test resources are shut down, deleted or rightsized.
- That Azure's own governance and security controls are replaced.
The Microsoft 365, Intune and Entra ID wording is the vaguest part. Public material does not say which objects from those services are discovered, or how they are represented. Treat this as a VM-discovery integration until NinjaOne documents more. Don't assume it inventories every Microsoft 365 or Entra object.
Other details are also missing from what I reviewed:
- Required Azure roles and permissions, and whether discovery is read-only.
- Subscription and region coverage.
- How often the inventory refreshes.
- Workload types beyond VMs.
- Pricing and general availability terms.
Practical checks before you connect a tenant
NinjaOne has not published setup steps in the material I reviewed. The checks below are my suggestions, not documented product behavior.
- Get the implementation documentation first. Run the requested Azure access through your normal cloud-governance review before connecting a production tenant. Don't infer the permissions from NinjaOne's Intune integration.
- Pilot on a limited scope. Compare a sample of VMs in the Azure portal with the records that appear in NinjaOne's discovered devices.
- Look for omissions and duplicates. A VM that is also an Intune-enrolled or agent-managed machine could show up twice.
- Test the lifecycle. Check how quickly a new VM appears, and what happens when a VM is stopped, renamed or deleted.
- Assign ownership. Decide who reviews newly discovered assets. In dev/test subscriptions, confirm with the application owner before stopping or deleting anything.
Analysis
The underlying problem is real and well known. Cloud workloads are often provisioned outside the team that runs endpoint tooling, and they can go untracked. The cost, security and compliance risks NinjaOne cites are plausible, but they are the company's argument. The announcement offers no measured results.
Discovery is also only the first step. Finding a VM does not show that it is approved, patched, protected or compliant. For Azure-heavy shops, native Azure tooling already shows these VMs, so the value here is mainly for MSPs and IT teams that want one console across endpoints and cloud. If you run NinjaOne already, the integration may be a cheap way to find gaps. Verify its permissions and accuracy before you rely on it as a source of truth.
Bottom line
NinjaOne's Azure integration adds Azure VMs to its discovered devices repository next to managed endpoints. That helps with inventory gaps, especially in dev/test subscriptions. Whether it suits your environment depends on details the vendor has not yet made public: permissions, scope, refresh behavior and cost.
References
- NinjaOne Announces Microsoft Azure Integration to Unify Visibility Across Hybrid IT Environments - TECHNOLOGY RESELLER TECHNOLOGY RESELLER · Tue, 17 Nov 2026 19:05:47 GMT
- NinjaOne anuncia su integración con Microsoft Azure para ofrecer una visión unificada de los entornos de TI híbridos ninjaone.com
- NinjaOne Integrations ninjaone.com