Spyglass Microsoft Intune: 4-Week Implementation

Intune is a cloud-based service that allows organizations to manage and secure their endpoints. The Spyglass Intune Implementation offer focuses on providing a fully functional and deployed instance of Intune that leverages all its capabilities. To do this, Spyglass follows a device management maturity model that consists of:

Planning

Foundational

Standardized

Governed

Secured

Generative

Each tier corresponds to a level of automation, business value, and security for the endpoint devices. To execute this, Spyglass leverages six phases that correspond to a tier of the maturity model.

Phase 0: Intune Envisioning and Assessment. Assesses the existing environment, creates use cases and requirements, determines the roadmap and timeline, and provides estimates of effort.

Phase 1: Intune Onboarding Implementation. Configures the devices to be enrolled in Intune, either as Entra ID Joined or Hybrid AD Joined, and validates the enrollment process.

Phase 2: Intune Device Policy Implementation. Creates and applies mobile application management, configuration profiles, compliance policies, and device groups for the devices.

Phase 3: Intune Application Management Implementation. Creates and deploys application packages, application updates, patch update rings, and mobile applications for the devices.

Phase 4: Intune Endpoint Security Implementation. Configures and validates Defender for Endpoint, BitLocker, Attack Surface Reduction, Endpoint DLP, and Endpoint Detection and Response for the devices.

Phase 5: Intune Automation Implementation. Creates and tests Autopilot profiles, and reviews and reports using Endpoint Analytics.

Additionally, Spyglass 365 can provide Endpoint Device Management Tasks. These are ongoing services that provides weekly and monthly proactive device management tasks, such as reviewing reports, adding/updating applications, reviewing and fine-tuning policies, and creating new policies as necessary.

Cost/Timeline: 4-Weeks ($50k)*

*=Additional scoping may be needed based on complexity and number of endpoints.