Xemplify Foresight Demo

Dashboard

Population

.../100

BUSINESS EXPERIENCE SCORE

Performing well, with preventable friction

History period+4.2

30 days agoToday

!...Users experiencing friction

◷...Estimated recoverable time

✓...Meets automation-readiness policy

Formula v1.0Coverage 94% representativePopulation selected enterprise workforceFreshness 2 minExclusions service and test accountsTime estimate approved event-duration assumptions

PRIORITIZED ISSUES

Prioritized issues and improvement opportunities

Rank by

Issue and likely cause Users / devicesScore / priority Policy state

1ObserveExperience and operational signals

2ExplainDevice, identity, service, and business context

3DecideRecommended action with confidence and policy

4ExecuteApproved playbooks through enterprise connectors

5VerifyMeasured recovery and evidence

Organization Platform Risk level Finding activity

RISK CONCENTRATION

Enterprise Health Map

Compare enterprise departments without overlapping labels, then isolate one Department or one operational risk category.

LowCritical

Select an Department name to focus the findings list. Select a category to recalculate the gradient using that signal domain.

PRIORITY

Highest-Impact Risk Findings

SERVICE DESK

Context Before, During & After Contact

Foresight correlates operational experience with incidents, requests, changes, problems, and service ownership records from the connected ITSM system.

Select identity

1

USER CONTACT

2

AGENT WORKSPACE

Unified support context

RECOMMENDED ACTION

3

RESOLUTION

Guided Resolution Workflow

Context available at first contactLess repetitive discovery

First-contact resolutionRecommended next action

Lower customer effortFewer transfers

Secure workflowVerified identity and approval

DESKSIDE SUPPORT

Predictive Device Intervention

Foresight correlates device signals into a pre-diagnosed event with remediation and lifecycle guidance.

Device

DEVICE HEALTH SIGNALS

Device

PerformanceReliabilityStorageSecurityConnectivityUsage

DEMO OPERATIONAL RISK

Scenario Operational Risk

0Risk score

Signal correlationAcross enterprise devicesReview priorityNot a predicted failure windowImpact assessmentUser, device, and mission

TECHNICIAN DASHBOARD

Pre-Diagnosed Device Event

Run diagnosticsApply fixesValidateMonitor

DECISION SUPPORT

Select the appropriate intervention

Three approved response options are evaluated for each device.

RECOMMENDED OUTCOME

Reduced downtimeProactive detection

Lower technician touchAutomation first

Smarter lifecycle decisionsData-driven options

Better user experienceRight-sized intervention

CORRELATED DEVICE CONTEXT

Devices Requiring Attention

⌕

CONTROLLED EXECUTION

Turn Intelligence into Governed Action

Review targets, approvals and response outcomes in one workflow.

0Preview runs this session

...Completed-run success

...Completed-run median

Execution history

AUTOMATION CATALOG

Governed Playbooks

EXECUTION RECORD

Select a governed playbook

Ready

◇

Choose a playbook to review its scope, approval gate, connector, and execution steps.

ENGINEER OPERATIONS

Fleet Intelligence and Controlled Action

Explore correlated records at scale, select a population, stage bulk remediation, inspect collection health, and export evidence.

CORRELATED DEVICE INVENTORY

Enterprise Fleet Explorer

	Device	Primary user	Department	Management	Experience	Demo operational risk	Compliance	Last check-in	Tickets

0 devices selected

GOVERNED BULK ACTION

Restore endpoint and Defender health

Approval required

RECENT EXPORTS

Generated evidence and datasets

TENANT ONBOARDING

Connect Foresight to a Microsoft tenant

Review how the enterprise application is authorized, what each permission can access, how the pilot is scoped, and which governance controls apply before activation.

STEP 1 OF 6

Connect your Microsoft tenant

Start with observation. Add governed action only after the customer defines its approval, targeting, verification, and rollback requirements.

▣

No tenant connectedAuthenticate as an authorized Microsoft administrator and review consent in Microsoft's tenant experience.

Demo

STEP 2 OF 6

Review requested access

Consent is granted to the Foresight service principal in Microsoft Entra ID. Microsoft Graph permissions authorize that application identity to access specific Intune or Entra resources.

What receives the permission?

The permission is assigned to the Foresight enterprise application in Entra—not to individual users, devices, groups, or Intune objects.

Microsoft Intunevia Microsoft Graph

Object types: managedDevice records
Examples: Device ID and name, OS, ownership, enrollment, compliance, last sync, and other API-exposed properties.
Technical reach: Tenant-wide access to the permitted managed-device resource.
Does not grant: Configuration changes, deployment, device actions, or arbitrary commands.

Microsoft Entra IDvia Microsoft Graph

Object types: Users, groups, Entra device objects, administrative units, applications/service principals, and other directory resources exposed by this permission.
Purpose: Correlates Intune devices with owners and customer-defined organizational populations.
Technical reach: Broad directory permission. Replace it with narrower permissions wherever the validated feature set permits.
Does not grant: Write, delete, role assignment, password, or authentication-method changes.

Object types: Directory audit activities and sign-in records available through Microsoft Graph.
Purpose: Correlates approved identity events with device and experience findings.
Technical reach: Application permission requiring administrator consent.
Does not grant: Changes to Conditional Access, identities, credentials, or audit records.

Important: pilot scope limits what Foresight collects and displays; it does not automatically narrow a tenant-wide Graph application permission.

STEP 3 OF 6

Start with a controlled pilot

Limit the initial working population, validate data quality and coverage, then expand only after the customer accepts the results.

Pilot population

Include enrolled Windows devicesSupported devices currently reporting through Intune Include approved identity signalsAccess remains role- and population-filtered inside Foresight Connect service managementOptional ServiceNow, Jira Service Management, or approved ITSM source

STEP 4 OF 6

Apply customer governance

Automation readiness is not authorization. Execution remains subject to the customer's approvals, maintenance windows, targeting rules, and security controls.

Require approval before executionNamed approvers or an approved ITSM workflow Validate targets immediately before actionPrevents stale or out-of-scope targeting Capture verification and rollback evidenceImmutable action, outcome, and exception trail

Unrestricted scripts are blocked

Only approved responses from the managed catalog may be staged. Each response requires the appropriate review and authorization.

STEP 5 OF 6

Validate before activation

Run non-destructive checks to confirm access, scope, freshness, and governance readiness.

○Microsoft Graph connectionNot run

○Pilot population resolutionNot run

○Telemetry coverage and freshnessNot run

○Approval and audit controlsNot run

STEP 6 OF 6

✓

Tenant connection is ready

Foresight can begin collecting approved telemetry for the pilot. No remediation runs until the applicable customer approval and security controls are satisfied.

ModeObserve onlyPopulationIT Operations · 250 devicesValidation4 of 4 passed

FORESIGHT USER GUIDE

From insight to action

Explore measurements, investigate issues and review proposed responses.

1

ANALYTICS

Start with enterprise experience

Understand what the score measures and why issues are flagged. Choose an issue to see the supporting observations, users affected and potential improvement.

2

OPERATIONAL HEALTH

See operational health across the environment

Explore devices and systems across enterprise departments. Drill through the hierarchy and compare domain-specific risk using the same scope as the risk export.

3

SERVICE DESK

Resolve with context already available

Select a support case to review user, device and incident context.

4

DESKSIDE SUPPORT

Choose the right device intervention

Compare device findings, operational priority and response options.

5

INTELLIGENCE

Explain what requires attention

Review device observations, associated users and recommended responses.

6

ORCHESTRATION

Review the response workflow

Review the target, proposed response, approval owner and success checks.

What makes Foresight differentObserve → Explain → Decide → Act → Verify. Connect operational context to a governed response.