If you use Microsoft 365, your CRM lets your Teams channel know.
The infrastructure that carries CRM events into your Teams channel is ready in the product: an outgoing webhook, retries, and a notification step in the visual workflow designer. The Microsoft 365 email connection, on the other hand, is not live today. On this page we set out one by one what is ready, what is a project and what does not exist at all.
IT is asking about one thing, the sales team about another
In a company that has moved to Microsoft 365, Teams is not a single application; it is the company's desk. Meetings happen there, files sit there, the team writes to one another there. When new software comes up for discussion, the question IT asks follows from that: does this thing come into our world? This is the picture we see in our own implementation meetings:
- In the Monday meeting, last week's numbers are shown by screen sharing; nobody looks at the report on their own, and what was looked at disappears along with the meeting.
- Sales news is typed into the channel by hand. The “we closed this one” message depends on one person remembering; if it is forgotten, there is no news either.
- Correspondence with the customer sits in Outlook, internal correspondence in Teams, and the record somewhere else. The only way to move data between three windows is to copy it; what moves is not the record itself but a copy of the text.
- Appointments are kept in the calendar but are not tied to the record in the CRM; the question “when did we last speak to this customer?” is answered by searching the calendar.
- IT is asking about enterprise sign-in and permission management; the sales team wants notifications. The two sides ask different things in the same meeting, and the vendor says “yes” to both at once.
This page splits that “yes” apart, one item at a time. On the Microsoft side there is something that can be built, and there are things that do not exist at all. We do not put the two in the same sentence.
Three separate sentences: what is live, what gets built and what does not exist
There is no out-of-the-box module for Microsoft Teams, and we will not say there is one. The connection is built as an integration project whose scope is set in the discovery call, using the REST API, webhooks and import/export.
In the notification direction the situation is better: the outgoing webhook infrastructure is complete in the product. Your system can verify each notification came from us, a notification that does not arrive is retried, the target address is validated, and it sits as a step in the visual workflow designer. That is why getting a CRM event into your Teams channel is a job to be configured, not written. This feature is new; if your decision depends on it, let's try it together in a demo.
On the Microsoft 365 side, email is not live today. The Outlook and Microsoft 365 connections are not open, so a Microsoft 365 mailbox cannot be connected to the CRM. We wrote the detail of this in its canonical place, on the email integration page, and we do not repeat it here.
The calendar is not on this page, because it is not in the product either. There is no Outlook calendar sync: the Microsoft 365 connection is not live today, so neither the email nor the calendar side works. Calendar sync is specific to the Google side only. It would have been easy to put the calendar under a “Microsoft 365 integration” heading as well; we are not doing that, because a gap that surfaces on implementation day costs more than a sentence said before the sale.
The reverse direction (creating a record in the CRM from Teams) is written over the REST API. The API is usable from the outside: ERP integrators can read and write records through this same REST API. The same framework applied to an ERP is on the Netsis integration page, and our general approach is on the integrations page.
Monday, 09:10. The weekly sales meeting is starting. Once the connection is in place, this is what changes:
-
1
The week's numbers are in the channel before the meeting
Closed opportunities and new leads land in the channel event by event. The meeting opens with making decisions, not with recounting the past.
-
2
The announcement no longer depends on one person remembering
On the opportunity-won event, a notification goes to the channel by itself. Nobody forgets to announce it; nobody writes the same news twice.
-
3
You go from the notification to the record itself in one step
The message carries the fields you defined in the scope (customer, amount, owner) and the address of the record. Everyone looks at the same record without waiting for a screen share.
-
4
Notification volume is limited by conditions
Because the notification is a workflow node, conditions and filters can be placed in front of it, for example only opportunities above a certain amount. The channel does not turn into a noticeboard.
The surface you rely on for the Microsoft side
Notification to the channel
On record creation and change events a notification goes to the receiving system, which can verify it came from us and reject forged ones.
Conditional notification node
The notification is a node in the visual workflow designer. Which record is announced under which condition is defined without writing code.
Microsoft 365 email: not live
The Outlook and Microsoft 365 connections are not open today, so a Microsoft 365 account cannot be connected. Generic IMAP/SMTP is not supported either.
Access without sharing passwords
Access is granted with permissions; no connection is made by sharing a user password. You can withdraw the permission just as you granted it.
Enterprise sign-in: OIDC yes, SAML no
OIDC is wired into the product and supported; we do not offer SAML. OIDC is configured during setup; if your decision depends on it, let's try it together in the demo.
REST API for the reverse direction
If you want to create records in the CRM from Teams, this is the surface you rely on: every record in the CRM can be read and written through the REST API, and you can read the field structure from outside.
What exists and what does not on the Microsoft side
| Topic | What exists today | How it is set up |
|---|---|---|
| CRM → notification to a Teams channel | Outgoing webhook, retries, target address validation and a workflow step are ready in the product | The subscription and the event–channel mapping are configured during implementation; no code is written |
| Microsoft 365 email | Not live today; the Outlook and Microsoft 365 connections are not open | We do not offer it. A Microsoft 365 account cannot be connected; the detail is on the email integration page |
| Outlook calendar | None. The Outlook and Microsoft 365 connections are not live today; there is neither email nor calendar sync | We do not offer it. If you need appointment sync, the only route that works today is Google Calendar |
| A CRM tab or app inside Teams | None; we have no interface embedded inside Teams | We do not offer it. The link in the notification takes you to the record itself, and the screen opens in the CRM |
| Teams chat being written to the customer record | None; the messaging channel list is closed: email, WhatsApp Business API, WhatsApp QR pairing and SMS | If you want correspondence to land on the record, the route that works today is the WhatsApp Business API. WhatsApp QR pairing is not the official API and carries the risk of the number being restricted; we do not offer it as a product promise |
| Automatic transcription of a Teams meeting | None; we have no connection that pulls the meeting in by itself | Uploading an audio recording to the CRM and producing a transcript and a summary is a separate matter; it is written up, with its limits, on the Zoom page |
What we have verified
How is the Microsoft side brought live?
-
1
Discovery
We work out who administers your Microsoft 365 account and which channels will be fed. We recommend that your IT lead is in this meeting.
-
2
Scope and event list
The event–channel mapping, the fields that will appear in the message and the noise limit are put in writing. The document also states that the calendar and Microsoft 365 email are out of scope, so there are no surprise line items.
-
3
Configuration and testing
The webhook subscription is defined and verification is tested on the receiving side. Test notifications are sent with sample events.
-
4
Training and go-live
Team training and close follow-up in the first week. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The notification side goes live with that plan.
Scope and setup terms
What the Microsoft connection covers today:
- Teams receives CRM notifications. Teams notification is new; if your decision depends on it, let's try it together in a demo.
- Microsoft 365 and Outlook email are not connected today. A Microsoft 365 account cannot be connected to the CRM, and we do not give a date for it.
- Calendar sync works on the Google side. Because the Microsoft 365 connection is not live today, there is no Outlook calendar sync.
- Notification links open the record in the CRM. There is no CRM tab or app inside Teams and no listing from us in the app store.
- Conversations are linked to records through the WhatsApp Business API and email. Teams chats do not land on the customer record; the messaging channels are email, WhatsApp Business API, WhatsApp QR pairing and SMS.
- WhatsApp QR pairing comes with a caveat. The same inbox can also be connected this way, but the method is not Meta's official API and carries the risk of the number being restricted by Meta. The route we recommend is the official Cloud API; if you still prefer QR pairing, we share the risk in writing and take the decision together. The detail is on the WhatsApp integration page.
- Meeting recordings are uploaded to the CRM. Teams meetings do not land in the CRM by themselves; producing a transcript and a summary from an audio recording is a separate flow, described with its limits on the Zoom integration page.
- Stock sync, a self-running order → invoice → collection chain and manufacturing/MRP automation are outside the scope. The reasons, and what can be done instead, are in one place: scope and setup terms.
Enterprise sign-in: OIDC is supported in the product and configured during setup; SAML is not available. If your decision depends on it, let's try it together in the demo. Two-factor authentication (TOTP, email code and backup codes), on the other hand, works and is mandatory for the admin account's web login.
Data location: your data is held in the European Union: the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no such feature as region selection. When you connect an email account, the mailbox itself continues to sit on the provider's side. This is a transfer abroad under Article 9 of the KVKK; we establish its legal basis together during the contract process. The detail is on the security page and in the KVKK privacy notice.
Certification: we do not hold an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment questionnaires and describe the architecture in writing.
Plan prices are in the open; scope comes out in discovery
The scope of Teams notifications, and their cost if any, are worked out in the discovery call and shared in writing. Plan prices and separately priced items, on the other hand, we publish on a single page with the figures.
Three plans, a scope table and separately priced items on a single page.
Frequently asked questions about the Teams integration
Does Rapitek CRM integrate with Microsoft Teams?
Does Rapitek CRM have a ready-made Teams app or tab?
Can we connect our Microsoft 365 account to the CRM?
Will our Outlook calendar sync with the CRM?
Do our Teams meetings land in the CRM automatically?
Do Teams chats land on the customer record?
Which events can be announced from the CRM to a Teams channel?
Are the notifications secure?
Can we create records in the CRM from Teams?
Can we do enterprise sign-in (SSO) with Microsoft Entra?
How mature is the Teams notification?
How long does implementation take, and is it included in the plan price?
Where is our data held?
Can we see it before buying?
Let us settle the Microsoft side in 30 minutes
In the intro call let us show, on your own scenario, how the channel notification is built; let us write the scope and the limits together. Then we open your 7-day trial account; no credit card required.
