Topic
This article describes what your organization needs to deploy and use NinjaOne Browser Management. Review each section before beginning your rollout.
Environment
- NinjaOne Endpoint Management
- Google Chrome
- Microsoft Edge
- Microsoft Windows
- Mozilla Firefox
Description
With NinjaOne's Browser Management application, you can inventory and manage your Microsoft Windows browser extensions and history directly in NinjaOne, providing control and visibility into extensions, history, and URL access.
Index
Select a topic to learn more:
- Platform Requirements
- Supported Browsers and Operating Systems
- Managed Browser Requirement
- Browser Extension Requirement
- Network Requirements
- Administrative Requirements
- Current Limitations
- Additional Resources
Platform Requirements
Ensure you meet all platform requirements described below.
| Requirement | Description |
|---|---|
| NinjaOne agent | Endpoints must have the NinjaOne agent installed, checked in, and running the current generally available release. The agent delivers the Browser Management policy to the endpoint and reports the device state back to the NinjaOne platform. |
| Browser Management license | Your NinjaOne account must have the Browser Management module activated for the organization or policy where it will be applied. Contact your NinjaOne account representative if you need this added. |
| Platform access | An account with sufficient administrative permissions is required to configure Browser Management policies, review alerts, and manage the browser extension allowlist. |
Supported Browsers and Operating Systems
Browser Management supports the following browsers:
- Google Chrome
- Microsoft Edge
- Mozilla Firefox
Supported endpoint operating system:
- Windows 10 and Windows 11
Managed Browser Requirement
The device must be registered as a managed device at the operating system level. This is achieved by joining the device to Active Directory (domain-joined) or Microsoft Entra ID. Once a device is under enterprise management, Chrome, Edge, and Firefox will recognize and apply the policy delivered by NinjaOne; no separate policy deployment through Group Policy or Intune is required by your team.
- For Chrome and Edge, enterprise management is recognized once the device is domain-joined or Microsoft Entra ID-joined; NinjaOne then applies policy directly.
- For Firefox, either the same domain or an Entra ID join satisfies the enterprise management requirement that Firefox checks before honoring the policy.
- Devices that are not domain-joined or Entra ID-joined (for example, a personal or unmanaged device) will not be covered by NinjaOne Browser Management.
Browser Extension Requirement
NinjaOne delivers browser management through a NinjaOne browser extension. Once a device is under enterprise management, NinjaOne automatically force-installs and locks the extension in place — no manual configuration of force-install or allowlist policies is required from your team.
Network Requirements
Your endpoints will need outbound HTTPS access to NinjaOne's cloud services for policy sync, telemetry, and alerting.
Administrative Requirements
Ensure you meet the following requirements:
NinjaOne does not require manual policy or extension deployment. After a device joins the domain or Entra ID, NinjaOne automatically applies the Browser Management policy. We recommend piloting Browser Management with a small group before rolling it out organization-wide, since the browser extension and policy changes are visible to end users.
Allow time for endpoints to check in and receive the updated policy — enforcement will not be immediate across all endpoints.
Current Limitations
Browsers or devices that are not domain-joined or Entra ID-joined are outside the scope of NinjaOne Browser Management. We do not currently support browsers other than Chrome, Edge, and Firefox.
Additional Resources
To learn how to use NinjaOne Browser Management, refer to NinjaOne Browser Management: Getting Started.