1
00:00:03,559 --> 00:00:05,673
Now that we have seen the theory, let's go

2
00:00:05,673 --> 00:00:08,514
in the lab and take a look at the service

3
00:00:08,514 --> 00:00:11,778
health dashboard. I am now in the lab

4
00:00:11,778 --> 00:00:14,313
environment and let me open up Edge here

5
00:00:14,313 --> 00:00:18,232
where I have already logged in the

6
00:00:18,232 --> 00:00:21,799
Microsoft 365 admin center. Now in order

7
00:00:21,799 --> 00:00:23,918
to look at health, it might not show up

8
00:00:23,918 --> 00:00:27,460
when you go to the admin center as part of

9
00:00:27,460 --> 00:00:29,996
your default navigation so you might have

10
00:00:29,996 --> 00:00:32,731
to click Show All at the bottom in order

11
00:00:32,731 --> 00:00:36,209
to see all of the different navigation

12
00:00:36,209 --> 00:00:38,591
elements. Now that we have all of them,

13
00:00:38,591 --> 00:00:41,962
one of the options you will see is health.

14
00:00:41,962 --> 00:00:44,545
So let me click on Health over here, and I

15
00:00:44,545 --> 00:00:48,894
will go into Service health. This is the

16
00:00:48,894 --> 00:00:51,937
service health dashboard. Here I will see

17
00:00:51,937 --> 00:00:54,448
in real time the health status of all

18
00:00:54,448 --> 00:00:57,419
services that are available with my

19
00:00:57,419 --> 00:01:00,022
current subscription. Right now, as you

20
00:01:00,022 --> 00:01:03,060
can see, Exchange Online has one advisory,

21
00:01:03,060 --> 00:01:06,898
Office 365 Portal has two advisories, and

22
00:01:06,898 --> 00:01:10,009
Office for the web has one. All of the

23
00:01:10,009 --> 00:01:13,054
rest of services are healthy and as

24
00:01:13,054 --> 00:01:17,263
incidents are more severe in importance,

25
00:01:17,263 --> 00:01:19,724
they will be at the top. So let me first

26
00:01:19,724 --> 00:01:22,628
of all click on the one advisory for

27
00:01:22,628 --> 00:01:25,389
Exchange Online. I can click into it here,

28
00:01:25,389 --> 00:01:28,092
and you can see that right now, for

29
00:01:28,092 --> 00:01:31,058
Exchange Online users may be unable to

30
00:01:31,058 --> 00:01:33,880
receive voicemails and use both subscriber

31
00:01:33,880 --> 00:01:37,902
access numbers and UM auto attendant. Now

32
00:01:37,902 --> 00:01:41,703
we can also view the history. So if I go

33
00:01:41,703 --> 00:01:45,246
into history here, I will see all of the

34
00:01:45,246 --> 00:01:47,560
latest advisories and incidents that

35
00:01:47,560 --> 00:01:50,953
happened in Office 365. Let's take an

36
00:01:50,953 --> 00:01:54,442
example of this one. Unable to access the

37
00:01:54,442 --> 00:01:57,105
admin portal. If I click into it, I will

38
00:01:57,105 --> 00:02:00,303
see that it started on September 10, at

39
00:02:00,303 --> 00:02:03,999
3:50 p.m., and it ended at September 10,

40
00:02:03,999 --> 00:02:07,184
at 6:00 p.m. I can also view the latest

41
00:02:07,184 --> 00:02:09,562
message so this is information on

42
00:02:09,562 --> 00:02:13,026
Microsoft, which is what is the title,

43
00:02:13,026 --> 00:02:16,122
user impact, more information, and final

44
00:02:16,122 --> 00:02:18,723
status, and I can also view the root

45
00:02:18,723 --> 00:02:22,548
cause, as well as next steps. If I ever

46
00:02:22,548 --> 00:02:25,911
needed, let's say for my change management

47
00:02:25,911 --> 00:02:29,103
or for IT records, I need to have the

48
00:02:29,103 --> 00:02:31,658
history of communications. I can also go

49
00:02:31,658 --> 00:02:34,057
here and see all of the different

50
00:02:34,057 --> 00:02:36,349
communications that Microsoft did

51
00:02:36,349 --> 00:02:39,583
regarding this incident. Now this is a

52
00:02:39,583 --> 00:02:42,191
good one, unable to access admin portal.

53
00:02:42,191 --> 00:02:45,789
What happens if we're unable to access the

54
00:02:45,789 --> 00:02:50,690
admin portal? We go to status.office .com,

55
00:02:50,690 --> 00:02:52,598
and remember that if you go to

56
00:02:52,598 --> 00:02:55,435
status.office .com and you're able to

57
00:02:55,435 --> 00:02:57,861
access the admin portal, chances are

58
00:02:57,861 --> 00:03:00,153
you're going to see what I have here on

59
00:03:00,153 --> 00:03:03,150
the screen right now with that the site is

60
00:03:03,150 --> 00:03:05,943
only updated when service issues are

61
00:03:05,943 --> 00:03:08,150
preventing tenant administrators from

62
00:03:08,150 --> 00:03:11,753
accessing service health in the Microsoft

63
00:03:11,753 --> 00:03:15,116
365 admin center. If SharePoint Online is

64
00:03:15,116 --> 00:03:17,096
down, if any other problem is down, well,

65
00:03:17,096 --> 00:03:20,339
you can still log in to the admin center,

66
00:03:20,339 --> 00:03:22,532
chances are you're not going to see

67
00:03:22,532 --> 00:03:25,110
anything important on this site. This site

68
00:03:25,110 --> 00:03:28,210
is really meant for when you can not log

69
00:03:28,210 --> 00:03:31,937
in the Office 365 admin portal. So those

70
00:03:31,937 --> 00:03:34,051
are the two locations where you can look

71
00:03:34,051 --> 00:03:36,794
at service health. Remember that before

72
00:03:36,794 --> 00:03:40,672
you open a service ticket or if you have a

73
00:03:40,672 --> 00:03:43,593
ton of users, or even a few users only

74
00:03:43,593 --> 00:03:46,248
that have similar problems, it's always a

75
00:03:46,248 --> 00:03:49,276
good idea to look in the service health as

76
00:03:49,276 --> 00:03:51,815
the first location you go to before you

77
00:03:51,815 --> 00:03:54,390
start debugging things, because if it's a

78
00:03:54,390 --> 00:03:56,263
service-wide issue and the problem's on

79
00:03:56,263 --> 00:03:58,289
the Microsoft side, you're not going to be

80
00:03:58,289 --> 00:04:00,990
able to get much done, and it's the same

81
00:04:00,990 --> 00:04:03,595
thing for any Software as a Service; if

82
00:04:03,595 --> 00:04:06,041
the problem is on the provider side, you

83
00:04:06,041 --> 00:04:10,272
need to wait for them to fix it. This is

84
00:04:10,272 --> 00:04:12,241
it for the service health dashboard. Now

85
00:04:12,241 --> 00:04:15,081
let's go back to the slides and talk about

86
00:04:15,081 --> 00:04:21,000
keeping up to date with Microsoft 365 updates.

