Platform Banner

Copilot (licence) - Choosing Copilot or connecting an external AI in Microsoft 365? Tutorial

Choosing Copilot or connecting an external AI in Microsoft 365? reveals that the debate isn’t just about performance, but how deep the integration goes. Copilot taps directly into the Microsoft 365 environment, using existing identities and permissions to work within your security model, while external AIs require linking separate environments, added governance, and ongoing administration. The video guides you through data access, permissions, and administration nuances, showing how an external AI might copy, share, and process content, versus the seamless, governed approach of Copilot. If you want a clear sense of which path fits your organization’s governance and integration needs, this comparison breaks down the structural implications behind each choice.

02:37
140 views
Parteger

Available in AI - Artificial Intelligence

00:00:04

the question is not just which AI to choose,

00:00:07

but how to integrate it

00:00:09

into the work environment.

00:00:10

There are two main approaches.

00:00:13

Activate an AI built into Microsoft 365

00:00:17

or connect an external AI

00:00:19

to the ecosystem.

00:00:21

Co-pilot represents

00:00:22

the integrated approach.

00:00:24

An external AI like chat GPT or a connected open AI solution

00:00:30

represents the added approach.

00:00:31

This design difference

00:00:33

changes how data is accessed,

00:00:35

how permissions are managed,

00:00:37

and how the solution is administered.

00:00:40

With an external AI connected to Microsoft 365,

00:00:44

2 separate environments

00:00:46

must be linked.

00:00:47

The user copies and pastes a Word document,

00:00:50

shares an Excel file from OneDrive,

00:00:53

or grants access

00:00:54

to specific content.

00:00:56

The AI only processes

00:00:58

what is explicitly shared or made accessible

00:01:02

through this connection.

00:01:03

This integration must be configured,

00:01:06

authorized,

00:01:07

and managed.

00:01:08

It is added to the existing system like a third party application.

00:01:13

It usually respects

00:01:14

the user's permissions,

00:01:16

but it creates an additional layer to manage for the organization.

00:01:20

Co-pilot follows a different logic.

00:01:22

It does not connect two separate systems.

00:01:25

It works directly

00:01:27

within the Microsoft environment

00:01:29

using existing identities

00:01:31

and permissions.

00:01:33

It only accesses

00:01:35

content the user already has.

00:01:37

No more,

00:01:38

no less,

00:01:39

it requires no additional external connection

00:01:43

and fits within

00:01:45

the existing architecture and rules.

00:01:48

So the difference is not just about the tool

00:01:50

but about integration responsibility

00:01:53

with an external AI,

00:01:55

the company must manage

00:01:57

an extra connection,

00:01:58

defined permissions,

00:02:00

control access,

00:02:01

and administer a third party application.

00:02:04

With co-pilot,

00:02:05

the AI relies directly on the security model already in place

00:02:10

in Microsoft 365.

00:02:12

So the choice becomes structural.

00:02:14

Do you add a solution?

00:02:16

That needs governance

00:02:17

or activate a capability

00:02:20

already governed.

00:02:21

Comparing AI tools

00:02:23

only on performance is not enough.

00:02:26

In a business context,

00:02:27

you also need to understand

00:02:29

how they integrate.

00:02:31

A connected application

00:02:33

or intelligence built directly

00:02:35

into the system.

Mandarine AI: WHAT YOU SHOULD KNOW

RELATED COURSES This tutorial is part of the following courses

E-learning Débutant

Vu 62 fois

Adopt Copilot in your enterprise ? Trust, Data and Value

Understand how Copilot integrates with Microsoft 365, protects data, and transforms the use of AI in the enterprise.

ALL COURSES