Microsoft Teams
The same recall problem as any chat platform, in the tenant most Saudi enterprises already run.
The same recall problem as any chat platform, in the tenant most Saudi enterprises already run.
What Microsoft Teams holds, and why that matters here
Where an organisation is standardised on Microsoft, Teams is usually the place internal conversation happens — and the place it becomes unfindable. The dynamic is the same as any chat tool: what was decided is in a thread, and the thread is gone.
The advantage over connecting a separate platform is that identity is already settled. The same tenant that governs who can open a file governs who can read a channel, so the assistant inherits one permission model rather than reconciling two.
The same caution applies as anywhere else: membership decides what an answer may draw on, and chats are outside scope. People speak differently in a private channel, and a tool that ignores that has misunderstood what it was given access to.
- Channel messages — within the teams the asker belongs to.
- Threads — the reasoning, not only the outcome.
- Files shared in channel — inside the same boundary.
- Meeting notes — where your organisation keeps them in channel.
- Identity — inherited from the tenant, not maintained separately.
Questions Teams channels let Elbi answer
What was decided here?
The thread, within the asker's own teams.
Has this come up before?
Prior discussion instead of asking again.
Where is that document?
Shared files, within the same permissions.
Who is working on this?
What the channel record shows.
What came out of that meeting?
Notes, where they are kept in channel.
Which team owns this?
Routing, so the question is asked once.
How Elbi reads Microsoft Teams
- Channels, not chatsElbi reads messages in the channels of the teams you choose. One-to-one chats, group chats and meeting chats stay out of scope, which confines the connection to the part of Teams people already treat as shared.
- Access through your own tenantReading runs through Microsoft Graph under an app registration in your Entra tenant, with read permissions your administrator grants and can review at any time.
- Membership is checked at the channelTeam membership is not the whole story. Private channels have their own membership inside a team, and shared channels can include people from other teams or organisations. An answer draws only on channels the asker belongs to.
- Files follow SharePoint's rulesFiles posted in a channel live in the team's SharePoint site; files shared in chats live in the sender's OneDrive. Channel files are answered under the same permissions as any other SharePoint document.
- Threads are read wholeA reply means little without the message it answers. Answers draw on the thread as a whole, so "we agreed to push it back" is understood alongside what was pushed back and who agreed.
- Posting is off unless you enable itBy default Elbi only reads. Posting into a channel is a separate permission, switched on only if you decide it serves a clear purpose.
Scope and control on a Teams connection
| Direction of access | Read by default. Channel messages and channel files are read to answer questions; nothing is posted, edited or deleted unless you enable posting for a defined purpose. |
|---|---|
| Who can see what | Channel membership, including private and shared channels, decides what each answer may draw on. Chats are excluded entirely. |
| Credentials | The app registration and its credential sit in your Entra tenant. You rotate the credential, remove teams from scope or withdraw consent, and each change takes effect without us. |
| Where data goes | No copy of your Teams content is made; messages are read to answer the question in front of Elbi. The content of Elbi's own conversations is destroyed within 24 hours, most often when the conversation ends, and no external AI service sees it. |
| Audit | Each lookup can be recorded — which channel was read, for which asker, in which conversation — alongside the audit records Microsoft Purview already keeps for your tenant. |
| If Teams is unreachable | Elbi says it cannot check the channel and does not reconstruct a discussion from memory. |
What this replaces
What this replaces is the same repeated question — asked in a channel, unanswered, asked again elsewhere, finally answered from memory by whoever was there.
It also cuts the specific waste of onboarding, where a new joiner needs context that genuinely exists but is spread across threads they cannot search effectively. That is a retrieval problem, and it is worth solving without asking anyone to write a new document.
It does not replace documentation, and should not. Policy belongs in approved material; chat is evidence of a conversation. Keeping those separate is what stops an assistant citing an offhand remark as though it were a rule.
Who gets most from a connected Teams
Microsoft estates
One tenant, one permission model, no second identity list.
Project teams
Decisions with the discussion that produced them.
Support
What was said to a customer, where it was said.
New joiners
Context that exists but was never documented.
Operations
Updates posted once and scrolled away.
Internal IT
Fewer repeated questions reaching the same few people.
Getting value from Teams
Start with one team whose channels already carry decisions people need later — a project team, an operations team, an internal IT support channel — and whose members agree to the pilot. The first useful questions are usually "what did we decide about…" and "has anyone dealt with this before", which today end with someone scrolling or asking again.
Onboarding comes next. New joiners need the context behind current work, and it sits in threads they were never part of. Being able to ask where a decision came from, and be shown the thread that produced it, shortens the period of asking around that most people accept as normal.
Keep policy out of it. When a channel message and an approved document disagree, the document wins. Teams is best connected alongside your policy sources, not instead of them.
What connecting Microsoft Teams involves
- Choose the teams and channelsName the first team and decide whether its private channels are included. Starting narrow keeps the review short and the expectations clear.
- Tell the membersPeople write differently when they know a channel may be used to answer colleagues' questions. A short note to the team before launch is both fair and useful.
- Grant read accessYour administrator registers the application and grants read permissions for the chosen teams. The permission list stays visible and reviewable in your tenant.
- Decide on files and meeting notesChannel files come from the team's SharePoint site; meeting notes and transcripts depend on where your organisation keeps them. Include each deliberately.
- Agree how guests are treatedGuests, and people from other organisations in shared channels, see what their membership allows in Teams. Decide whether they may use Elbi at all before they find out by asking.
- Test with edited and deleted messagesEdit one message, delete another, remove someone from a private channel, then check that answers reflect the channel as it stands now.
Channel messages and the PDPL
Channel messages are full of personal data about people other than the asker: colleagues named in discussions, customers mentioned by name, phone numbers pasted into threads, the occasional personal remark. Under the Personal Data Protection Law, using those messages to answer someone else's question is processing, and the people who wrote them are data subjects too.
That makes transparency more important here than in most connections. Staff should know which teams are connected and for what purpose, and teams that routinely discuss individual customers, employees or cases should be connected only where the purpose clearly justifies it.
Your Microsoft Purview retention and deletion policies continue to govern Teams itself. Reading a message to answer a question does not extend its life: once a message is deleted under your policy, it is no longer there to answer from.
What organisations typically see
How Copilot and other tools approach Teams
Copilot in Teams, part of Microsoft 365 Copilot, summarises chats, channel conversations and meetings for the licensed user, within that user's own access. For catching up on one's own conversations and meetings, that is exactly what it is designed for.
Elbi's Teams connection is narrower by design: channels only, no private chats, and answers drawn from shared team knowledge rather than one person's conversations. It tends to suit organisations that want one assistant answering from Teams, from approved documents and from other systems, with a clear line between discussion and policy.
The other familiar approach is exporting channels into a wiki or knowledge base. The result is tidier, but someone has to produce it, and an export starts ageing the day it is made.
Common questions
Yes, and this is the point. The tenant already governs who may read what; the assistant inherits that rather than keeping its own view of it.
No. One-to-one and group chats are out of scope, and we would recommend leaving them there.
Yes, and we suggest it. A narrow first scope makes the review straightforward.
Only if you turn that on. Reading is where the value is.
No copy is made. Content is read to answer the question in front of it.
By default it does not, and it should not. Policy comes from your approved documents; a channel message is a conversation, not a rule.
Only if you include them, and then only for their members. Private and shared channels have their own membership, checked separately from the parent team.
They are stored in OneDrive or SharePoint rather than in the channel itself, so including them is a separate decision, made team by team.
Only if you decide they should. Guests can read the channels they belong to in Teams, but access to an internal assistant is a separate policy choice.
Find what your teams already decided
Elbi answering from your Teams channels, in Arabic and English, within the membership your tenant already enforces.