How BK Replay is set up
BK Replay works with your own Azure environment: recordings, transcripts, summaries and the AI live with your organisation, not with BK IT. BK IT provides the software that records, processes and displays, and gets only the permissions it needs for that. This page explains how it fits together, for anyone with questions about it (IT, security, privacy officer).
In short
| Part | Where | What it holds |
|---|---|---|
| Storage | An Azure storage account in your own subscription | The recordings (audio) and the transcripts and summaries as files |
| Database | An Azure SQL database in your own subscription | Call data, transcripts, summaries, promises, the word list, the audit log |
| AI | Azure AI Speech and Azure OpenAI in your own subscription | Processes the audio and text; stores nothing itself |
| BK Replay (at BK IT) | The recording servers and the portal | Software and configuration, no call data |
You choose the European region, the size and the security of your resources yourself, and you decide who can access them. The cost of those resources runs through your own Azure subscription.
How a call flows
- An employee with a recording policy makes or receives a call. Teams invites the BK Replay recording server to the call (compliance recording, a standard Microsoft Teams feature).
- The recording server receives the audio of both sides and holds it temporarily until the call has ended.
- Straight after that, the recording goes to your storage and the details go into your database. Nothing stays behind on the recording server.
- BK Replay has your AI create the transcript and summary, and stores the result in your storage and database.
- The portal and the Teams app read from your database and storage, only for people with a role for it.
No keys or passwords
BK Replay uses no keys, passwords or connection strings anywhere to reach your resources.
- In your Microsoft 365 environment, the BK Replay Recorder app exists as an enterprise application. After your consent (admin consent), you give that app a role on exactly the resources that are needed.
- BK Replay's servers sign in as that app with a federated credential (workload identity federation): their own managed identity in Azure proves who they are. There is no secret or certificate of the app that could leak.
- You can revoke access at any time by removing the role or disabling the app. BK Replay stops immediately.
- On the storage account, access keys are off; only Microsoft Entra sign-in works. The database uses Entra sign-in only, without SQL users with a password.
Least privilege
| Where | Role for BK Replay Recorder | Why |
|---|---|---|
| Storage | Storage Blob Data Contributor, only on the recordings container | Write and read recordings, and delete them after the retention period |
| Database | db_owner, only in the BK Replay database | Write and read data, and update the schema itself for new versions |
| AI | Cognitive Services User, only on the AI resource | Call speech recognition and summaries |
| Microsoft Graph | Record calls of employees with a recording policy, read call data, read users | Recording, the Telephony page, colleagues' names in the word list |
In addition:
- The BK Replay Portal app can only sign in on behalf of the user. What someone sees is decided by the roles you assign in your own Entra ID. Every request is checked on the server.
- With the Meetings module, BK Replay Recorder gets calendar and send permissions, limited to that one shared mailbox (Exchange RBAC for Applications). BK Replay cannot read other mailboxes.
- Credentials for an integration with your CRM or PSA can be kept in your own Azure Key Vault, with read access only for BK Replay Recorder (Key Vault Secrets User).
- Firewalls on your storage, database and AI can be closed, except for BK Replay's fixed addresses. BK IT gives you those addresses and the regions that work with them.
GDPR and ownership
- You own the data: it is in your own subscription, under your own management and backup policy. BK IT is the processor.
- You set the retention periods yourself (see General); BK Replay deletes automatically after that.
- Deleting at a data subject's request is possible per call, with a trace in the audit log without content (see Viewing a call).
- Audit log: who viewed, listened to, exported or deleted what is stored in your own database (see Audit log).
- AI: Microsoft does not use data in Azure AI Speech and Azure OpenAI to train models. You choose a European region and an EU data zone for the models yourself.
- Logs at BK IT contain only technical data (IDs, times, error messages): no phone numbers, names or call text.
- Your own reporting: because the database is yours, you can read it with your own tools. BK IT provides stable views and a script to grant read access.
What is at BK IT
- The recording servers and the portal, with a copy of the audio only while a call is in progress.
- Per organisation, the configuration: your tenant ID, the addresses of your resources and the settings from the portal (such as retention periods, the summary instructions and the branding). No call data.
More about access, retention and data subject rights is under Privacy and security.
