1
00:00:02,508 --> 00:00:05,098
Let's start by doing an introduction to

2
00:00:05,098 --> 00:00:09,467
Microsoft 365 User Profiles. First of all,

3
00:00:09,467 --> 00:00:12,593
what is the user profile? The user profile

4
00:00:12,593 --> 00:00:15,451
is really all of the different properties

5
00:00:15,451 --> 00:00:19,475
or metadata around the user. You have

6
00:00:19,475 --> 00:00:21,358
mandatory properties such as username and

7
00:00:21,358 --> 00:00:24,457
the name of the user which is already

8
00:00:24,457 --> 00:00:26,802
there for every user, but also some

9
00:00:26,802 --> 00:00:30,642
optional ones such as department, manager,

10
00:00:30,642 --> 00:00:35,325
office, phone number, and so on. Now where

11
00:00:35,325 --> 00:00:38,592
is this information stored? It's in fact

12
00:00:38,592 --> 00:00:42,340
stored into three places; in Azure Active

13
00:00:42,340 --> 00:00:45,608
Directory, Exchange Online, and SharePoint

14
00:00:45,608 --> 00:00:47,895
Online. If we look at the diagram, let's

15
00:00:47,895 --> 00:00:51,156
take for example first of all a cloud-only

16
00:00:51,156 --> 00:00:53,554
user. Most of the information will be

17
00:00:53,554 --> 00:00:57,158
inside Azure Active Directory. So

18
00:00:57,158 --> 00:00:59,446
information such as username, password,

19
00:00:59,446 --> 00:01:01,759
department, manager, and really most of

20
00:01:01,759 --> 00:01:05,480
the information on that user. Some

21
00:01:05,480 --> 00:01:08,554
information such as the profile picture is

22
00:01:08,554 --> 00:01:11,507
stored into Exchange Online. SharePoint

23
00:01:11,507 --> 00:01:14,800
Online also has its own user profile where

24
00:01:14,800 --> 00:01:19,134
information gets synced from Azure AD in a

25
00:01:19,134 --> 00:01:21,834
one-way only, and SharePoint Online has

26
00:01:21,834 --> 00:01:25,050
additional information in the profile not

27
00:01:25,050 --> 00:01:28,867
existing into Azure AD such as skills,

28
00:01:28,867 --> 00:01:34,004
About Me, birthday, schools, and so on.

29
00:01:34,004 --> 00:01:36,301
Now if you have a hybrid architecture, as

30
00:01:36,301 --> 00:01:39,093
a lot of enterprises do where as they

31
00:01:39,093 --> 00:01:41,634
still have an Active Directory

32
00:01:41,634 --> 00:01:44,778
on-premises, that is the main source of

33
00:01:44,778 --> 00:01:47,031
profile information, but that gets

34
00:01:47,031 --> 00:01:50,177
synchronized to Azure AD through Azure AD

35
00:01:50,177 --> 00:01:53,156
Connect or other sync engines that you

36
00:01:53,156 --> 00:01:56,524
might be using, but why is the user

37
00:01:56,524 --> 00:01:59,100
profile so important? Why do we need to

38
00:01:59,100 --> 00:02:02,959
take care of it? First of all, a lot of

39
00:02:02,959 --> 00:02:06,122
Microsoft 365 experiences depend on the

40
00:02:06,122 --> 00:02:09,187
user profile. To give you an example, it

41
00:02:09,187 --> 00:02:12,196
lets you have a workflow with manager

42
00:02:12,196 --> 00:02:14,132
approval. Well, flow that you're probably

43
00:02:14,132 --> 00:02:17,755
going to use for that workflow cannot

44
00:02:17,755 --> 00:02:19,900
automatically guess the manager of the

45
00:02:19,900 --> 00:02:23,422
user. It comes from that user's profile.

46
00:02:23,422 --> 00:02:26,569
If it's not in there, that workflow will

47
00:02:26,569 --> 00:02:29,133
fail. Other examples include the your team

48
00:02:29,133 --> 00:02:31,826
calendar, which is based on a common

49
00:02:31,826 --> 00:02:35,248
manager, or the company directory and work

50
00:02:35,248 --> 00:02:37,305
chart where people would go to find your

51
00:02:37,305 --> 00:02:40,077
phone number, find information about what

52
00:02:40,077 --> 00:02:44,241
office are you on, and so on. There are

53
00:02:44,241 --> 00:02:47,633
also a lot of new experiences, which I

54
00:02:47,633 --> 00:02:50,082
will call intelligent as Microsoft calls

55
00:02:50,082 --> 00:02:53,916
them, that depend on your user profile.

56
00:02:53,916 --> 00:02:56,197
For example, a lot of the dove

57
00:02:56,197 --> 00:02:58,695
recommendations on relevant content, all

58
00:02:58,695 --> 00:03:00,958
of this is made better by the information

59
00:03:00,958 --> 00:03:03,604
in the user profile, because it can say,

60
00:03:03,604 --> 00:03:05,780
hey, it looks like everybody from your

61
00:03:05,780 --> 00:03:08,408
department or a lot of people from your

62
00:03:08,408 --> 00:03:11,038
department have read this document in the

63
00:03:11,038 --> 00:03:13,560
past two days. So I'm going to push it to

64
00:03:13,560 --> 00:03:16,806
you because it must be relevant to you, or

65
00:03:16,806 --> 00:03:19,632
similar things like that, all of those

66
00:03:19,632 --> 00:03:25,000
connections enhance those intelligent experiences.