Access for the work you enable
Microsoft 365 uses OAuth and Microsoft Graph. Read-only mode gathers context; actions need additional permissions. Review the actual consent scopes before enabling write access.
We’re looking for MSPs to put DaemonLayer through its paces.
AI agents resolve password resets, mailbox access and group changes end to end — approved where you require it, completed in Microsoft 365 and written back to the HaloPSA ticket.
Before you grant access
Your technical lead can review access before you connect HaloPSA or grant Microsoft 365 consent.
Microsoft 365 uses OAuth and Microsoft Graph. Read-only mode gathers context; actions need additional permissions. Review the actual consent scopes before enabling write access.
Connect a selected client’s Microsoft 365 tenant and start with a supported request. Your HaloPSA API account has its own permissions, which also need reviewing.
Your Microsoft 365 administrator can revoke the app’s permissions in Microsoft Entra. Review the HaloPSA API connection separately when disconnecting.
Published data hosting is in the UK and EU; AI processing uses EU data zones. Review the details for your clients’ residency requirements.
From request to recorded outcome
Follow a mailbox access request through an intelligent workflow. The checks and controls stay visible, and your engineer’s working record stays in HaloPSA.
The category and confidence are determined and the matching workflow is selected. Anything uncertain goes to a technician instead.
It confirms Alex and the accounts mailbox exist in the client’s tenant and that no access is in place yet.
When your rules require it, the workflow pauses and notifies the approver with the proposed change. Nothing changes until it is approved. A rejection hands the ticket to a technician.
Full Access is granted in Microsoft 365. Note, status and time entry are written to the HaloPSA ticket.
Your Halo configuration matters
Tickets go to the client’s primary or secondary technician first. If neither is available within the SLA window, they go to another technician in the HaloPSA Team.
Map statuses by ticket type, so updates follow the structure configured in your Halo instance.
Write back notes, status updates and time entries. Send requester notifications through Halo email actions when configured.
What your AI agents can handle
AI agents interpret the request and carry out supported actions. Predefined workflows supply the checks and boundaries, with context returned to HaloPSA when an engineer needs to take over.
Verify identity, act only with the supported account actions and notify the user.
Grant supported mailbox and delegate permissions.
Add or remove users from supported Microsoft 365 groups.
Configure supported automatic replies and forwarding requests.
Update details such as job title, department or phone number.
Carry out supported account setup and offboarding tasks.
Anything outside a supported workflow goes to your engineers in HaloPSA, with the context already gathered.
Automation you can account for
Define access and approval requirements before a workflow makes changes in a client’s environment.
Explore authorisation controls ↗Sensitive requests pause where the selected workflow requires authorisation. Your team can review the proposed change and its context.
External-system workflow steps have cryptographically linked records to help detect changes to the execution history. Outcomes return to HaloPSA.
Start with one client tenant. Cancel in the admin panel.
We contact you to agree a plan. Unless you cancel, if no plan is agreed your account converts automatically to the matching paid plan based on ticket volume. Pricing is confirmed before you are charged.
A first step you can assess
Choose a client you are authorised to connect. Review consent with your technical lead, then evaluate a routine request before extending automation to more clients.
Start with one clientAgree the client scope, set up the HaloPSA API connection and review ticket-type and status mappings.
Ask the client’s authorised administrator to review the Microsoft Graph permissions. Choose read-only or the access needed for your selected action.
Set the approval rules, run a supported request and inspect its outcome in HaloPSA before connecting more clients.
Yes. Begin with a selected client’s Microsoft 365 tenant and a supported request. Review the HaloPSA intake scope as well as the Microsoft 365 connection, then expand after you have checked the results.
Context gathering can use read-only access. Password resets, group changes and mailbox actions require the appropriate write permissions. An authorised administrator reviews the consent scopes for the connection. Workflow controls limit execution but do not themselves narrow an underlying API permission grant.
The published privacy policy specifies UK and EU cloud hosting. AI processing takes place in EU data zones. If a client requires US or Australian residency, confirm the arrangement before connecting them; local hosting in those regions is not stated.
AI can make mistakes. Configured confidence thresholds and approval gates limit when actions run. Requests that cannot proceed go to the service desk with context and execution history. Review initial results and sensitive actions before expanding; do not assume every change is automatically reversible.
An authorised administrator can review and revoke the app permissions in the client’s Microsoft Entra tenant. Review the HaloPSA API application separately.
The published offer is a 14-day trial with no credit card. An activation-based start is not specified; confirm the start date if client consent may take time. DaemonLayer contacts you to agree a plan. Unless you cancel, if nothing is agreed the account converts to the matching paid plan, with pricing confirmed before charging.
The published terms describe work towards formal certification; they do not establish completed SOC 2 certification. Confirm current certification evidence, support hours and response arrangements for your time zone on the demo call.
Your next routine request
Start with one client, or book a 30-minute walkthrough and see routine Microsoft 365 requests completed through your HaloPSA service desk.
Form not loading? Open it in a new tab.