Shadow AI at the first gate
Hartwell Trust Bank checks an outside AI use case with fictional data.
Coming
See every demonstrationMICROSOFT 365 SECURITY IMPLEMENTATION
Identity and endpoint baselines, piloted on 250 devices before the wave.
Security changes without a validated pilot, a recovery plan and a named operator end up reverted at the first support call. In four weeks on one tenant we audit the boundary, approve the identity, endpoint and recovery design, configure a pilot of up to 250 devices, resolve the exceptions and train your operations team, then run the production wave you approve and hand over the operating evidence.
01 Source02 Boundary03 Human decision04 Evidence
HOW IT WORKS
The control path in practice.
- Week one: audit the tenant boundary and approve the identity, endpoint and recovery design.
- Week two: configure the pilot of up to 250 devices with Microsoft Entra ID, Microsoft Intune and Microsoft Defender for Endpoint.
- Week three: validate the pilot, resolve the exceptions and train the operations team.
- Week four: execute the production wave you approve and transfer the operating evidence.
THE PROBLEM
Why do baseline rollouts get reverted?
Because a policy that was never piloted meets a device nobody inventoried and a person with no recovery path, and the fastest fix at nine in the morning is to turn it off. The implementation puts the pilot, the exception register and the recovery runbook before the wave, and every production change needs your approval of the exact change with its validation evidence and recovery plan.
The statement of work confirms the Microsoft Entra ID, Microsoft Intune and Microsoft Defender for Endpoint work packages, the twelve to twenty Conditional Access policies, the production-wave quantities and the support period. Larger estates get a separate schedule.
THE MICROSOFT INSIGHT
What does onboarding a device to Defender for Endpoint buy you now?
Since October 2026 Microsoft Defender for Endpoint discovers local AI agents and their configured MCP servers on onboarded Windows and macOS devices and lists them in the AI agent inventory, so the same onboarding that protects the endpoint also tells you which agents a developer installed.
Since October 2026 Microsoft Defender for Endpoint discovers local AI agents and their configured MCP servers on onboarded Windows and macOS devices and lists them in the AI agent inventory and advanced hunting. (Microsoft Learn, checked Nov 4, 2026)
Onboard the devices and the agent inventory fills itself. Leave them off and the first agent you learn about is the one in the incident.
THE METHOD
What happens in the four weeks?
Design, pilot, validation, wave, each gated by your approval.
- Week 1: audit the tenant boundary and approve the identity, endpoint and recovery design.
- Week 2: configure the pilot of up to 250 devices.
- Week 3: validate the pilot, resolve exceptions, train the operations team.
- Week 4: execute the customer-approved production wave and transfer the operating evidence.
THE MAIL
What does the baseline already include for email?
Microsoft Defender for Office 365 Plan 1 is included in Microsoft 365 E3, and since July 2026 Defender for Office 365 detects prompt injection attacks hidden in inbound email, so the baseline switches on protection the license already carries before anything is bought.
Since July 2026 Microsoft Defender for Office 365 detects prompt injection attacks hidden in inbound email, and Defender for Office 365 Plan 1 is included in Microsoft 365 E3. (Microsoft Learn, checked Nov 4, 2026)
Turn on what the license includes and the first wave covers mail as well as identity and devices. Skip it and the gap is the channel most attacks use.
WHAT IT IS NOT
Does the engagement include licenses or ongoing support?
No. Microsoft licenses, unrelated application remediation, additional tenants, unsupported devices and continuing managed support are excluded, and no helpdesk reduction, enrollment speed or compliance certification is promised. Assessment-only work never authorizes a production change.
You name a sponsor and technical owners, provide the applicable licenses and approved evidence sources, and grant least-privilege access; the statement of work confirms quantities, acceptance tests and change windows. Delivery is remote. The estimated fee depends on estate size, workload complexity, evidence availability and change windows, and is confirmed before purchase.
AFTER TWO WEEKS
What will be working after two weeks?
- You hold an approved identity and endpoint implementation design with a recovery plan.
- Entra ID access policies, the Intune configuration and the Defender for Endpoint baseline are configured and piloted on up to 250 devices.
- You hold the pilot validation, the exception register and your own release decision for the wave.
- Your operations team is trained and holds the recovery runbook and the support handoff.
The work is delivered remotely inside your own Microsoft tenant, wherever your business is, and on site only when the work needs it.
HONEST ABOUT LIMITS
What this does not do yet
It does not extend to the network path without the Entra Suite. Microsoft Entra Internet Access, in the Microsoft Entra Suite or standalone with Entra ID P1 or P2, includes prompt injection protection, shadow AI discovery, TLS inspection and data loss prevention for web traffic, and its network controls for agents need a Microsoft Agent 365 license. (Microsoft Learn, checked Nov 4, 2026) Microsoft Entra Internet Access, in the Entra Suite or standalone with Entra ID P1 or P2, adds prompt injection protection, shadow AI discovery and web DLP at the network layer, and its agent network controls need a Microsoft Agent 365 license; the design records whether that layer is licensed and sequences it after the identity and endpoint waves.
It does not include licenses, extra tenants, unsupported devices or continuing managed support.
It does not promise helpdesk reduction or a compliance certification; it produces the operating evidence.
THE ONE THING TO REMEMBER
Pilot, exception register, recovery runbook, then the wave you approve.
Said another way: no production change without the exact change, its evidence and its rollback in front of you.
Said a third way: the baseline that survives is the one the operations team was trained to run.
SHOW YOUR WORK
See the control path on a fictional bank.
DIRECT ANSWERS
Questions before you decide.
How big a pilot?
Up to 250 devices on one tenant, with twelve to twenty Conditional Access policies and the production-wave quantities fixed in the statement of work. Larger estates get a separate schedule.
Who approves production changes?
You do, for each exact change, with its validation evidence and recovery plan in front of you. Assessment-only work never authorizes a production change.
What is handed over?
The approved design, the configured Entra ID, Intune and Defender for Endpoint baselines, the pilot validation and exception register, administrator training, the recovery runbook and the support handoff, with named operations and recovery owners.
How is it priced?
Confirmed before purchase from estate size, workload complexity, evidence availability and change windows, in the scoping call. The Microsoft Marketplace listing is bought by private offer after that call. No price appears on this site.
NEXT STEP
Start with a boundary you can explain.
Choose a focused check, or speak with the team about the workflow you need to improve.
View the Microsoft Marketplace listing It is bought by private offer after the scoping call, on your Microsoft agreement.