---
title: Conduct Risk Monitoring
seoTitle: Conduct Risk Monitoring for Microsoft Teams Calls
description: Check recorded Microsoft Teams calls against your own conduct rules, during or right after the call, with transcripts from AI models hosted in the EU.
subnav: true
finished: true
---

> [!herorow]
> Conduct Risk Monitoring
>
> # Find conduct risk *across your recorded calls*
>
> Argus Archive checks recorded calls against your own rules, during the call or right after it, and alerts the right reviewer.
>
> [Get a demo](/request-a-demo/)
>
> ![An Argus Archive policy as a flowchart: conduct rules for suitability, conflicts, vulnerable clients and risk warnings, each with its alert](/media/uploads/2026/10/18-policy-rules.jpg)

> [!plain]
> The problem
>
> ## Most calls are never reviewed
>
> Recording every call is only half the duty. Rules such as MiFID II and the Consumer Duty also expect firms to review what was said and show what they found. A compliance team listening by hand can only hear a small sample, so most conduct issues surface later, as a complaint or a regulator's question.

> [!highlights]
> Risks
>
> ## Conduct risks your rules can find
>
> You decide what each rule looks for, in plain language. Common starting points:
>
> ### Misleading promises
>
> Returns promised, risks played down, or terms left out.
>
> ### Unsuitable advice
>
> A product pushed before the client's needs are checked.
>
> ### Information leakage
>
> Client data or deal details shared where they shouldn't be.
>
> ### Off-channel moves
>
> "Call me on my mobile", or "let's move this to WhatsApp".
>
> ### Conflicts of interest
>
> Personal interests mixed with client business.
>
> ### Your own policies
>
> Anything your rules describe, from sales scripts to internal limits.

> [!security]
> Trust
>
> ## What your data protection officer will ask
>
> ![](/assets/icons/comprec-icon-enforced-by-policy.png)
>
> ### Your rules only
>
> Argus looks only for what your written rules describe, for the people you assign them to.
>
> ![](/assets/icons/callrec-icon-responsible-ai.png)
>
> ### AI with limits
>
> No emotion or voice recognition, and your data is never used to train AI.
>
> ![](/assets/icons/comprec-icon-role-access.png)
>
> ### Access by role
>
> Reviewers see only the alerts their role and groups allow.
>
> ![](/assets/icons/callrec-icon-location.png)
>
> ### Data residency
>
> Records are processed and stored on Microsoft Azure in the European Union, with more regions to follow.
>
> ![](/assets/icons/callrec-icon-entra.png)
>
> ### Your Microsoft sign-in
>
> Entra ID, MFA and Conditional Access protect every login.
>
> ![](/assets/icons/callrec-icon-audit-history.png)
>
> ### Every step logged
>
> The audit log shows who viewed, escalated or closed each alert.

> [!tour]
> Alerts
>
> ## From your rule to a recorded decision
>
> ![Argus Archive rule editor with a rule written in plain language](/media/uploads/2026/09/argusarchive-workflow-editor.jpg)
>
> ### Write the rule
> Describe what to look for in plain language and add your business context. Test it on past calls, then assign it to the people it covers.
>
> - Tested before it goes live
> - Different rules for different people
>
> ![The Argus Archive compliance assistant flagging a remark inside a Microsoft Teams call](/media/uploads/2026/09/argusarchive-teams-compliance-assistant.jpg)
>
> ### Get the alert
> Alerts arrive while the call is live with the Real-time add-on, or after it ends. A rule can also send a message in Microsoft Teams.
>
> - During the call or after it
> - Assigned to a reviewer
>
> ![A recorded meeting playing back in Argus Archive, with its video and screen share, speaker-labeled transcript, AI summary and keywords](/media/uploads/2026/10/29-meeting-transcript.jpg)
>
> ### Review the call
> Open the recording, its transcript and its summary from the alert. Transcripts come from frontier AI models hosted in the EU.
>
> - Recording, transcript and summary together
>
> ![An Argus Archive case with its reference, its conversation count and legal hold on](/media/uploads/2026/10/13-case-alerts.jpg)
>
> ### Record the decision
> Escalate the alert to a colleague, or close it as resolved or dismissed. Each needs a reason, and every step goes into the audit log.
>
> - A record you can show when asked

> [!faq]
> FAQ
>
> ## Frequently asked questions
>
> Still have questions? Ask the team that built it.
>
> [Talk to us](/contact/)
>
> ### What does Argus look for?
> Only what your rules describe, such as advice, promises or client data, in the calls of the people each rule is assigned to. It has no emotion or voice recognition.
>
> ### Is it just keyword spotting?
> No. Rules use large language models to understand what was meant in context, so they catch risks that keyword lists miss and raise fewer false alarms.
>
> ### Can we test a rule before it goes live?
> Yes. Run it against past calls first, review the results, then publish it.
>
> ### Does it check calls while they happen?
> Yes, for users with the Real-time add-on. For everyone else, calls are checked after they end.
>
> ### Which Microsoft 365 licenses do we need?
> Each recorded user needs a license Microsoft lists as eligible for compliance recording.
>
> [Microsoft's license list](https://learn.microsoft.com/en-us/microsoftteams/teams-recording-compliance)
>
> ### How much does it cost?
> Argus Archive is priced per user, per month, with usage included, and you're warned before you go over.
>
> [See pricing](/pricing/)

> [!articles]
> Articles
>
> ## Worth reading
>
> Monitoring, inspections and what AI changes for conduct reviews.
>
> - /blog/real-time-compliance-monitoring/
> - /blog/what-the-amfs-spot-inspections-reveal-about-mifid-ii-communication-recording-requirements/
> - /blog/the-fcas-mills-review-why-ai-makes-communications-archives-more-important-than-ever/