Microsoft 365 Integration

Your Microsoft estate.
One security picture.

Put the security signals from your Microsoft estate to work. Braintree connects supported Defender, identity and email integrations to Arctic Wolf’s investigation and response, with the licences, permissions and action authority agreed.

Global security expertise. Local Microsoft depth.

Arctic Wolf

Your Microsoft
signals. Connected.

Microsoft 365 Integration

Defender XDR telemetry

Entra identity context

Agreed response permissions

MICROSOFT 365 INTEGRATION

Put your Microsoft security investment to work.

Signals across identities, email and endpoints become more useful when the investigation can see their relationship. A working integration needs the correct source, permissions and data flow, then an agreed response process.

01

Connect Defender signals

Supported Defender XDR integrations bring alerts from Endpoint, Identity, Office 365, Cloud Apps and Cloud into the investigation. Each workload depends on the licences and configuration in your tenant.

02

Respond through Microsoft tools

Supported integrations can connect investigation to endpoint containment, identity restrictions or malicious-email removal. Monitoring access and permission to change a system are separate decisions.

03

Maintain a working connection

Braintree helps map the application permissions, credential lifecycle and source health behind the integration. This makes the ongoing owner of the connection clear.

04

Connect the incident workflow

Where Sentinel is part of your operation, scope how Arctic Wolf tickets reach Microsoft and how statuses are handled. The Ticket API and Microsoft automation support a defined customer workflow.

HOW THE WORK CONNECTS

A connection your team can operate.

Required Microsoft licences differ by workload and response action. Cloud and hybrid identity configurations support different actions; government-cloud limitations also apply. The proposal confirms the tenant, source and action-specific requirements rather than assuming a Microsoft 365 subscription enables everything.

01

Scope

Identify workloads, signals and objectives.

02

Authorise

Confirm licences, consent and permissions.

03

Validate

Check source health and useful telemetry.

04

Respond

Test escalation and permitted actions.

THE SERVICE IN PRACTICE

What your team
will work with.

A Microsoft coverage map

Review the Microsoft workloads and licences already in place, the supported signals available and the separate response actions your team wants to enable.

A validated data connection

Demonstrate source health and useful security telemetry, with ownership of permissions and credential renewal recorded for the handover.

An agreed response example

Test an authorised action on an appropriate account, message or device so that your team understands both the security effect and the business impact.

Braintree

Close to your business.

Braintree connects the security operation to the Microsoft estate, people and processes it needs to protect.

Microsoft integration and local implementation

Agreed service scope and response ownership

Coordination as your environment evolves

Arctic Wolf

Built to see. Ready to act.

Arctic Wolf combines the Aurora Superintelligence Platform, its Agentic SOC and specialist security teams.

24×7 monitoring within the MDR service scope

AI-led investigation with human oversight

The Concierge Experience and security guidance

MICROSOFT 365 INTEGRATION IN DETAIL

The detail behind the decision.

Explore the fit, implementation requirements and practical questions with your team.

01

Start with the licences and signals you already have

Braintree’s Microsoft 365 integration offering connects supported Microsoft security information with Arctic Wolf’s monitoring and response operation. The assessment should begin with the tenant, deployed services and licences. Email, identity, endpoints and cloud workloads can contribute different evidence; a single Microsoft subscription does not establish every monitoring or response capability.

The proposed design should show which source feeds which workflow and who maintains the connection. This makes the assessment useful for an organisation that already owns Microsoft security tools but needs a clearer route from their alerts to investigation and action. The assessment also identifies configuration gaps before the service goes live.

02

Use the supported Defender connection

Arctic Wolf’s current Graph API guide identifies a Microsoft Defender XDR sensor for alerts from Defender for Cloud, Cloud Apps, Endpoint, Identity and Office 365. The documentation specifies the corresponding Microsoft licensing and application permissions. The relevant services must be licensed and enabled to produce the alerts used by the integration.

The same guide describes credential expiry and API constraints that can affect retrieval. Braintree should include credential ownership and renewal in the handover, then validate the sources expected from the tenant. A connected application is the starting point; the customer needs evidence that the intended security information is arriving and available for investigation.

03

Configure monitoring and response separately

The Microsoft 365 monitoring guide offers a deployment-application route and a manual configuration route for sending the required logs. Active Response is documented separately. Its Microsoft 365 integration supports deletion of a malicious email, subject to the required access and service configuration. If Microsoft is the only email-security product, the vendor specifies a dependency on Defender for Office 365 alerts for that response flow.

The configuration review should therefore show both sides: what information is collected and what action can be taken. Identity and host actions use their own supported integrations. Braintree should confirm tenant-type limitations and demonstrate authorised actions in an agreed test environment before operational use.

04

Define the relationship with Sentinel

Arctic Wolf publishes a sample Ticket API integration in which its tickets feed Microsoft Defender and Sentinel alerts, with Logic Apps supporting status synchronisation. This is a documented implementation example, not evidence that every Sentinel workspace is automatically connected or that all data moves in both directions.

Where Sentinel is part of the customer’s operating model, the assessment should identify which system owns the incident record, how duplicate alerts are handled and what happens when a ticket closes. A clear workflow prevents the internal team from maintaining competing records of the same investigation and makes the purpose of the integration understandable.

05

Set practical boundaries for the Microsoft estate

The integration assessment includes collaboration and identity requirements across Teams, SharePoint and Entra. The implementation should confirm the actual events and controls available for those services. General collaboration coverage should not be interpreted as unrestricted visibility into every document, conversation or account action.

  • Inventory Microsoft tenants, subscriptions, security licences and enabled services.

  • Map Microsoft 365, Defender and any Azure sources to supported collection methods.

  • Confirm application permissions, credential renewal and integration ownership.

  • Identify authorised email, identity or host responses and test the required actions.

  • Specify the Sentinel ticket workflow where it is required.

  • Agree contacts, escalation and a review of coverage when the Microsoft environment changes.

BEFORE YOU DECIDE

Practical questions.

▸

Does buying Microsoft 365 enable every Arctic Wolf integration?

▸

Is email monitoring enough to enable email deletion?

▸

Is Sentinel integration a standard mirror of all security data?

▸

Who maintains the Microsoft application credentials?

▸

Will cloud identity response sign a user out of an on-premises desktop session?

▸

Does Microsoft email response remove every copy across the tenant?

BUILD YOUR BUSINESS CASE

Connect Microsoft signals to an accountable response.

The problem to solve.

A Microsoft 365 tenant may generate useful security information without a clear route for investigation, escalation and follow-up.

What success should look like.

Identify the signal and access requirements for the integration, with named owners for tenant configuration and response actions.

Bring these into the discussion.

A useful starting point for your team and the people approving the investment.

  1. Tenant structure, Microsoft subscriptions and existing security integrations.

  2. Administrative roles, access constraints and the events the team needs to investigate.

  3. Current monitoring, escalation and remediation processes, including third-party responsibilities.

  1. Tenant structure, Microsoft subscriptions and existing security integrations.

  2. Administrative roles, access constraints and the events the team needs to investigate.

  3. Current monitoring, escalation and remediation processes, including third-party responsibilities.

LET’S GROW.

Work through the next step with Braintree.

Bring the tenant and monitoring context. We will help clarify the integration prerequisites and operational handover.

Braintree

Specialists in Business Applications,
Modern Workplace and Azure.

Microsoft
Solutions Partner

Built By Dynamite

© 2026 Braintree (Pty) Ltd

Braintree

Specialists in Business Applications,
Modern Workplace and Azure.

Microsoft
Solutions Partner

Built By Dynamite

© 2026 Braintree (Pty) Ltd

Braintree

Specialists in Business Applications,
Modern Workplace and Azure.

Microsoft
Solutions Partner

Built By Dynamite

© 2026 Braintree (Pty) Ltd