How we access your Microsoft 365, where your data lives, which providers we use, how we use AI, and what happens if something goes wrong or you leave.
We reach your tenant through Microsoft's partner access (GDAP) with only the admin roles your services need, reviewed every quarter and removed when you leave.
Every Evisent account uses multi-factor authentication.
Automations and Evisent Insights, which handle email, files, finances and client records, run inside your own Microsoft 365 tenant. Never in ours.
Our Practice Automation products use rules and Microsoft-native tools, with no AI on your client content. A custom build uses AI only where you have approved it, with identifiers tokenised first.
If an incident affects your data, we tell you within 24 hours of finding it and help you assess your notifiable data breach duties.
What we build lives in your tenant. When you leave, we remove our access and delete what we hold, and the lists, flows and policies stay yours.
We use Granular Delegated Admin Privileges (GDAP), Microsoft's partner access model. You accept the relationship, you can see every role we hold in your admin centre, and you can end it at any time. These are the roles Practice Automation needs; managed IT clients agree their full role set at onboarding.
| Role | Why we need it | Used for |
|---|---|---|
| Exchange Administrator | Mail flow rules and retention on mailboxes | Payment and instruction guards, email filing |
| Security Administrator | Anti-phishing and impersonation protection | Payment and instruction guards |
| Compliance Administrator, eDiscovery Manager | Purview retention, data loss prevention and content search | Exposure sweeps, retention |
| SharePoint Administrator | Creating sites and lists | Registers, project and job setup, CPD tracker |
| Teams Administrator | Creating channels for alerts and projects | Project and job setup, alerts |
| Cloud Application Administrator | Creating app registrations for our products, and consenting the Evisent Live app | Automations, Evisent Live readings |
Your email, files, finances and client records never leave your Microsoft 365 tenant. The only thing we hold about you is what we already see as your IT provider: user names and email addresses, device and licence counts, and the status of your security tools.
| Data | Where | How long |
|---|---|---|
| Your email, files and records | Your Microsoft 365 tenant, Australian data location (checked at onboarding) | As you decide |
| Practice Automation: the automations, their logs and outcomes | Your Microsoft 365 tenant | As you decide |
| Evisent Insights and custom builds: finances, projects, documents, approvals, staff availability | Your Microsoft 365 tenant only | As you decide |
| Discovery interview recordings and transcripts | Your Microsoft 365 tenant only; see below | See below |
| Evisent Live: user names and email addresses, device, licence and security-tool status | Evisent's Microsoft Azure, Australia East | Daily snapshots 13 months, evidence packs 7 years; deleted within 30 days of exit |
| ID verification results (AML pack, in validation) | An Australian-hosted verification provider chosen with you to suit your requirements, and your client file | 7 years, per AML/CTF record keeping |
| Device security telemetry (managed IT clients) | Our security providers' platforms, mostly in the United States; see below | Per vendor retention |
| Notes and tickets about your systems | Our service desk in Australia and our documentation platform in the United States; see below | For the life of the relationship |
| Website enquiries | Our website providers, listed below; some outside Australia, as our privacy policy explains | As our privacy policy sets out |
Evisent Live reads configuration and status from your Microsoft 365 and security tools every morning. It is read-only, and it has no permission to read mail, files or SharePoint.
| Microsoft Graph permission (read-only) | What it is used for |
|---|---|
User.Read.All | Users, to count who is covered |
AuditLog.Read.All | MFA registration status |
Policy.Read.All | Conditional Access policies |
GroupMember.Read.All | Who is in the groups a Conditional Access policy includes or excludes, so MFA coverage is counted per person |
DeviceManagementManagedDevices.Read.All | Intune devices: compliance and encryption |
DeviceManagementConfiguration.Read.All | Intune compliance policies |
SecurityAlert.Read.All | Open Microsoft 365 security alerts |
SecurityEvents.Read.All | Microsoft Secure Score, shown as a benchmark |
IdentityRiskyUser.Read.All | Risky users (where Entra ID P2 is licensed) |
IdentityRiskEvent.Read.All | Risky sign-in detections |
No Mail, Files or Sites permissions are requested. Security tools (endpoint protection, detection and response, application allowlisting, patching) are read through their own read-only API keys.
| Question | Answer |
|---|---|
| Where is it hosted? | Microsoft Azure, Australia East. The app's static front end is served from Microsoft's global edge; the data is not. |
| How long is it kept? | Daily snapshots for 13 months. Evidence packs for 7 years. |
| Who can see it? | Evisent staff, signed in with Microsoft Entra and on an allowlist. Client login is In validation: piloting with managed clients, rolling out to all managed clients in early 2027. |
| Who else can see it? | Only people you share it with: read-only links that expire, with every open logged and revocable at any time. Shared views show counts and percentages, with staff names left off by default. |
| Does AI read it? | No. Collection and scoring are plain code. No AI reads client data. |
None of our Practice Automation products uses AI on your client content. They run on rules and Microsoft-native tools, so every decision can be explained, which matters under the Privacy Act transparency rules from 10 December 2026.
A build made for your business can use AI where rules cannot do the job, and only with your sign-off. Identifiers are tokenised first, a named person approves the result, and it is logged. The rules are below.
We use AI tools, including Anthropic's Claude, for internal work such as drafting and research. Your client data does not go into those tools. The one exception is discovery interview transcripts, which we may process with an AI service outside Australia, only with your sign-off (see below).
If you want Microsoft 365 Copilot or another AI tool, we can license, configure and secure it for you, and we help you set the data rules first.
Enquiries sent through our ask and booking forms are not processed by AI. Our retired AI readiness quiz used Anthropic's Claude to prepare reports; it has been switched off.
The fixed-price Practice Automation products use no AI on your client content. Custom builds and Evisent Insights are different: they are built for your business, and a step can use AI where rules cannot do the job. When one does, the written scope names the step, the model and where it runs, and these rules apply.
| Rule | What it means |
|---|---|
| Runs in your tenant | The build and its data live in your own Microsoft 365 and Azure tenant. Evisent holds no copy of the data in it. |
| Rules and formulas first | Numbers come from rules and formulas, never from AI, so every figure can be traced and explained. |
| Identifiers tokenised | Before anything is sent to an AI model, names, account numbers and other identifiers are swapped for tokens. The key that swaps them back stays in your tenant. |
| Where the model runs | Tokenising does not change the rule above. Data that needs to stay in Australia stays here. A more capable model hosted overseas is used only for data that is allowed to leave, with your sign-off and within your compliance obligations. |
| A named person approves | Nothing an AI step produces is final until a named person in your business has approved it. |
| Logged and exportable | Each AI step is logged with what was sent, what came back and who approved it. The log can be exported for your auditor, licensee or insurer. |
| Run in parallel first | A new process runs alongside the old one until you are satisfied, then cuts over. |
In an Automation & AI Discovery we interview your staff one at a time. They only tell the truth if it is safe to, so the rules are fixed before the first interview and staff are told them.
| Question | Answer |
|---|---|
| Are interviews recorded? | Yes, with each person's consent, asked at the start. Someone who does not want to be recorded is interviewed with notes only. |
| Where is the recording kept? | With a business meeting notetaking service, hosted outside Australia, on Evisent's account. We record only with your sign-off and each person's consent. |
| Who can open it? | Only the Evisent staff running the engagement. Your leadership and other staff are not given access. |
| How long is it kept? | Recordings and transcripts are deleted 30 days after the findings report is delivered. |
| What does leadership see? | Themes and scored opportunities. Not recordings, not transcripts, and not who said what. |
| Do staff send you files? | No. Staff show the work on screen share. They never email files to us and we take no copies of your documents. |
| What if someone reports a security problem? | We raise it with your sponsor as a security finding, without saying who told us. Staff are told this before the interview starts. |
| Is AI used on the transcripts? | Yes, with your sign-off, and staff are told before the interview. After each interview we may use a business-grade AI service, hosted outside Australia, to help turn the transcript into notes and themes. Under that service’s business terms, what we submit is not used to train its models. A person at Evisent reads every transcript and writes the findings, and no AI output goes to your leadership unreviewed. If you would rather your transcripts were not processed this way, say so and we work from them by hand. |
We use as few providers as we can, and only for what each one does best.
| Provider | What for | Whose data | Where |
|---|---|---|---|
| Microsoft (Microsoft 365, Azure) | Your tenant; our automation service | Your client data | Australia |
| Endpoint detection and response provider | Detecting and responding to threats on devices | Device telemetry | United States |
| Application control provider | Allowing only approved software to run | Device telemetry | United States |
| Patch management provider | Keeping operating systems and applications up to date | Device and software inventory | United States |
| Microsoft 365 management platform | Microsoft 365 standards and drift checks, hosted by Evisent | Tenant configuration | Australia (Microsoft Azure, Melbourne) |
| Service desk platform | Tickets and projects | Support records | Australia |
| IT documentation platform | Documentation | System configuration notes | United States |
| ID verification provider (AML pack) | ID, sanctions and PEP checks | Your clients' identity data | Australia. Provider chosen with you, to suit your requirements |
| Email delivery provider | Delivering website enquiries to our inbox | Website enquiries | United States |
| Cloudflare | Website hosting and enquiry database | Website enquiries | Website served from a global network; enquiry database in the Oceania region |
| Google, Microsoft Clarity and Microsoft Advertising | Website analytics and advertising measurement | Website visit data | Outside Australia, typically United States |
| Fireflies.ai (business account) | Recording and transcribing discovery interviews, with the client's sign-off and each person's consent | Interview recordings and transcripts, deleted 30 days after the findings report is delivered (Fireflies states it does not use meeting data to train AI models) | Outside Australia |
| Anthropic (Claude, business plan) | Our internal work; discovery interview transcripts, with the client's sign-off | Evisent's own material; transcripts of discovery interviews (not used to train models under the business terms) | United States |
Send it to us. Licensees, insurers and auditors ask the same questions, and we would rather answer them in writing than leave you guessing.