WEBVTT
00:00:00.540 --> 00:00:05.260
Anyway, let's get things going
and talk about cloud nirvana.
00:00:05.310 --> 00:00:11.570
I mean that's what the cloud is,
isn't it? You guys, all you
00:00:11.620 --> 00:00:15.890
guys professionals, what
does professionals mean?
00:00:16.880 --> 00:00:18.310
Are you all professionals?
00:00:19.450 --> 00:00:22.890
Yeah, you get paid for it so you
must be professionals. I presume
00:00:22.940 --> 00:00:27.490
you're interested in the transition
from on premises Exchange.
00:00:27.540 --> 00:00:29.630
Are you looking for good reasons
why you are not going to go
00:00:29.680 --> 00:00:31.280
to the cloud? That's
why you are here.
00:00:31.940 --> 00:00:35.920
We'll talk a lot about all the
things that you need to figure
00:00:35.970 --> 00:00:38.920
out, factor into your
transition plan.
00:00:40.660 --> 00:00:41.290
To begin,
00:00:43.800 --> 00:00:45.490
do you remember Exchange 4.0?
00:00:47.290 --> 00:00:50.990
Anybody? It was good, wasn't it?
00:00:53.430 --> 00:00:56.400
Especially when you install it
on Pentium-class systems.
00:00:57.610 --> 00:00:58.260
That was fun.
00:01:00.340 --> 00:01:05.720
The one great thing 4.0 did a long,
long time ago, 19 years ago,
00:01:06.530 --> 00:01:10.080
is it proved Microsoft's credentials
in the enterprise.
00:01:10.440 --> 00:01:13.590
Because up to that point in time
Microsoft was essentially a
00:01:13.640 --> 00:01:17.290
desktop company, a PC company,
Excel, Word et cetera.
00:01:17.850 --> 00:01:22.150
But then Exchange 4.0 came out
and it was so much better then
00:01:22.200 --> 00:01:26.680
MS Mail and people turned around
and said these guys can actually
00:01:26.730 --> 00:01:28.440
build enterprise applications.
00:01:30.890 --> 00:01:32.950
Nineteen years ago Exchange 4.0
00:01:34.210 --> 00:01:39.100
help to launch Microsoft into the
enterprise space and now Exchange
00:01:39.150 --> 00:01:44.750
Online is helping prove the same
kind of credentials in the cloud
00:01:44.800 --> 00:01:47.950
because e-mail is the easiest workload
to move to the cloud.
00:01:48.610 --> 00:01:51.360
It's the reason why an awful lot
of people are moving to the
00:01:51.410 --> 00:01:54.710
cloud and it's very successful
in the cloud.
00:01:56.050 --> 00:02:02.000
In short, Exchange is the gateway
drug to the cloud.
00:02:02.050 --> 00:02:06.670
And it's gathering pace, this move.
00:02:07.190 --> 00:02:09.270
And there are many, many influences.
00:02:10.210 --> 00:02:13.280
Some of it is because of the enormous
investment that Microsoft
00:02:13.330 --> 00:02:15.790
is making in spreading data
centers around the world.
00:02:16.420 --> 00:02:23.170
Recent additions for Office 365 were
in Austria in Vienna and Finland.
00:02:24.370 --> 00:02:25.070
That's good.
00:02:26.110 --> 00:02:31.860
I think also we've got much better network
bandwidth, generally speaking.
00:02:31.910 --> 00:02:34.140
I mean there are some parts of the
world where you still can't
00:02:34.190 --> 00:02:37.410
get decent bandwidth, but generally
speaking the vast bulk of
00:02:37.460 --> 00:02:40.760
the world is better connected than
ever before. And you've got
00:02:40.810 --> 00:02:45.360
things like Express Route and things
like that are coming and
00:02:45.410 --> 00:02:49.510
making it easier to get data over
to the cloud. I think then
00:02:49.560 --> 00:02:52.090
also there is no doubt that we
have had a lot of opportunity
00:02:52.140 --> 00:02:56.730
to learn about the cloud, and this
means that most large corporations
00:02:56.780 --> 00:03:00.250
now have actually signed up to become
one of the over 1 million
00:03:00.300 --> 00:03:02.660
cloud tenants in Office 365.
00:03:03.320 --> 00:03:07.490
They may not be using it, but they
are sniffing at the edges.
00:03:07.540 --> 00:03:08.490
They're interested.
00:03:09.440 --> 00:03:12.690
And they're interested because
generally speaking within the
00:03:12.740 --> 00:03:16.060
industry, people are
saying this works.
00:03:16.900 --> 00:03:18.310
And economics work.
00:03:19.360 --> 00:03:23.570
I tweeted something the other day
when Perry Clark talked about
00:03:23.620 --> 00:03:28.480
this in the Office 365 inside the
curtain session. He said that
00:03:28.530 --> 00:03:29.380
in his view
00:03:30.710 --> 00:03:35.360
a mailbox in Office 365 is always
going to be cheaper than it
00:03:35.410 --> 00:03:36.870
is on premises.
00:03:37.990 --> 00:03:41.790
And he's actually right, because
when you nest out all of the
00:03:41.840 --> 00:03:45.860
costs of delivering something like
a 50 gigabyte mailbox and
00:03:45.910 --> 00:03:51.710
100 gigabyte archive and all of
the other functionality that's
00:03:51.760 --> 00:03:55.310
in Office 365 and you compare it
to what it would cost you to
00:03:55.360 --> 00:03:58.050
provide that on prem,
00:03:59.610 --> 00:04:01.000
it's a hard, hard
00:04:02.500 --> 00:04:06.700
case to make that on prem is going
to be cheaper, because it's not.
00:04:07.390 --> 00:04:12.290
The scale that Microsoft buys hardware,
the scale that they operate
00:04:12.340 --> 00:04:17.670
at allows them to get down to a
point where a gigabyte of data
00:04:17.720 --> 00:04:21.440
to them costs a couple
of pennies per month.
00:04:23.740 --> 00:04:25.630
You can't operate at
that kind of scale.
00:04:27.590 --> 00:04:30.820
I think another important thing
is that the SLA performance is
00:04:30.870 --> 00:04:33.380
generally Excellent. Now there
have been big outages.
00:04:33.430 --> 00:04:34.790
There's no doubt about that.
00:04:35.790 --> 00:04:40.190
By big I mean well-publicized outages,
such as the one last July
00:04:41.200 --> 00:04:44.470
when parts of the United States,
in particular were affected.
00:04:44.520 --> 00:04:45.980
But let me tell you this.
00:04:47.590 --> 00:04:50.280
Because Office 365 is now so big
00:04:51.540 --> 00:04:57.480
that even an outage that might
affect 100,000 mailboxes is no
00:04:57.530 --> 00:05:03.550
more than a little insignificant
blip in the overall performance
00:05:03.600 --> 00:05:04.660
of the service.
00:05:05.510 --> 00:05:09.570
Generally speaking, and I have been
in Office 365 user for the
00:05:09.620 --> 00:05:13.810
last four years, I've received
nothing but Excellent service.
00:05:13.860 --> 00:05:20.730
I could not make on prem Exchange run
at the same kind of service level.
00:05:20.780 --> 00:05:26.820
I couldn't simply because updating
a DAG member server is so
00:05:26.870 --> 00:05:29.420
destructive, something like
that, simple stuff.
00:05:29.980 --> 00:05:32.130
And don't get me going
about server security.
00:05:33.660 --> 00:05:34.700
They are disruptive.
00:05:35.880 --> 00:05:38.320
And then, of course, you've got these
pundits. Who are these pundits?
00:05:38.370 --> 00:05:41.630
Does anybody know what the word pundit
means or where it came from?
00:05:45.400 --> 00:05:46.270
Fox News.
00:05:50.270 --> 00:05:54.010
Is there a Republican supporter
here? Can we have him removed?
00:05:57.740 --> 00:06:01.200
He's making jokes, okay. That's good.
You can Tweet that. That's good.
00:06:01.250 --> 00:06:06.120
I'll give you that. Pundit is actually
a name that comes from India.
00:06:06.170 --> 00:06:09.010
It comes from India and
it's a wise person.
00:06:10.230 --> 00:06:13.840
The pundit, no. It's not
Fox News. You're right.
00:06:15.310 --> 00:06:20.200
Anyway, these wise people have now
said that Office 365 is okay,
00:06:20.250 --> 00:06:23.870
so it's okay. Once you've got approval,
your CIOs will be reading
00:06:23.920 --> 00:06:26.080
about this in the newspapers.
00:06:26.770 --> 00:06:33.600
We know how dangerous an article was
in the hands of a reckless CIO.
00:06:37.020 --> 00:06:39.750
Anyway, some news about the
current public status.
00:06:41.830 --> 00:06:46.600
This is frustrating to me. Microsoft
won't tell me how many mailboxes
00:06:46.650 --> 00:06:47.900
they are actually running.
00:06:49.940 --> 00:06:53.150
It's competitive information. It's
confidential. But you know what?
00:06:53.200 --> 00:06:56.710
They have to tell the SEC how much
money they're making out of it.
00:06:56.760 --> 00:06:59.040
So the only way you can actually
go interpret this and this is
00:06:59.090 --> 00:07:01.600
what I do. I've been doing it for
the last couple of years is
00:07:01.650 --> 00:07:05.690
you take the financial run rate, the
annual run rate for commercial
00:07:05.740 --> 00:07:09.200
cloud services, which is right
now according to quarter three
00:07:09.250 --> 00:07:14.400
fiscal '15 results,
6.3 billion a year.
00:07:16.170 --> 00:07:17.230
That includes Azure
00:07:18.700 --> 00:07:22.660
and it includes Dynamics CRM, but
I reckon a good chunk of it
00:07:22.710 --> 00:07:24.350
is Office 365.
00:07:25.410 --> 00:07:28.480
And then you have to figure out
how much an average subscriber
00:07:28.890 --> 00:07:33.160
is paying for Office 365 per month,
and you divide it into that
00:07:33.210 --> 00:07:34.150
big number.
00:07:35.190 --> 00:07:37.670
Right now I figure
00:07:39.210 --> 00:07:42.450
that between 80 and 90 million,
maybe 100 million, it depends
00:07:42.500 --> 00:07:47.780
on how many academic, free and school
mailboxes are there, but
00:07:47.830 --> 00:07:51.910
I think there's quite a lot of mailbox
there. Here's the thing.
00:07:51.960 --> 00:07:56.030
You guys that are all the on prem
community, you are still in
00:07:56.080 --> 00:07:56.900
the majority.
00:07:57.930 --> 00:08:00.880
And you are still going to be in
the majority or at least another
00:08:00.930 --> 00:08:01.690
two years.
00:08:02.530 --> 00:08:07.260
After that, I can't tell because a
lot of it depends on the velocity
00:08:09.020 --> 00:08:13.620
that Office 365 maintains. If he
keeps on going the way it is,
00:08:13.670 --> 00:08:17.750
the tipping point could be sooner.
On the other hand, if let's
00:08:17.800 --> 00:08:21.640
say Exchange 2016 comes out and
is a roaring success from the
00:08:21.690 --> 00:08:26.090
get-go, you might all migrate overnight
and say we are happy
00:08:26.140 --> 00:08:31.270
campers and it might take a little
bit longer, but the salient
00:08:31.320 --> 00:08:37.410
facts are that Office 365 is doing
extremely well and is accumulating
00:08:37.460 --> 00:08:41.190
mailboxes fast, at a very
significant rate.
00:08:42.790 --> 00:08:45.670
Let's talk a little bit about
Exchange Online itself.
00:08:46.930 --> 00:08:53.460
Let's try to identify what's different
than on prem. I'm sure
00:08:53.510 --> 00:08:55.800
you've heard the fact
00:08:57.010 --> 00:09:02.600
often repeated that Exchange Online
and Exchange on prem are
00:09:02.650 --> 00:09:03.780
kissing cousins.
00:09:05.380 --> 00:09:08.640
They share the same code base.
00:09:09.680 --> 00:09:10.350
Yeah, they do,
00:09:11.850 --> 00:09:16.460
but there's a lot of little if then
else's in there because when
00:09:16.510 --> 00:09:21.410
you think about it a massively scalable
multitenant environment
00:09:21.890 --> 00:09:24.400
is very, very different than the
kind of on prem environment
00:09:24.450 --> 00:09:25.030
that you've run.
00:09:25.830 --> 00:09:29.560
And Exchange 2013 and Exchange
2016 are going to have to deal
00:09:29.610 --> 00:09:30.220
with that.
00:09:31.770 --> 00:09:33.500
Exchange Online, what you get today,
00:09:34.860 --> 00:09:37.740
let's say if you went and
started off Outlook
00:09:39.110 --> 00:09:40.080
were back today.
00:09:40.630 --> 00:09:42.560
You log on to your tenant.
00:09:43.600 --> 00:09:44.540
Have a look at the URL
00:09:45.750 --> 00:09:49.410
and you probably see tacked onto
the end of the URL a little
00:09:49.460 --> 00:09:53.890
version string and the version string
might just start with 16.
00:09:55.960 --> 00:10:00.570
Exchange Online is already running
code that will be delivered
00:10:00.620 --> 00:10:04.570
later on this year because it's
always ahead of what you see
00:10:04.620 --> 00:10:06.420
in the latest cumulative update.
00:10:07.220 --> 00:10:12.060
It's already running bits
of Exchange 2016.
00:10:13.090 --> 00:10:16.030
And Exchange Online, this is unpublishable,
00:10:17.320 --> 00:10:18.910
but you have to accept it as fact.
00:10:19.630 --> 00:10:25.840
Exchange Online will always be feature
rich compared to Exchange
00:10:25.890 --> 00:10:30.210
on prem. There are some things that
are always going to be only
00:10:30.260 --> 00:10:31.460
available in the cloud.
00:10:32.050 --> 00:10:33.530
We will talk about that later on.
00:10:35.030 --> 00:10:36.350
So that's the current status.
00:10:37.500 --> 00:10:41.600
In terms of its deployment, it's
in data centers around the world
00:10:41.650 --> 00:10:42.710
which is fantastic.
00:10:43.330 --> 00:10:47.210
There are nine separate regions.
Think of nine regions as nine
00:10:47.920 --> 00:10:50.740
in our mess active directory forests.
00:10:51.410 --> 00:10:56.250
I'm putting it in on prem terms.
Nine enormous instances of
00:10:56.300 --> 00:10:59.680
the Exchange directory store because
they have a separate Exchange
00:10:59.730 --> 00:11:04.880
directory which is used to hold
information used by Exchange.
00:11:05.850 --> 00:11:08.850
And then there are all these mailboxes
and all these tags.
00:11:08.900 --> 00:11:09.680
How many tags?
00:11:10.470 --> 00:11:14.350
Hundreds and hundreds and hundreds.
00:11:15.170 --> 00:11:21.030
One piece of data given out the other
day, 1.2 million database copies.
00:11:22.640 --> 00:11:25.270
Each databases four copies.
00:11:26.010 --> 00:11:28.110
You now know how many
databases they have.
00:11:29.560 --> 00:11:34.120
And because Exchange supports 100
databases per DAG, you not
00:11:34.170 --> 00:11:37.410
a good idea about how many DAGs
they have, and it's a lot.
00:11:41.540 --> 00:11:44.790
Some of the figures that are being
thrown out, one was given
00:11:44.840 --> 00:11:48.270
the other day, about 50,000 servers
running for Exchange Online.
00:11:48.320 --> 00:11:49.770
They are the mailbox servers.
00:11:50.520 --> 00:11:53.850
But as you are all well aware and infrastructure
is not just mailboxes.
00:11:54.320 --> 00:11:58.920
In fact, the entire infrastructure
for Exchange Online is around
00:11:58.970 --> 00:12:02.470
about 100,000 servers.
That's a lot.
00:12:04.420 --> 00:12:06.760
That's a few little blinking
red lights to look at.
00:12:09.160 --> 00:12:12.570
Thanks be to God that managed availability
is there. I'll bet
00:12:12.620 --> 00:12:15.950
you thought that you would never
hear anybody say that, but the
00:12:16.000 --> 00:12:19.500
salient fact is that manageability
is absolutely a great example
00:12:19.770 --> 00:12:23.630
of technology transfer from the cloud
to on prem, because without
00:12:23.680 --> 00:12:26.150
managed availability they couldn't
run at this scale.
00:12:27.800 --> 00:12:33.790
I mean I have a whole pile of other
pieces and if you went behind
00:12:33.840 --> 00:12:36.860
the curtain session the other day you
would have learned about them.
00:12:36.910 --> 00:12:39.130
They have a phenomenal workflow engine.
00:12:39.900 --> 00:12:44.800
They have a great capacity to go
and catch systems, to detect
00:12:44.850 --> 00:12:48.420
problems, to fix problems, but without
managed availability they
00:12:48.470 --> 00:12:52.200
wouldn't be able to deal with Exchange.
It is a great, great thing.
00:12:54.570 --> 00:12:58.550
When you look at it, some of the
characteristics of what users
00:12:58.600 --> 00:13:00.660
get, huge mailboxes,
00:13:02.200 --> 00:13:06.980
indeed the new Office 365 import
service that was announced the
00:13:07.030 --> 00:13:12.050
other day is the thing where you
put all your PSTs on drive,
00:13:12.100 --> 00:13:14.940
ship them off to Microsoft data
centers and have them ingested
00:13:14.990 --> 00:13:19.940
into the service. It's a great way to
fill up all of those big mailboxes.
00:13:20.470 --> 00:13:24.120
Let's get rid of PSTs for
once and for all, please.
00:13:24.770 --> 00:13:28.670
The most insecure, the most unreliable,
the most horrible file
00:13:28.720 --> 00:13:31.860
format known the man, please.
00:13:35.310 --> 00:13:36.610
Thank you. You're all very nice.
00:13:37.680 --> 00:13:40.440
Seriously, this is a good way to
do it. If you are doing the
00:13:40.490 --> 00:13:43.180
Office 365 import service and you
are getting rid of PSTs like
00:13:43.230 --> 00:13:49.200
this, please, please direct the important
to the archive mailboxes
00:13:49.800 --> 00:13:54.520
for one very good reason and that
is you do not want output to
00:13:54.570 --> 00:13:58.120
suddenly wake up in the morning and say
I've got 100 gig to synchronize.
00:13:58.540 --> 00:14:00.330
Please let me get on
with that for you.
00:14:01.020 --> 00:14:02.530
This will be a bad thing.
00:14:03.850 --> 00:14:05.110
Put them in the archives.
00:14:07.370 --> 00:14:10.770
My favorite decision of all time
was reached recently when they
00:14:10.820 --> 00:14:18.460
removed the processing of the deleted
items tag out of the MRM policy.
00:14:20.980 --> 00:14:24.580
This is a great example of
where a decision is taken
00:14:25.950 --> 00:14:30.060
I think to help very small tenants,
but it gets in the way of
00:14:30.110 --> 00:14:31.880
large tenants, large enterprises.
00:14:33.480 --> 00:14:36.630
What this actually means, if you
haven't been following along,
00:14:37.620 --> 00:14:41.940
is that once an item goes into the
deleted items folder, it stays
00:14:41.990 --> 00:14:48.020
there, forever and ever
and ever and ever,
00:14:49.600 --> 00:14:54.920
unless the user decides to go and
remove it by emptying the folder.
00:14:55.460 --> 00:14:59.800
And the reason why this is done
is because so many people lost
00:14:59.850 --> 00:15:03.430
stuff and there are no backups
in Exchange Online.
00:15:04.880 --> 00:15:09.310
So once stuff in the old way, it
was cleared out after 30 days
00:15:09.360 --> 00:15:13.950
by the deleted items tab and the
default MRM policy it would
00:15:14.000 --> 00:15:17.730
go into recoverable items. It would
stay there for 30 days and
00:15:17.780 --> 00:15:19.970
then it would be removed from
the database and that was it.
00:15:21.890 --> 00:15:26.200
No backups, and if you are a CIO
came down to you or your CEO
00:15:26.250 --> 00:15:31.660
and said by the way. I seem to have,
in a fit of temper, deleted
00:15:31.710 --> 00:15:36.380
some e-mail from two months ago
and it's gone. I can't find it.
00:15:36.430 --> 00:15:38.810
That would be it. And
that's a bad thing.
00:15:40.560 --> 00:15:43.450
It is a bad thing when you don't
have backups, at least. So they
00:15:43.500 --> 00:15:45.200
decided to keep everything there.
00:15:48.470 --> 00:15:53.630
The interesting thing is if you
are in a hybrid configuration
00:15:54.300 --> 00:15:57.990
and you move one of these mailboxes
that has a ginormous deleted
00:15:58.040 --> 00:16:01.930
items folder back to on
prem, what happens?
00:16:02.700 --> 00:16:05.670
The first night, what happens?
00:16:07.800 --> 00:16:09.330
MFA wakes up
00:16:10.760 --> 00:16:14.260
and on the on prem server and says
excuse me, sir. I seem to
00:16:14.310 --> 00:16:18.260
realize that you have got 100,000 items
in your deleted items folder.
00:16:18.310 --> 00:16:21.270
Let me take care of that for
you and cleans them all out.
00:16:22.740 --> 00:16:25.220
They are still there. They are
still recoverable and you will
00:16:25.270 --> 00:16:28.270
have backups on prem, so that's okay,
but it's just kind of interesting
00:16:28.320 --> 00:16:33.090
how they just go away when you move people
back. Okay. Hybrid connectivity.
00:16:33.140 --> 00:16:37.250
This is Microsoft's great differentiator.
It's a thing that
00:16:37.300 --> 00:16:39.230
nobody else has and it's fantastic.
00:16:39.880 --> 00:16:44.750
The hybrid creates a unified GAL,
gives you unified mail flow
00:16:45.370 --> 00:16:49.090
and it gives you unified organization
all created by the hybrid
00:16:49.140 --> 00:16:50.580
configuration wizard.
00:16:52.490 --> 00:16:55.020
But the thing about it is, that
I have to point out to you, is
00:16:55.070 --> 00:16:58.170
management is not always unified
because there are some things
00:16:58.220 --> 00:17:01.390
that don't flow across the connector.
00:17:02.700 --> 00:17:05.640
It's a thing that you have to enormous
detail to, especially
00:17:05.690 --> 00:17:10.400
things like transport rules and,
indeed, MRM policies because
00:17:10.450 --> 00:17:12.780
if you make a change on one side
you have to make sure that the
00:17:12.830 --> 00:17:15.600
change is echoed on the other. Otherwise
you will have different
00:17:15.650 --> 00:17:19.100
processing occurring in on
prem and in the cloud.
00:17:20.690 --> 00:17:24.960
I'll also say that hybrid connectivity
is really only the start.
00:17:25.820 --> 00:17:31.290
There's so much more that you have
to think about because if
00:17:31.340 --> 00:17:34.890
you really want to have a unified
Office 365 environment, you're
00:17:34.940 --> 00:17:37.710
going to have Federation for single
sign-on and that sort of
00:17:37.760 --> 00:17:40.230
stuff, and you're probably going
to be thinking about things
00:17:40.280 --> 00:17:43.460
like using some of the advanced
features that are available in
00:17:43.510 --> 00:17:47.460
Office 365 that are so much easier
in the cloud than they are
00:17:47.510 --> 00:17:49.670
on prem, like rights management.
00:17:50.190 --> 00:17:53.680
You have to figure that kind of
stuff out. I also point out
00:17:53.730 --> 00:17:56.490
that there is AAD connect coming.
00:17:57.270 --> 00:17:59.340
This is going to be
the preferred tool
00:18:01.000 --> 00:18:05.830
for helping with hybrid systems
because it will facilitate, for
00:18:05.880 --> 00:18:11.390
example, the synchronization of
Office 365 Groups back into
00:18:12.680 --> 00:18:14.420
in on prem environment.
00:18:17.940 --> 00:18:23.490
A point I make continually to people
is that sure, Exchange Online
00:18:23.540 --> 00:18:27.760
is great, but you pay for more
than Exchange Online when you
00:18:27.810 --> 00:18:29.630
buy an Office 365 license.
00:18:30.260 --> 00:18:34.380
Now if you want to give Microsoft
or money for free or you want
00:18:34.430 --> 00:18:37.190
to give Microsoft too much money
for the license, that's okay,
00:18:37.860 --> 00:18:41.460
but it seems to me that if you are
going to transition workload
00:18:41.510 --> 00:18:42.200
to the cloud
00:18:43.440 --> 00:18:48.260
that you owe it to the company,
your employers, to look at what
00:18:48.310 --> 00:18:52.270
else can be dumped. You are paying
for this functionality so
00:18:52.320 --> 00:18:55.780
you should at least think about
using it. I'm just pointing
00:18:55.830 --> 00:18:59.520
out a couple of things here. Clearly,
SharePoint online, pretty
00:18:59.570 --> 00:19:03.160
good, I use it a lot for
document storage.
00:19:03.990 --> 00:19:08.000
I particularly use OneDrive for
business. I think that's okay.
00:19:08.670 --> 00:19:11.750
It's got some synchronization
issues, but that's life.
00:19:12.840 --> 00:19:14.690
I use Skype for business
all the time,
00:19:15.990 --> 00:19:17.350
but I'm a small
00:19:19.240 --> 00:19:22.620
tenant, if you will. Some of the
larger enterprises still need
00:19:22.670 --> 00:19:24.720
some functionality that has
yet to be delivered.
00:19:25.360 --> 00:19:27.890
I don't use Yammer because I can
communicate quite happily with
00:19:27.940 --> 00:19:29.520
myself through e-mail.
00:19:32.190 --> 00:19:35.240
I do use Office Delve because I
think it's a fantastic way of
00:19:35.290 --> 00:19:36.980
finding things that I have forgotten.
00:19:38.450 --> 00:19:42.640
It is kind of creepy at times that
Office Delve is so good at
00:19:42.690 --> 00:19:46.040
finding things that I've forgotten
or things that I didn't want
00:19:46.090 --> 00:19:50.750
to keep, but I really think that's
good. And then there's this
00:19:50.800 --> 00:19:54.540
new things that they have put
out, the Video Portal. What a
00:19:54.590 --> 00:19:58.020
fantastic way of doing internal
training videos.
00:19:59.580 --> 00:20:03.060
It's a fantastic integration between
Office 365 and Azure media
00:20:03.110 --> 00:20:07.010
services and it's so simple to hook
up your videos and make them
00:20:07.060 --> 00:20:12.410
available to end-users including
having those videos discoverable
00:20:12.460 --> 00:20:13.720
and shown through Delve.
00:20:14.230 --> 00:20:17.560
The point I'm making to you is there's
a lot more. Don't restrict
00:20:17.610 --> 00:20:20.430
your horizons to just Exchange.
00:20:23.060 --> 00:20:26.510
I think it's also important to
say that Office 365 is not the
00:20:26.560 --> 00:20:30.480
same for everybody. I guarantee you
in this room there are probably
00:20:30.530 --> 00:20:34.400
representatives for tens, maybe hundreds
of tenants and we might
00:20:34.450 --> 00:20:37.740
all see different things, so there
are a couple of things I will
00:20:37.790 --> 00:20:40.890
go through fairly quickly here.
The first thing is multitenant
00:20:40.940 --> 00:20:44.720
versus dedicated. The largest customers
use dedicated tenants.
00:20:44.770 --> 00:20:48.690
That gives them more control over
customization and feature rollout
00:20:48.740 --> 00:20:52.280
stuff like that. The vast bulk
of us use multitenant. We get
00:20:52.330 --> 00:20:55.090
what Microsoft gives us when
Microsoft gives us.
00:20:55.820 --> 00:20:59.530
This first release versus standard
release. First release, I'm
00:20:59.580 --> 00:21:02.340
on it because I want to see
new functionality early.
00:21:03.710 --> 00:21:08.460
You see new functionality anytime
2 to 6 weeks maybe even six
00:21:08.510 --> 00:21:12.430
months before the general population
sees it. I like that.
00:21:13.120 --> 00:21:16.590
There are E-SKUs, SKUs and P-SKUs.
00:21:17.110 --> 00:21:19.760
E is for enterprise. P is for personal.
00:21:20.950 --> 00:21:22.770
P are the small guys.
00:21:23.500 --> 00:21:27.290
E are the enterprise. There is a
lot more functionality in the
00:21:27.340 --> 00:21:30.970
enterprise SKUs, but you pay a lot
more for it. There's government
00:21:31.020 --> 00:21:32.290
and academic plans.
00:21:35.700 --> 00:21:39.450
And they have their own pricing arrangements
and there are other
00:21:39.500 --> 00:21:41.910
differences that we're not going
to go into here. There are
00:21:41.960 --> 00:21:45.850
standalone plans like SharePoint
online in case some people think
00:21:45.900 --> 00:21:49.740
of that as Office Online. There's stuff
that's delivered by Microsoft
00:21:50.110 --> 00:21:52.070
and their stuff that's
delivered by partners.
00:21:52.980 --> 00:21:55.690
Microsoft and HP, for example, have
got an arrangement that they
00:21:55.740 --> 00:21:59.040
are going to deliver Office 365
out of HP data centers.
00:21:59.090 --> 00:22:02.570
Office 365 in China, it's
delivered by a partner.
00:22:03.660 --> 00:22:06.110
There are different places that you
are going to get Office 365.
00:22:06.160 --> 00:22:08.410
And then there is the
last thing here.
00:22:08.960 --> 00:22:10.140
Flighting and straggling,
00:22:11.700 --> 00:22:16.410
flighting is the way Microsoft
deploys different features out
00:22:16.460 --> 00:22:17.670
to tenants.
00:22:18.970 --> 00:22:22.320
Some people might have slightly different
versions of code because
00:22:22.370 --> 00:22:25.560
they have been flighted at different
times or they have been
00:22:25.610 --> 00:22:27.900
flighted at different versions.
I know this is an interesting
00:22:27.950 --> 00:22:32.100
use of the word flight. It's a
new way to use this word, but
00:22:32.150 --> 00:22:35.720
just go along with me. Basically
it's a way of distributing code
00:22:35.770 --> 00:22:36.650
to tenants.
00:22:37.790 --> 00:22:41.380
You see this all the time in
the Yammer support groups.
00:22:42.640 --> 00:22:46.030
I don't see this feature but you
see this feature but we are
00:22:46.080 --> 00:22:49.100
paying the same or we're on the
same plan. It's simply because
00:22:49.370 --> 00:22:53.500
if we think about it with all of
the servers it's impossible
00:22:53.550 --> 00:23:00.480
to update them all at the same time.
You never, ever see a common
00:23:00.530 --> 00:23:05.180
view of Office 365 across the
entire infrastructure.
00:23:06.060 --> 00:23:08.590
It's understandable. Just think
how long it takes you to deploy
00:23:08.640 --> 00:23:11.340
a new version of office server products.
00:23:12.120 --> 00:23:14.810
Now imagine what it's like to do
it across millions of servers.
00:23:15.810 --> 00:23:20.190
Straggling is also in the same
bucket because sometimes some
00:23:20.240 --> 00:23:21.620
servers are overlooked.
00:23:22.460 --> 00:23:23.730
They have this incredible
00:23:24.990 --> 00:23:28.920
workflow engine. They have this incredible
capability to do automated
00:23:28.970 --> 00:23:34.190
updates, but sometimes servers are
overlooked and you might connect
00:23:34.240 --> 00:23:37.160
to a slightly outdated server and
see a different view from what
00:23:37.210 --> 00:23:37.690
I see.
00:23:38.440 --> 00:23:43.190
That's kind of interesting. And it's
part of just the characteristics,
00:23:43.440 --> 00:23:46.460
the unique characteristics
of running in the cloud.
00:23:48.330 --> 00:23:50.850
Let's talk about everybody's
favorite topic.
00:23:50.900 --> 00:23:56.090
I seem to have been doing migration
for most of my career.
00:23:57.320 --> 00:23:59.720
One of these days I'll get
to where I'm going.
00:24:05.400 --> 00:24:09.680
Before we go, I think you have to
know what we're going to move.
00:24:11.770 --> 00:24:14.190
I see a lot of people just starting
off. We moved a couple of
00:24:14.240 --> 00:24:16.600
mailboxes, but there's so much more.
00:24:17.600 --> 00:24:22.250
Clearly, if you're going to go
to Office 365 remember what I
00:24:22.300 --> 00:24:25.630
said before. It's much more than
Exchange. It's a good idea
00:24:25.680 --> 00:24:29.520
to think about I've got the mailboxes
but what about all of this
00:24:29.570 --> 00:24:30.240
other stuff?
00:24:31.280 --> 00:24:35.120
Am I interested in public folders, moving
them across? Am I interested
00:24:35.170 --> 00:24:37.450
in eliminating public folders, perhaps?
00:24:39.090 --> 00:24:39.980
Nobody said yes.
00:24:41.380 --> 00:24:46.330
Somebody did. You want to
get rid of them tomorrow?
00:24:55.840 --> 00:24:59.390
I don't know if you heard that. This
is the new migration technique
00:24:59.980 --> 00:25:01.250
for public folders.
00:25:01.810 --> 00:25:05.960
Just lie and tell people they are not
supported anymore. They're gone.
00:25:09.490 --> 00:25:10.170
Well done.
00:25:10.950 --> 00:25:12.790
I'll use that again.
00:25:14.300 --> 00:25:22.700
There's lots of stuff. And clients
tend to be a bit of a problem.
00:25:22.750 --> 00:25:26.490
You are going to need to use the
latest clients, so that means,
00:25:26.540 --> 00:25:30.610
essentially, you are going to have
to get up to Outlook 2010,
00:25:31.970 --> 00:25:37.060
service pack whatever it is, whatever
the latest is that's the
00:25:37.110 --> 00:25:41.910
general rule. There are various
things on the website to tell
00:25:41.960 --> 00:25:44.040
you exactly what it is
at any point in time.
00:25:44.660 --> 00:25:49.570
What I want to point out here is in
the prem world you have control
00:25:49.620 --> 00:25:53.460
over clients much more, so you
can always make sure that you
00:25:53.510 --> 00:25:56.560
match the server functionality
that you're deploying with the
00:25:56.610 --> 00:26:00.570
client functionality. Remember
now, you're not in control of
00:26:00.620 --> 00:26:01.970
the servers anymore.
00:26:02.560 --> 00:26:05.430
As those servers keep on getting
updated, you have got to make
00:26:05.480 --> 00:26:08.050
arrangements that your clients
are getting updated.
00:26:08.100 --> 00:26:09.630
Otherwise, you are in danger
00:26:11.110 --> 00:26:13.660
of becoming out of date
and out of support.
00:26:14.240 --> 00:26:17.930
Browsers are a particular issue,
or have been a particular issue
00:26:17.980 --> 00:26:18.980
over the last year.
00:26:20.160 --> 00:26:24.080
Chrome, which is a pretty
decent browser,
00:26:25.550 --> 00:26:29.510
Google in their wisdom went and deprecated
the show modal dialog
00:26:29.560 --> 00:26:31.520
API last September.
00:26:32.250 --> 00:26:36.240
Half of OWA stopped working. Half
of the Exchange administration
00:26:36.290 --> 00:26:42.310
center stopped working. Half of the Office
365 admin port stopped working.
00:26:42.650 --> 00:26:48.530
That wasn't very kind of them. So
you have to be able to I think
00:26:48.580 --> 00:26:52.980
really, really get yourself in a
frame of mind that clients are
00:26:53.030 --> 00:26:57.350
now going to be updated much, much
faster than they were before
00:26:57.980 --> 00:27:00.000
to match what's going
on with the servers.
00:27:02.370 --> 00:27:04.860
In terms of the knowledge that you
need to go and approach this
00:27:04.910 --> 00:27:09.390
migration, clearly you need a lot
of Office 365 knowledge, but
00:27:09.440 --> 00:27:13.560
you also need project management.
If ever there was a migration
00:27:13.610 --> 00:27:18.020
that needed solid project management
support, it's the move to
00:27:18.070 --> 00:27:24.270
Office 365. Go get a good project
manager, a good technology
00:27:24.320 --> 00:27:27.500
project manager, one that has appreciation
for what you are going
00:27:27.550 --> 00:27:31.840
to and use them to help you get
there. It will be good for you.
00:27:32.680 --> 00:27:34.990
Switching over, the big bang approach,
the one that you do on
00:27:35.040 --> 00:27:40.350
the weekend, that's fine for small
enterprises, absolutely hopeless
00:27:40.400 --> 00:27:42.510
for the large guys. You are going
to be doing this for months.
00:27:42.560 --> 00:27:47.450
That's why hybrid is so important.
It's so critical to prepare
00:27:47.500 --> 00:27:52.360
for that. Your network, in particular,
is going to need some attention.
00:27:53.120 --> 00:27:54.260
And it's really simple.
00:27:55.900 --> 00:28:01.150
On prem, where is all your data flowing?
It's to your data centers,
00:28:02.960 --> 00:28:08.860
especially all the client interaction
is to your data centers.
00:28:09.550 --> 00:28:14.620
Office 365, you've got a couple
of things to move first, like
00:28:14.670 --> 00:28:18.990
mailboxes, and then you want all
of your users to have really
00:28:19.040 --> 00:28:24.520
good response time back from the
service, not only for mailboxes
00:28:24.570 --> 00:28:28.700
but also for OneDrive,
SharePoint et cetera.
00:28:30.560 --> 00:28:34.370
This is an opportunity for you to
have a conversation with your
00:28:34.420 --> 00:28:38.250
network team and figure out how
you're going to re-architecture
00:28:38.300 --> 00:28:43.330
network so that instead of being
inward focusing you're outward
00:28:43.380 --> 00:28:44.900
focusing especially
00:28:46.150 --> 00:28:47.280
towards Microsoft.
00:28:48.120 --> 00:28:53.370
That's just the way it is. ExpressRoute
option which essentially
00:28:53.420 --> 00:28:57.400
allows you to have a very fast connection
to Office 365 is being
00:28:57.450 --> 00:29:01.870
upgraded to support Office 365.
I think that's a good thing to
00:29:01.920 --> 00:29:04.370
look after if you are you interested.
00:29:05.340 --> 00:29:09.190
In terms of migration toolkits, they
are improving all the time.
00:29:10.650 --> 00:29:11.520
Some of the
00:29:13.560 --> 00:29:15.850
public folder scripts are a bit outdated.
00:29:16.910 --> 00:29:21.500
If you take them off the Exchange
kit, that's a bad idea.
00:29:21.550 --> 00:29:24.340
Go and get the latest versions
that are online. In terms of
00:29:24.390 --> 00:29:29.400
the commercial toolkits, there are
lots of people out there that
00:29:29.450 --> 00:29:34.050
advertise a capacity, capability
of moving mailboxes and other
00:29:34.590 --> 00:29:36.960
pieces of data to Office 365.
00:29:38.060 --> 00:29:40.310
I'm not going to endorse
anybody here.
00:29:42.070 --> 00:29:44.040
What I will say is test.
00:29:44.920 --> 00:29:49.590
Go ask the folks that are down in
the exhibition area. Ask them
00:29:49.640 --> 00:29:52.900
for test versions and go and test
them in your environment and
00:29:52.950 --> 00:29:55.070
you'll find the best one for you.
00:29:56.030 --> 00:29:59.850
The ones that, some of them have great
project management capabilities
00:29:59.900 --> 00:30:03.080
so you can plan and automate mailbox
transition. Some of them
00:30:03.130 --> 00:30:06.370
are only Exchange and some of them
will do Exchange and SharePoint.
00:30:06.420 --> 00:30:08.680
Some of them will also
have Active Directory.
00:30:09.450 --> 00:30:12.440
You've really got to go and do some
00:30:13.670 --> 00:30:17.960
planning and some testing and also
think about cost because they
00:30:18.010 --> 00:30:19.890
do vary enormously in cost.
00:30:22.360 --> 00:30:25.630
Let's pretend that we've got
Office 365. That was quick.
00:30:25.680 --> 00:30:29.080
That was called the Big Bang migration.
It happened just there.
00:30:30.590 --> 00:30:31.940
Didn't you see the
mailboxes go by?
00:30:31.990 --> 00:30:39.810
Zoom. Might appeal to you as I
said earlier is that you want
00:30:39.860 --> 00:30:43.480
to start thinking about using more
of Office 365. But this is
00:30:43.530 --> 00:30:46.630
actually an interesting thing because
you have an opportunity
00:30:46.680 --> 00:30:50.690
to influence how your company
deals with information.
00:30:53.760 --> 00:30:57.270
The classic on prem environment
probably has Exchange,
00:30:58.470 --> 00:31:02.110
FileShares, file servers, that
kind of stuff. There are some
00:31:02.160 --> 00:31:04.270
other applications out there
that you are using.
00:31:05.960 --> 00:31:09.440
Again, you are paying for Office
365, so let's maximize the use
00:31:09.490 --> 00:31:12.210
of Office 365 by using the
features that are there.
00:31:12.910 --> 00:31:16.230
That means that you are going to have
to rethink how your organization
00:31:16.920 --> 00:31:22.410
shares information, collaborates,
uses documents, shares documents,
00:31:22.460 --> 00:31:25.480
backs up documents, classifies documents.
00:31:26.130 --> 00:31:29.940
In short, it's an opportunity to
think about the information
00:31:29.990 --> 00:31:31.550
flow within your organization.
00:31:32.890 --> 00:31:36.200
This is a point I've made to several
companies that I have been
00:31:36.250 --> 00:31:37.060
working with.
00:31:37.970 --> 00:31:41.120
It's also an opportunity to clear
up a lot of the sins of the
00:31:41.170 --> 00:31:45.070
past, because let's face it, if
your he still running a 1990s
00:31:46.300 --> 00:31:50.660
era file sharing environment and
using that for document storage,
00:31:51.350 --> 00:31:55.620
you probably don't have an earthly
chance of being able to resist
00:31:55.670 --> 00:31:57.710
something like an eDiscovery action
00:31:59.350 --> 00:32:01.110
from an offended third-party.
00:32:02.530 --> 00:32:06.800
It's time to protect. There are some
things easier and some things
00:32:06.850 --> 00:32:08.550
are much harder in the cloud.
00:32:10.410 --> 00:32:15.160
Easier, encryption is enormously
easier in prem,
00:32:16.460 --> 00:32:19.600
some forms of encryption. S/MIME
isn't particularly easier.
00:32:20.170 --> 00:32:24.470
PGP isn't particularly easier, but
if your interest is in things
00:32:24.520 --> 00:32:30.380
like rights management and OME the
office 365 messaging encryption
00:32:30.790 --> 00:32:34.830
kind of technology, it's like click,
click, click a couple of
00:32:34.880 --> 00:32:38.750
PowerShell commands and it's done.
The reason is because Microsoft
00:32:38.800 --> 00:32:41.960
is done all of the heavy lifting
behind it. It's the kind of
00:32:42.010 --> 00:32:44.080
thing when you set up AD
00:32:45.300 --> 00:32:49.260
rights management on prem and you
need a server, maybe a couple
00:32:49.310 --> 00:32:53.230
of servers. You need about 42 hours
just to read the documentation.
00:32:53.980 --> 00:32:58.360
You need a test plan and all the
rest. Just do it. 5 minutes
00:32:58.410 --> 00:33:03.190
and you will have AAD rights
management going.
00:33:03.900 --> 00:33:04.810
That's really good.
00:33:05.990 --> 00:33:08.590
SharePoint document libraries and
the base functionality are
00:33:08.640 --> 00:33:09.620
also very easy.
00:33:10.290 --> 00:33:11.690
Workflow isn't so easy.
00:33:12.650 --> 00:33:15.230
Dedicated applications that you
filter and SharePoint aren't
00:33:15.280 --> 00:33:15.970
so easy.
00:33:16.900 --> 00:33:19.790
Skype is very easy, again, because
all of the heavy lifting is
00:33:19.840 --> 00:33:22.940
done except for things like enterprise,
voice, outside calling
00:33:22.990 --> 00:33:25.430
and those things are kind of tough.
The biggest thing that's
00:33:25.480 --> 00:33:27.270
easier is flexing capacity.
00:33:28.540 --> 00:33:31.060
When you need to move more mailboxes
you just do them.
00:33:31.110 --> 00:33:34.260
There's nothing about bringing up
use service and all the rest.
00:33:34.310 --> 00:33:38.340
It's done. They are bringing
on new servers all the time.
00:33:38.860 --> 00:33:43.160
Hundreds of new servers are added
to Office 365 every week and
00:33:43.210 --> 00:33:47.280
that's to add capacity for existing
tenants and new tenants.
00:33:47.880 --> 00:33:51.100
The hardest things are dealing
with third-party applications.
00:33:52.200 --> 00:33:55.290
In fact, the whole industry is
going through a transformation
00:33:55.340 --> 00:33:58.490
here, because when you think about
it, Exchange, part of the
00:33:58.540 --> 00:34:01.370
reason why Exchange is very successful
in the non-prem world
00:34:02.210 --> 00:34:04.170
was because we have had this enormously
00:34:05.640 --> 00:34:11.280
rich ecosystem built up around the
product of third-party products
00:34:11.640 --> 00:34:14.420
that fill in all the gaps
that Microsoft left.
00:34:15.880 --> 00:34:19.200
The essential thing that all of
those third-party products rely
00:34:19.250 --> 00:34:20.520
on his access to data.
00:34:21.150 --> 00:34:23.770
If they don't have access to
data they can do anything.
00:34:24.700 --> 00:34:29.190
It's really, really difficult at times
to get that data for third-party
00:34:29.820 --> 00:34:31.230
out of your tenant.
00:34:33.010 --> 00:34:36.940
There is a lot of third-party
ISPs out there who are
00:34:38.250 --> 00:34:40.990
figuring out how they are going to
deal with the new cloud work.
00:34:42.780 --> 00:34:46.850
Microsoft is releasing new APIs and
they have made an announcement
00:34:46.900 --> 00:34:49.560
to the new REST API which looks very,
very promising. It's going
00:34:49.610 --> 00:34:53.690
to replace Exchange Web Services,
but essentially, there is still
00:34:53.740 --> 00:34:59.330
such a lot of data that the ISPs
depend on, things about all
00:34:59.380 --> 00:35:02.630
the auditing records and stuff
like that, accounting records
00:35:02.680 --> 00:35:05.260
just can't get, so they
are dealing with it.
00:35:06.660 --> 00:35:10.930
And of course, it's also a little
bit harder to integrate Exchange
00:35:10.980 --> 00:35:15.750
Online with on premises software.
If you've got Exchange built
00:35:15.800 --> 00:35:21.710
into something like workflow and a new
user comes into the organization
00:35:21.760 --> 00:35:24.650
and you set up a new mailbox and
you send them a welcome message
00:35:24.700 --> 00:35:28.000
and all that, it's a little bit
harder, not very much harder,
00:35:28.050 --> 00:35:30.860
just a little bit.
00:35:31.690 --> 00:35:34.710
We've got to the cloud and now
we have to deal with it.
00:35:39.440 --> 00:35:42.060
This is probably the biggest thing
that people struggle with.
00:35:43.910 --> 00:35:46.700
The cloud today is not
the cloud tomorrow.
00:35:48.250 --> 00:35:52.990
The old ways of developing software
are gone. They are dusted.
00:35:53.040 --> 00:35:56.100
They are not coming back. There is
no point in complaining about it.
00:35:56.150 --> 00:35:59.000
This is just what we have to deal
with today until somebody comes
00:35:59.050 --> 00:36:00.100
up with a better plan.
00:36:00.800 --> 00:36:03.520
New features are going to
appear all the time.
00:36:04.510 --> 00:36:08.060
New features are written by Microsoft
as a response to customer
00:36:08.110 --> 00:36:12.100
requests and to remain competitive
in the market and so forth
00:36:12.150 --> 00:36:15.980
and that's great. They delight users.
They dismay administrators
00:36:16.030 --> 00:36:16.620
at times.
00:36:17.680 --> 00:36:19.650
And we will talk a little
more about that.
00:36:20.940 --> 00:36:22.720
But it's the same everywhere
in the cloud.
00:36:23.930 --> 00:36:28.480
A really good example of that is
the ex accompli apps that have
00:36:28.530 --> 00:36:33.710
become Outlook for iOS and Outlook
for android. Every two weeks
00:36:34.420 --> 00:36:37.230
these clients are updated. Every
two weeks something different
00:36:37.280 --> 00:36:37.910
is there.
00:36:38.530 --> 00:36:41.350
My gosh, you could be on iTunes
all the time, give me new, give
00:36:41.400 --> 00:36:44.900
me new, give me new just to keep
up to date, but that's the world
00:36:44.950 --> 00:36:45.560
we live in.
00:36:46.930 --> 00:36:49.940
The challenges I think for admins,
and I guess most of you are
00:36:49.990 --> 00:36:53.620
admins in this room. I don't think
many users have survived this far.
00:36:56.320 --> 00:36:59.940
They probably feel insulted or maligned
or something like that.
00:37:01.530 --> 00:37:06.530
The challenge for us as the admins
is to understand the change,
00:37:07.040 --> 00:37:10.510
to know what's coming before users
see it. It's a really bad
00:37:10.560 --> 00:37:13.930
idea when a user comes in on Monday
morning and sees something
00:37:13.980 --> 00:37:17.020
and starts ringing and you don't
know anything about it.
00:37:18.360 --> 00:37:23.920
Also, to think about some of these
user features can have some
00:37:23.970 --> 00:37:28.140
level of administrative control
of plight if required.
00:37:28.630 --> 00:37:30.500
These are the challenges
we have to deal with.
00:37:32.520 --> 00:37:37.160
It's all a factor of losing control,
because when you are on
00:37:37.210 --> 00:37:40.670
prem you can do anything you like. The
servers are under your control.
00:37:40.720 --> 00:37:43.850
AD is under your control. The clients
are under your control.
00:37:43.900 --> 00:37:45.660
The network is under your control.
00:37:47.110 --> 00:37:49.140
Management isn't under your control.
But you get the idea.
00:37:49.190 --> 00:37:52.060
You have control of everything
and you can tweak stuff.
00:37:54.080 --> 00:37:55.940
You can tweak anything you want.
00:37:56.490 --> 00:37:59.490
But Office 365 gives you no control.
00:38:00.470 --> 00:38:02.680
They have a roadmap.
It's very clear.
00:38:03.500 --> 00:38:06.690
They do a good job of publishing
it and that's what you're going
00:38:06.740 --> 00:38:07.150
to get.
00:38:10.920 --> 00:38:13.940
Details because of some of that
flighting stuff and straggling
00:38:13.990 --> 00:38:17.010
stuff can vary from time to time,
but essentially what's on the
00:38:17.060 --> 00:38:20.900
roadmap is what you get. And you
can look and see what's coming
00:38:20.950 --> 00:38:23.250
up and you can try to figure
out what's going to happen.
00:38:26.720 --> 00:38:30.300
It's also true that Microsoft sometimes
makes decisions that
00:38:30.350 --> 00:38:31.840
you are going to disagree with.
00:38:32.770 --> 00:38:36.140
I fundamentally disagree with the
decision not to clean out the
00:38:36.190 --> 00:38:40.650
deleted items folder. I think that's
stupid, but I'm looking
00:38:40.700 --> 00:38:43.090
at it from the perspective
of an enterprise admin.
00:38:44.070 --> 00:38:48.000
For somebody who's running as a
tenant who's serving 20 users
00:38:48.050 --> 00:38:50.730
and they don't have the time to
deal with users telling them
00:38:50.780 --> 00:38:55.440
that they can't find a deleted message,
it's the greatest innovation
00:38:56.760 --> 00:38:58.040
in the last 20 years.
00:39:02.590 --> 00:39:05.850
Part of losing control is this
ever-changing interface.
00:39:08.050 --> 00:39:11.080
Because we don't have formal
release cycles,
00:39:12.300 --> 00:39:15.600
with Exchange you think that there
is a cumulative update coming
00:39:15.650 --> 00:39:19.480
every 13 weeks in something might
change in the UI of OWA in
00:39:19.530 --> 00:39:22.130
that stage or even Outlook or whatever,
00:39:23.860 --> 00:39:30.020
but the UI in Office 365 is in
this constant flux. Things are
00:39:30.070 --> 00:39:33.930
changing all the time underneath
of it. So you can see stuff
00:39:33.980 --> 00:39:38.120
happening that is totally unpredictable.
My example here is
00:39:38.170 --> 00:39:43.390
in January 2015, this year, they were
preparing for the new compliance
00:39:43.440 --> 00:39:47.100
center which is the new area where all
of the things about preservation,
00:39:47.590 --> 00:39:51.720
archiving, retention policies comes
from. There were changes
00:39:51.770 --> 00:39:54.530
that were going to be made to the
Exchange administration console
00:39:54.580 --> 00:39:58.060
and also to the Office 365 administration
console. All of a
00:39:58.110 --> 00:40:01.320
sudden we started to see things
like duplicate items showing
00:40:01.370 --> 00:40:05.240
up in menus. We started to see menu
items being missing. It was
00:40:05.290 --> 00:40:06.750
there a moment ago and now it's gone.
00:40:07.360 --> 00:40:09.930
That's quite disconcerting when
you think about it. You start
00:40:09.980 --> 00:40:13.830
wondering to yourself what kind
of mind altering drugs did I
00:40:13.880 --> 00:40:15.080
have at lunchtime.
00:40:15.940 --> 00:40:18.190
It was there before lunch and now
it's gone, but that's the type
00:40:18.240 --> 00:40:22.830
of thing. You also saw things like
options being grayed out all
00:40:22.880 --> 00:40:26.540
of a sudden and this is all because
data is being refreshed and
00:40:26.590 --> 00:40:29.680
data elements are being refreshed and
UI elements are being refreshed
00:40:29.730 --> 00:40:30.770
and it just happens.
00:40:32.640 --> 00:40:34.630
It's something we have
to factor in.
00:40:35.410 --> 00:40:37.600
Here are some other examples
of UI changes.
00:40:38.270 --> 00:40:42.330
The app launcher came in. See this
thing here? All the apps.
00:40:42.380 --> 00:40:45.920
Why did that come in? Simple. It
was needed because there wasn't
00:40:45.970 --> 00:40:50.820
enough space on the bar, the browser
bar to fit all of the options
00:40:50.870 --> 00:40:53.570
that a user could use. I think
it's a pretty good idea.
00:40:54.750 --> 00:40:57.260
You should've seen the hate
mail that came out of this.
00:40:58.840 --> 00:41:04.260
Users hated it. The next one. Another
hate mail blizzard, the
00:41:04.310 --> 00:41:06.320
icon for Outlook.
00:41:07.730 --> 00:41:11.730
Microsoft changed the text underneath
of it for mail from Outlook
00:41:11.780 --> 00:41:12.400
to mail.
00:41:13.150 --> 00:41:14.970
Everybody thought that was a disaster.
00:41:16.640 --> 00:41:19.380
You see the type of people we have
to work with? I mean, my God.
00:41:20.790 --> 00:41:25.700
Group notifications, so Office 365
you can like things in Office
00:41:25.750 --> 00:41:30.910
365 Groups. I am of an age when
like means something specific
00:41:30.960 --> 00:41:31.500
to me.
00:41:32.210 --> 00:41:35.400
I'm not into Facebook likes. I'm
not into Twitter likes, any
00:41:35.450 --> 00:41:39.660
type of likes. But anyway, apparently,
it's part of being social.
00:41:39.710 --> 00:41:43.490
I guess I'm not very social, so
I don't like them, but anyway
00:41:43.540 --> 00:41:46.600
you can like stuff in groups. When
you like stuff in groups you
00:41:46.650 --> 00:41:50.050
get notifications that somebody
really likes you. I'm so this
00:41:50.100 --> 00:41:53.630
popped up and it wasn't working
of course because nobody was
00:41:53.680 --> 00:41:57.840
really using groups. And then they
said we've got to take that
00:41:57.890 --> 00:42:01.910
away and so it appeared. It was there
for about six hours and disappeared.
00:42:01.960 --> 00:42:08.980
Confusion. Distribution groups, you
know in on prem, OWA, you've
00:42:09.030 --> 00:42:12.560
got an option where users can manage
for their own distribution groups.
00:42:14.000 --> 00:42:17.010
So that option disappeared for a
while and that wasn't so good.
00:42:17.750 --> 00:42:20.780
But essentially, at the end of the
day the point you've got to
00:42:20.830 --> 00:42:24.460
figure out, if you can't learn to
live with cloud cadence, should
00:42:24.510 --> 00:42:25.750
you be going to the cloud?
00:42:26.480 --> 00:42:29.430
If your organization can't live
with this, should they be going
00:42:29.480 --> 00:42:30.150
to the cloud?
00:42:34.450 --> 00:42:37.110
Some examples to a fairly major
00:42:38.400 --> 00:42:39.930
recent new functionality,
00:42:41.190 --> 00:42:45.150
this new functionality is introduced
to first release tenants
00:42:45.200 --> 00:42:46.380
first, naturally.
00:42:47.240 --> 00:42:50.950
They get to see it. However, Microsoft
will tell you that it's
00:42:51.000 --> 00:42:54.690
about two weeks before general availability
occurs. That's not
00:42:54.740 --> 00:42:55.580
actually true.
00:42:56.400 --> 00:42:58.740
That's what's on the website.
It's not true. And the reason
00:42:58.790 --> 00:43:02.350
is because once stuff goes into first
release it's an opportunity
00:43:02.400 --> 00:43:05.780
for Microsoft to experiment with
it. It's an opportunity to
00:43:05.830 --> 00:43:09.960
tweak it. It's an opportunity to
see what users like and dislike.
00:43:10.650 --> 00:43:14.910
Some things and Delve is the best
example of it were in first
00:43:14.960 --> 00:43:17.480
release status for a very long
time. For Delve it was about
00:43:17.530 --> 00:43:18.510
six months.
00:43:19.340 --> 00:43:24.340
Eventually, they will say this is ready.
At that point new functionality
00:43:24.390 --> 00:43:27.180
goes into general release
and everybody gets it.
00:43:28.170 --> 00:43:32.300
Everybody gets it if you're on the
right plan because some plans
00:43:32.350 --> 00:43:36.690
don't have some of this stuff in it.
In the last number of months,
00:43:36.740 --> 00:43:39.950
I think this is the list since last
November. We've had Delve,
00:43:40.000 --> 00:43:44.440
Office Video, Office 365 Groups,
Clutter and People View.
00:43:45.310 --> 00:43:47.000
That's a lot of new functionality.
00:43:48.410 --> 00:43:50.730
That's a lot of new functionality
for users to deal with, but
00:43:50.780 --> 00:43:52.910
it's also a lot of new functionality
for admittance to figure
00:43:52.960 --> 00:43:55.270
out how they're going to use. This
is the kind of cadence that
00:43:55.320 --> 00:43:56.420
you're going to have to deal with.
00:43:57.960 --> 00:44:01.320
Office Delve is an interesting
example of what happens.
00:44:01.370 --> 00:44:03.950
Remember I said it takes about
six months? I think this is a
00:44:04.000 --> 00:44:08.890
great interface. I think it's a
great way to liberate people
00:44:08.940 --> 00:44:12.560
from information silos that too often
exist inside organizations.
00:44:12.590 --> 00:44:15.820
I really like it. I think there
is some tweaking that could be
00:44:15.870 --> 00:44:19.660
done with the Office Graph database,
especially from Europe,
00:44:19.710 --> 00:44:21.970
but we'll get to that
in another place.
00:44:22.800 --> 00:44:26.750
Essentially, everything that you do
in Office 365 has been tracked
00:44:26.800 --> 00:44:30.070
and it goes into the Office Graph
database which is where Delve
00:44:30.120 --> 00:44:31.680
gets its information from.
00:44:32.630 --> 00:44:35.970
You look about some of the things that
they have to do over that period.
00:44:36.020 --> 00:44:39.290
If you were using Delve first release
and you went through all
00:44:39.340 --> 00:44:44.000
of this, so you didn't know about,
for example, SharePoint holds.
00:44:44.050 --> 00:44:47.660
If a document was put on hold or
a document library was put on
00:44:47.710 --> 00:44:52.910
hold and a change was made in it,
up popped the preservation
00:44:52.960 --> 00:44:56.410
library in a Delve view. That shouldn't
happen because that's
00:44:56.460 --> 00:44:57.540
a hidden library.
00:44:58.050 --> 00:44:59.910
It wasn't very hidden for
you, but there you go.
00:45:00.930 --> 00:45:04.560
It couldn't cope with any documents
that were in groups, private
00:45:04.610 --> 00:45:08.390
document libraries. They remain
invisible even to people who
00:45:08.440 --> 00:45:11.780
owned those documents, so that
shouldn't have happened.
00:45:13.090 --> 00:45:16.760
Initially, out of the box it didn't
provide any way to hide documents
00:45:16.810 --> 00:45:20.510
from Delve. You can now do it by making
a change to the SharePoint
00:45:20.560 --> 00:45:26.310
schema in the libraries. You can
say all the documents in the
00:45:26.360 --> 00:45:29.800
HR document library I don't want
them to ever show up in Delve,
00:45:29.850 --> 00:45:30.860
so that's pretty good.
00:45:32.130 --> 00:45:36.410
Then boards were added. There's this
thing of being able to very
00:45:36.460 --> 00:45:40.920
quickly set up a collection of
documents by pinning them all
00:45:40.970 --> 00:45:41.670
to a board.
00:45:42.270 --> 00:45:46.150
It's a nice idea, but there is no administrative
control whatsoever.
00:45:46.840 --> 00:45:50.960
You could have 42 different boards
with approximately the same
00:45:51.010 --> 00:45:54.680
name, which doesn't seem to be
a good thing, but it's the way
00:45:54.730 --> 00:45:55.410
that it's done.
00:45:56.390 --> 00:45:58.490
And then you have e-mail
attachments were added.
00:45:59.420 --> 00:46:02.770
What this means is that if somebody
sends you an attachment and
00:46:02.820 --> 00:46:07.970
you are in Exchange Online mailbox,
those attachments can be
00:46:08.020 --> 00:46:12.280
surfaced in Delve. Not all attachments
will be surfaced.
00:46:12.330 --> 00:46:15.750
Delve will make a calculation as
to which are the most relevant
00:46:15.800 --> 00:46:17.540
to you and show you them.
00:46:18.160 --> 00:46:19.420
But here's the kicker.
00:46:19.960 --> 00:46:25.000
It depends on those messages containing
the attachments remaining
00:46:25.050 --> 00:46:26.020
in the inbox.
00:46:26.820 --> 00:46:30.410
If you go and refile the document
somewhere and then you say
00:46:30.460 --> 00:46:32.510
oh Delve. That's a very interesting
attachment and I would like
00:46:32.560 --> 00:46:35.210
to see that and you click
on it, you won't see it.
00:46:36.570 --> 00:46:37.770
It is still an open the bug.
00:46:39.000 --> 00:46:41.490
I'm not picking on Delve, because
I think a Delve is great.
00:46:42.390 --> 00:46:45.720
What I'm trying to do here is illustrate
the kind of dynamics
00:46:45.770 --> 00:46:47.160
that you actually see
00:46:48.700 --> 00:46:52.160
inside the service. These
are exposed to end-users.
00:46:54.550 --> 00:46:57.100
It's not like you're running in
a test environment. You figure
00:46:57.150 --> 00:47:00.120
all of this stuff out and make sure
it's ready and then release.
00:47:00.170 --> 00:47:02.150
This all happens in live time.
00:47:03.440 --> 00:47:04.510
It's very different.
00:47:05.660 --> 00:47:09.800
Another example, Office 365 Groups, I
think this is a great innovation too.
00:47:10.470 --> 00:47:14.500
It's the first innovation in the
area of distribution groups
00:47:14.550 --> 00:47:17.840
that we have had since dynamic distribution
groups were introduced
00:47:17.890 --> 00:47:21.890
in Exchange 2003. It's the future
of distribution groups and
00:47:21.940 --> 00:47:22.830
so that's good too.
00:47:24.110 --> 00:47:29.470
How can I begin? I got very upset
when these were introduced.
00:47:29.520 --> 00:47:33.810
I did. I may have said words that
started with F and ended with
00:47:33.860 --> 00:47:34.700
something else.
00:47:36.680 --> 00:47:37.940
What do you think I said?
00:47:38.520 --> 00:47:40.630
Fun, yeah, fun,
00:47:42.890 --> 00:47:45.420
there you go. Fun for
the Republican Party
00:47:47.260 --> 00:47:51.020
and Fox News. I could
have said Fox News.
00:47:52.760 --> 00:47:54.660
You missed that one, eh?
00:47:56.830 --> 00:48:00.260
That's a queue for go fast. Anyway
I may have said words.
00:48:05.400 --> 00:48:10.170
Basically, groups leverage a lot of
different parts of Office Online.
00:48:10.220 --> 00:48:13.680
You got Exchange contributing to
shared mailbox and a calendar.
00:48:13.730 --> 00:48:16.930
You have OneDrive. You have OneNote.
And you're going to have
00:48:16.980 --> 00:48:20.290
other stuff that's going to be put in
there. It's really, really good.
00:48:21.000 --> 00:48:23.700
But what I really got upset about
was the fact that there was
00:48:23.750 --> 00:48:27.660
absolutely no management control
over groups. Anybody could
00:48:28.710 --> 00:48:34.710
create a group. I realized that this
is a clash between my fuddy-duddy
00:48:34.760 --> 00:48:38.640
management style, which is where
I would like control because
00:48:38.690 --> 00:48:41.760
I remember what happened when public
folders were introduced
00:48:42.520 --> 00:48:46.420
and people forgot. There are probably
a few of you in this room
00:48:47.450 --> 00:48:51.600
who forgot to put any control
on the public folder route.
00:48:56.440 --> 00:49:00.440
Come on. There are a couple
of you here. There you go.
00:49:00.490 --> 00:49:03.820
There you go. So what happened when
you didn't control the public
00:49:03.870 --> 00:49:07.120
folder route and the user could
create a public folder?
00:49:07.170 --> 00:49:10.830
This is a reason why some companies today
have 2 million public folders.
00:49:13.330 --> 00:49:16.290
I pointed this out to the development
engineers and said maybe
00:49:16.340 --> 00:49:20.340
it would be a bad idea to replicate
the faults of the past.
00:49:20.390 --> 00:49:24.810
I was told I am too old. I don't
understand. It's the way of
00:49:24.860 --> 00:49:29.670
the cloud. We're making users collaborate
better. They say they
00:49:29.720 --> 00:49:32.380
are going to be collaborating so
much that they will be creating
00:49:32.430 --> 00:49:34.910
groups from here to the end of eternity
and then we will be trying
00:49:34.960 --> 00:49:36.830
to delete them until the end of eternity.
00:49:38.920 --> 00:49:42.550
Again, it's an example. It's a clash
of the kind of on prem environment
00:49:42.600 --> 00:49:44.910
and the clash with the cloud environment
that you have to get
00:49:44.960 --> 00:49:47.290
your head around. I still like it.
00:49:48.390 --> 00:49:51.400
The next thing we have to discuss
is how do you know when any
00:49:51.450 --> 00:49:52.920
of this stuff changes.
00:49:54.430 --> 00:50:04.180
Whispery clouds are extraordinarily
difficult to stand on our document.
00:50:05.710 --> 00:50:11.300
TechNet, our friend, your source
of wisdom for years, boy it
00:50:11.350 --> 00:50:12.530
struggles with the cloud.
00:50:14.150 --> 00:50:16.490
The writers or human and
they are like us.
00:50:17.290 --> 00:50:20.500
They find it difficult to know what's
going on and so you can't
00:50:20.550 --> 00:50:23.990
depend on TechNet. It really,
really struggles.
00:50:24.550 --> 00:50:29.740
And you can't take Exchange on prem
content and read it directly
00:50:29.790 --> 00:50:32.570
into the cloud because of the
differences that exist.
00:50:32.620 --> 00:50:33.880
That's a health warning.
00:50:36.400 --> 00:50:43.160
When you have features like Delve
or Office 365 Groups or Clutter
00:50:43.210 --> 00:50:47.640
or People View are introduced, they
are normally introduced with
00:50:47.690 --> 00:50:49.440
a total lack of documentation.
00:50:50.450 --> 00:50:53.540
They are normally introduced with
the total lack of advice or
00:50:53.590 --> 00:50:55.900
guidance or whatever. You
might get a blog post.
00:50:57.750 --> 00:51:02.580
I like a lot of the people, some
of whom are in this room who
00:51:02.630 --> 00:51:04.800
write for blogs.office.com.
00:51:06.010 --> 00:51:07.670
I do really like you guys.
00:51:08.770 --> 00:51:13.070
But let's face it. You are marketeers
and you sometimes don't
00:51:13.120 --> 00:51:15.920
write at the level that
technologists require.
00:51:16.730 --> 00:51:18.730
It would be nice if you
did, but you don't.
00:51:20.020 --> 00:51:25.660
A post on the office.com site is
not exactly documentation.
00:51:25.970 --> 00:51:29.670
Anyway, blogs are like dead fish.
Why are blogs like dead fish?
00:51:32.270 --> 00:51:35.370
Three days, yeah, after three
days they're out-of-date.
00:51:36.100 --> 00:51:39.550
In the clouds a blog is out of
date after three days, so you
00:51:39.600 --> 00:51:42.830
have to bear that in mind. And
there are lots of great blogs.
00:51:44.210 --> 00:51:48.130
MVPs, Microsoft customers, other
folk, they go and they write
00:51:48.180 --> 00:51:52.200
blogs and it's great, lots of advice,
but really, really you
00:51:52.250 --> 00:51:58.110
have to take account of the fact that
the time they write something
00:51:58.770 --> 00:51:59.940
is not necessarily
00:52:01.230 --> 00:52:03.470
reporting exactly what you
see in front of you.
00:52:04.970 --> 00:52:08.540
I won't even start talking about
all of the troubles of keeping
00:52:08.590 --> 00:52:09.650
books updated.
00:52:10.880 --> 00:52:11.370
How do
00:52:13.880 --> 00:52:17.840
we track change? First thing is,
I think that any of you, it
00:52:17.890 --> 00:52:23.360
would be very wise that you take
a trial domain. Go and get
00:52:23.410 --> 00:52:29.020
a test domain in Office 365 and go
and only by a couple of licenses
00:52:29.070 --> 00:52:33.080
in it, but put it into the
first release program.
00:52:34.230 --> 00:52:37.320
You can keep your production domain.
That's standard release,
00:52:37.370 --> 00:52:40.620
but at least that first release
domain will allow you to see
00:52:40.670 --> 00:52:44.020
what's coming. It will allow you
to play with the stuff and it
00:52:44.070 --> 00:52:46.580
will allow you to figure out what's
happening and it will allow
00:52:46.630 --> 00:52:48.250
you to prepare for your users.
00:52:49.130 --> 00:52:53.260
Second place, definitely keep an
eye on the Office 365 roadmap.
00:52:53.820 --> 00:52:57.420
In particular, look at the part
that says in development.
00:52:58.300 --> 00:53:02.190
That gives you advanced warning.
And then look at the part saying
00:53:02.240 --> 00:53:07.510
rolling out. That tells you what
should be rolling out to first
00:53:07.560 --> 00:53:10.540
to the first release people and
then general availability.
00:53:10.870 --> 00:53:12.170
You need to keep an eye on that.
00:53:12.780 --> 00:53:17.520
Definitely look at the Office 365 blog
to see all of the information.
00:53:18.880 --> 00:53:21.790
It can give you a heads up. Today,
they talked about the new
00:53:21.840 --> 00:53:25.260
Office 365 port service,
so that's a good thing.
00:53:26.100 --> 00:53:27.940
There are lots of other good blogs
out there, but remember the
00:53:27.990 --> 00:53:28.990
health warning.
00:53:29.850 --> 00:53:31.420
And then here's a good thing.
00:53:32.190 --> 00:53:35.340
You should be part of the Office
365 Yammer network.
00:53:35.970 --> 00:53:39.240
I never thought I would say you should
be part of and then Yammer
00:53:39.290 --> 00:53:40.870
network in the same sentence.
00:53:43.000 --> 00:53:48.170
I really didn't. Anyhow, now that
I've purged my soul on that
00:53:48.220 --> 00:53:52.090
one I'm sure I'll hear about that
one in Twitter later on.
00:53:53.380 --> 00:53:57.780
There is actually a very nice group
in Yammer called Change Alerts
00:53:57.830 --> 00:54:03.290
which is driven by members of the
network who have noticed things
00:54:03.340 --> 00:54:07.110
changing in their Office 365 tenant.
They are bringing it to
00:54:07.160 --> 00:54:11.190
the notice of others that are there.
That's a great public service
00:54:11.240 --> 00:54:13.230
and you should be part of
that public service.
00:54:13.790 --> 00:54:15.390
And then there is Twitter.
00:54:16.590 --> 00:54:20.050
Twitter at one stage was called
the only reliable indication
00:54:20.100 --> 00:54:24.420
of service health a cause if something
went down in Office 365
00:54:24.470 --> 00:54:27.770
you found out about it quickest in
Twitter. I still think Twitter
00:54:27.820 --> 00:54:31.560
is a very good place to find out
what's happening and you should
00:54:31.610 --> 00:54:32.890
probably think about that.
00:54:34.190 --> 00:54:35.550
Something about interfaces,
00:54:38.220 --> 00:54:42.360
starting off with how you
interact with Office 365.
00:54:42.950 --> 00:54:47.030
It's important to say that the administration
interfaces do occur
00:54:47.080 --> 00:54:51.040
in different places. You form tasks
two different interfaces.
00:54:51.090 --> 00:54:56.270
It is sometimes frustrating to see
that there are so many different
00:54:56.320 --> 00:55:00.290
ways of doing it. I is doing a lot
of work to try to bring all
00:55:00.340 --> 00:55:02.700
of those interfaces together, but
I think it's inevitable because
00:55:02.750 --> 00:55:06.620
let's face it. We're still only a
couple of years down this cloud
00:55:06.670 --> 00:55:10.990
journey and a lot of the interfaces
that we see out there are
00:55:11.040 --> 00:55:15.130
interfaces that are inherited from
the on premises environment.
00:55:15.180 --> 00:55:19.570
Look at the Exchange Administration
Console. It's going to take
00:55:19.620 --> 00:55:23.920
time for us to see a truly unified
view of Office 365 administration.
00:55:23.970 --> 00:55:27.840
Just be prepared to do things
in different places.
00:55:30.050 --> 00:55:33.120
Some tools that you can use, clearly
there is the Admin Portal
00:55:33.170 --> 00:55:36.980
and the Exchange Administration Center,
that in particular should
00:55:37.030 --> 00:55:39.510
be very useful to you.
00:55:40.390 --> 00:55:43.310
There's the Azure Active Directory
Portal with full figure out
00:55:43.360 --> 00:55:45.810
stuff about what's being
replicated up to Azure.
00:55:46.560 --> 00:55:50.480
And then there's this Office 365
Admin App. I was talking to
00:55:50.530 --> 00:55:53.580
the program manager of this app
the other day. He gave me a
00:55:53.630 --> 00:55:57.510
bit of a shock because he came
up to me and he said I wanted
00:55:57.560 --> 00:56:00.250
to talk to you about what you have
been writing about my application.
00:56:00.700 --> 00:56:03.280
And I thought I was going to get
hit or something like that.
00:56:03.330 --> 00:56:04.290
What had I said?
00:56:04.850 --> 00:56:08.630
I was frantically thinking who have
I offended in the last six months?
00:56:10.120 --> 00:56:12.660
That was a long list,
actually. That was
00:56:15.370 --> 00:56:19.620
a very long list. Anyhow, we talked
a bit and then I said how
00:56:19.670 --> 00:56:21.840
old are you? And he said 23.
00:56:22.990 --> 00:56:24.840
And that's when I felt old.
00:56:27.050 --> 00:56:30.050
This is a great app. It's
updated every two weeks,
00:56:31.310 --> 00:56:34.180
so there are new versions of it
every two weeks. And it is nice
00:56:34.230 --> 00:56:36.130
to be able to carry it
around in your pocket.
00:56:37.320 --> 00:56:39.940
An app that shows you what is happening
on the service and what
00:56:39.990 --> 00:56:43.630
service messages are coming up and
they're adding more and more
00:56:43.680 --> 00:56:47.390
bits to it. It's still got a way
to go, but this is definitely
00:56:47.440 --> 00:56:51.560
a thing to track. Then there is
PowerShell. Of course there
00:56:51.610 --> 00:56:55.760
is PowerShell. PowerShell always
works and it's great.
00:56:56.440 --> 00:56:59.380
And you should use it.
00:57:00.370 --> 00:57:01.310
It's reduced.
00:57:02.240 --> 00:57:03.360
Why is it reduced?
00:57:04.000 --> 00:57:05.960
There is so much stuff that is
so behind the scenes that you
00:57:06.010 --> 00:57:08.500
don't need to get involved with,
but there is still a lot of
00:57:08.550 --> 00:57:09.770
PowerShell there that you can use.
00:57:10.620 --> 00:57:16.050
It is important that you look at
on prem scripts and test them
00:57:16.100 --> 00:57:19.230
before attempting to use them in
production with Exchange Online
00:57:19.280 --> 00:57:22.460
because it's likely the stuff will
break. It's very likely that
00:57:22.510 --> 00:57:24.860
stuff will break. In particular,
you are going to have to think
00:57:24.910 --> 00:57:28.270
about authentication, things like
if you want to send e-mail
00:57:28.320 --> 00:57:30.680
and stuff like that, think
about authentication.
00:57:31.390 --> 00:57:35.600
The general routine inside your
scripts or inside a PowerShell
00:57:35.650 --> 00:57:37.980
session you are going to be connecting
to Exchange Online.
00:57:38.030 --> 00:57:44.190
That's very similar to connecting
to PowerShell inside on prem
00:57:44.240 --> 00:57:46.940
because it's remote PowerShell. Remember
that PowerShell started
00:57:46.990 --> 00:57:49.810
it off and it was just a direct
connection to the server you
00:57:49.860 --> 00:57:52.360
are on? And then it went
to a remote connection?
00:57:53.620 --> 00:57:57.480
You use the exact same technology
in Exchange Online. It will
00:57:57.530 --> 00:58:01.050
then load all of the Exchange cmdlets.
00:58:01.720 --> 00:58:04.530
Note that there are some special
cmdlets if you want to deal
00:58:04.580 --> 00:58:08.990
with the client center. That's documented
online. You may also
00:58:09.040 --> 00:58:13.800
want to load a set of cmdlets to deal
with Microsoft online services.
00:58:14.100 --> 00:58:17.280
If you want to deal with licenses
or you want to deal with user
00:58:17.330 --> 00:58:22.560
accounts, you need those cmdlets,
and then there are other ones
00:58:22.610 --> 00:58:24.130
like Azure Active Directory.
00:58:26.250 --> 00:58:29.500
Terms of clients, I said the latest
are strongly recommended.
00:58:30.320 --> 00:58:34.250
A thing to remember about Outlook web
app is that it is the experimental
00:58:34.300 --> 00:58:41.440
platform for Exchange Online. New features
show up here all the time.
00:58:42.400 --> 00:58:51.990
It's because Outlook it can't just
change its user interface
00:58:52.040 --> 00:58:55.800
quickly enough to deal with the
new functionality, but they can
00:58:55.850 --> 00:58:58.160
make changes behind the scenes for
Outlook Web App and a bang,
00:58:58.210 --> 00:59:00.000
there you go.
00:59:01.060 --> 00:59:05.300
It's a really nice client now. I
didn't really like it when it
00:59:05.350 --> 00:59:08.970
came out first in Exchange 2013, but
I think it has evolved tremendously.
00:59:09.500 --> 00:59:13.800
I especially like it if you are
on a flaky connection because
00:59:13.850 --> 00:59:17.460
it's so much less demanding on
the network then Outlook is.
00:59:18.640 --> 00:59:23.350
Interestingly, Outlook is still
the most prevalent client used
00:59:23.400 --> 00:59:25.020
to connect to Exchange Online.
00:59:26.870 --> 00:59:33.260
IOS is the most popular mobile client
despite the fact that android
00:59:33.690 --> 00:59:34.840
has the market share.
00:59:36.780 --> 00:59:42.550
It's clear that the mobile client strategy
is in flux at the moment.
00:59:42.600 --> 00:59:45.740
We have seen that the client, the
Outlook for iOS and Outlook
00:59:45.790 --> 00:59:48.590
for android client evolving
very quickly.
00:59:49.380 --> 00:59:53.350
Windows 10 will bring universal
client for Windows Phone.
00:59:54.910 --> 00:59:57.690
It's hard to keep up with times.
It is really hard to keep up.
01:00:00.060 --> 01:00:03.560
Second most popular thing, we've had
migration. Let's talk about support.
01:00:05.840 --> 01:00:09.470
Generally, Office 365 has a
very good SLA record, but
01:00:10.900 --> 01:00:16.390
things will happen. The DevOps model,
which means that the developers
01:00:16.440 --> 01:00:20.760
actually work on the service, they
support the service. If a
01:00:20.810 --> 01:00:24.190
code goes bad they go fix it. It
helps keep people very focused,
01:00:24.240 --> 01:00:25.420
but things happen.
01:00:26.470 --> 01:00:29.370
It's important to say that if you
go and look at the service
01:00:29.420 --> 01:00:35.010
dashboard and you see a red mark
against something like Exchange
01:00:35.060 --> 01:00:38.230
or SharePoint or something like
that, that may not necessarily
01:00:38.280 --> 01:00:42.430
be of any consequence to you. It may
affect something in a completely
01:00:42.480 --> 01:00:43.550
different region.
01:00:44.240 --> 01:00:46.940
There might be millions of mailboxes
but you don't care because
01:00:46.990 --> 01:00:48.240
you just keep on working.
01:00:49.520 --> 01:00:52.040
That's one of the problems that
we've got that Microsoft has
01:00:52.090 --> 01:00:55.810
to work on is to be able to filter
all of the signals that they
01:00:55.860 --> 01:00:59.260
gather which allow them to
know when I have problems.
01:01:00.050 --> 01:01:04.230
Instead of providing you with a
global view of how it is across
01:01:04.280 --> 01:01:09.070
the entire service, to give you a view
of what affects a particular tenant.
01:01:09.120 --> 01:01:11.270
That would be really nice. I believe
they're working on that,
01:01:11.320 --> 01:01:12.510
so that's good.
01:01:14.050 --> 01:01:18.020
The dashboard tells you what's going
on in any particular instance.
01:01:19.760 --> 01:01:21.860
I said to one of the engineers
working on this that it would
01:01:21.910 --> 01:01:24.530
be nice if some of the explanations
were in English from time
01:01:24.580 --> 01:01:25.170
to time.
01:01:25.780 --> 01:01:29.660
Some of them are written in engineereez
which is a special language
01:01:29.710 --> 01:01:31.200
used by support people.
01:01:33.480 --> 01:01:34.310
For you guys,
01:01:35.570 --> 01:01:38.820
here's one that we have when we
are working on the book, just
01:01:38.870 --> 01:01:40.740
to show you how it happens.
01:01:41.790 --> 01:01:44.500
I collaborated with Michael van
Hornenbig in Belgium and Paul
01:01:44.550 --> 01:01:45.770
Cunningham in Australia.
01:01:46.340 --> 01:01:49.190
Paul gets up early because he's
in Australia and they get up
01:01:49.240 --> 01:01:52.980
in the middle of the night or something
like that. Anyway, 7 A.M.
01:01:53.030 --> 01:01:56.220
On 7th of April, a week before we
close off the text of the book,
01:01:56.750 --> 01:02:00.120
Paul sends me a message, I can't
find any of the files.
01:02:00.170 --> 01:02:01.360
They've all gone away.
01:02:01.960 --> 01:02:05.300
This is in our SharePoint
document library.
01:02:05.810 --> 01:02:08.480
That wasn't a good start to the
day, as you can imagine.
01:02:08.530 --> 01:02:12.580
There was absolutely nothing available
on Twitter. There was
01:02:12.630 --> 01:02:16.910
absolutely nothing available on the service
dashboard. It just happened.
01:02:18.140 --> 01:02:22.290
That's a very recent example of how
things can happen. You know why?
01:02:23.210 --> 01:02:27.040
Despite the mild panic that we
went through it was just that
01:02:27.090 --> 01:02:30.700
behind the scenes somebody was changing
a network appliance in
01:02:30.750 --> 01:02:31.840
a data center.
01:02:32.580 --> 01:02:36.740
Because that network appliance
change was, let's put it like
01:02:36.790 --> 01:02:41.580
this, was slightly screwed up and
didn't work, all of a sudden
01:02:41.630 --> 01:02:45.510
service disappeared to a select
group of tenants including the
01:02:45.560 --> 01:02:48.340
one we were using. So
these things happen.
01:02:49.530 --> 01:02:50.590
It's just part of life.
01:02:52.990 --> 01:02:56.640
This is the detail.
We don't need that.
01:02:57.430 --> 01:02:58.650
Support is different.
01:02:59.170 --> 01:03:02.500
Remember, you don't have any control
over all of the stuff that
01:03:02.550 --> 01:03:04.820
is happening. Here is
some advice for you.
01:03:06.080 --> 01:03:10.450
When you get on the phone and talk
to a front level support person
01:03:11.640 --> 01:03:14.500
try to make the experience as pleasant
for both of you as you
01:03:14.550 --> 01:03:20.370
possibly can. Please. They will
appreciate it and so will you.
01:03:21.080 --> 01:03:25.190
It's going to be entirely exasperating
if you get on the phone
01:03:25.240 --> 01:03:29.670
with these guys and you don't have
details about your environment.
01:03:31.180 --> 01:03:34.520
They can't go behind the scenes and
start looking up stuff about
01:03:34.570 --> 01:03:37.620
your data. That is not
the way things happen.
01:03:38.410 --> 01:03:42.380
They are there at the first level
to filter, to eliminate the
01:03:42.430 --> 01:03:46.770
easy cases, to help you understand
what's going on so that maybe
01:03:46.820 --> 01:03:49.970
you can solve the problem, so prepare.
01:03:50.570 --> 01:03:55.650
Understand what's happening and be
prepared to give that information
01:03:55.700 --> 01:03:56.580
to support.
01:03:57.240 --> 01:03:58.970
Document everything.
01:04:00.250 --> 01:04:04.580
Document all interactions you have
and understand that it's going
01:04:04.630 --> 01:04:07.670
to take time to resolve things
if they need to escalate.
01:04:08.620 --> 01:04:14.200
Don't hesitate to ask for a support
problem to be escalated,
01:04:14.970 --> 01:04:18.010
but be fair with people, with
these guys. If you go and ask
01:04:18.060 --> 01:04:20.970
for everything to be escalated,
that's not going to be helpful.
01:04:21.690 --> 01:04:24.710
Ask to escalate if you need escalation,
if it's a really important
01:04:24.760 --> 01:04:27.330
problem, because you are the only
one that understands the full
01:04:27.380 --> 01:04:32.580
context of the problem. And do remember
to cover all those basics.
01:04:33.230 --> 01:04:39.550
A little thing about reporting, out-of-the-box,
Office 365 gives
01:04:39.600 --> 01:04:44.040
you basic reports for many aspects of
the service, which is pretty good.
01:04:44.810 --> 01:04:47.960
There is a very interesting data
mark behind the scenes.
01:04:48.350 --> 01:04:51.920
This is where all of the information
is gathered and stored for
01:04:51.970 --> 01:04:53.080
up to 90 days.
01:04:56.010 --> 01:04:58.820
You can then use it, there is a
set of PowerShell cmdlets to
01:04:58.870 --> 01:05:02.980
get that information out of it or
you can export stuff to Excel
01:05:03.030 --> 01:05:05.420
and play around with it and all
the rest of it. There's also
01:05:05.470 --> 01:05:09.730
a group of third parties that do
a good job of making sense of
01:05:09.780 --> 01:05:13.300
it, so if you are interested in grabbing
stuff out of the service,
01:05:13.350 --> 01:05:15.980
go and talk to some of them and
I think some of them, most of
01:05:16.030 --> 01:05:17.860
them here, I'm not sure about
the rest of them here.
01:05:18.520 --> 01:05:23.790
In terms of monitoring it's really
difficult or impossible to
01:05:23.840 --> 01:05:26.470
be looking at Office
365 all the time.
01:05:27.510 --> 01:05:31.380
I think you probably want to consider
some third-party monitoring
01:05:31.430 --> 01:05:36.430
tools to help you automate the process
and I mentioned a couple here.
01:05:36.480 --> 01:05:37.990
Some of these folks are here today.
01:05:38.770 --> 01:05:42.910
Important, as I said earlier with
the migration tools, test and
01:05:42.960 --> 01:05:44.330
figure out what's good for you.
01:05:47.350 --> 01:05:52.850
A lot of people wonder is Microsoft
just going away from on premises?
01:05:52.900 --> 01:05:55.540
Is there any benefit whatsoever
of this cloud stuff?
01:05:55.590 --> 01:05:58.400
Actually, there is, because there
is lots of technology that
01:05:58.450 --> 01:06:00.830
has been transferred from the cloud.
01:06:02.260 --> 01:06:06.020
Specifically in these areas, lots
of automation stuff, lots of
01:06:06.070 --> 01:06:10.200
easier debugging, MAPI over HTTP
is much easier to figure out
01:06:10.250 --> 01:06:14.640
what's going on than the old way.
There's a lot more administrative
01:06:14.690 --> 01:06:17.880
flexibility that is being built-in,
Role-based Access Control,
01:06:17.930 --> 01:06:18.830
for example.
01:06:19.670 --> 01:06:22.230
That would probably exist unless
we were going for cloud.
01:06:22.790 --> 01:06:29.870
Client flexibility, the fact that can OWA
can change with new functionality.
01:06:30.470 --> 01:06:34.580
And even things like the way Autodiscover
has expanded its capabilities
01:06:34.630 --> 01:06:38.230
over the last couple of years so
that's able to provide back
01:06:38.280 --> 01:06:42.290
in its XML manifest a complete snapshot
of all of the resources
01:06:42.340 --> 01:06:43.750
that the client is able to have.
01:06:44.260 --> 01:06:48.010
This has all come as a result
of cloud technology.
01:06:49.080 --> 01:06:50.200
It's been pretty good.
01:06:51.170 --> 01:06:54.880
Some features are never going to
transition and here's why.
01:06:54.930 --> 01:07:00.820
They are either too complex, too
costly, too many moving parts,
01:07:01.600 --> 01:07:07.580
too many things to tweak or too
much inertia in enterprise IT.
01:07:07.630 --> 01:07:12.010
I don't think that many enterprise
IT departments will be capable
01:07:12.060 --> 01:07:15.820
or would be capable of setting up
the kind of environment that's
01:07:15.870 --> 01:07:19.110
required to drive something like
Delve or the Office Graph.
01:07:21.000 --> 01:07:23.870
Nobody's going to pay for the amount
of hardware that's used
01:07:24.640 --> 01:07:28.670
to do the machine learning that's
required to figure out how
01:07:28.720 --> 01:07:32.820
to filter mail messages for Clutter.
It's just not going to happen.
01:07:32.870 --> 01:07:35.610
And let's face it. None of
us like upgrading stuff.
01:07:37.880 --> 01:07:41.780
Enterprise IT generally breaks
out in boils any time it aches
01:07:41.830 --> 01:07:43.190
about an upgrade.
01:07:44.230 --> 01:07:46.940
Whereas, in the cloud everything
is being upgraded all the time
01:07:46.990 --> 01:07:48.700
because it's a constant feedback.
01:07:50.030 --> 01:07:53.970
For all of these reasons, you are
not going to see some things
01:07:54.540 --> 01:07:57.540
on premises.
01:07:58.500 --> 01:08:03.210
Those things are things like Delve,
like Clutter, like People
01:08:03.260 --> 01:08:06.690
View maybe. I don't know. The Microsoft
people used to say I
01:08:06.740 --> 01:08:08.790
don't know. But definitely Delve,
01:08:10.670 --> 01:08:14.150
Clutter and the Office Graph because
they all depend on this
01:08:14.200 --> 01:08:15.490
Office Graph technology.
01:08:19.030 --> 01:08:23.950
As we aim towards the finish line
here, I think it is important
01:08:24.000 --> 01:08:25.910
to think about a back-out plan.
01:08:25.960 --> 01:08:30.520
I think it really is because the
cloud may not work for you.
01:08:31.650 --> 01:08:32.670
It may not work
01:08:34.350 --> 01:08:38.420
for you. The situation may be that
it will work for you in five
01:08:38.470 --> 01:08:40.950
years time, but won't
work for you now.
01:08:42.180 --> 01:08:46.290
Maybe you think about how if you
do go to Office 365 how are
01:08:46.340 --> 01:08:49.610
you going to get back out. As it
turns out, mailboxes are easy.
01:08:50.140 --> 01:08:53.440
It's all the other stuff that you
move across that isn't so easy
01:08:53.490 --> 01:08:56.980
because whereas, Microsoft is giving
you things like the mailbox
01:08:57.030 --> 01:09:00.700
replication service and the Hybrid
Configuration Wizard for Exchange,
01:09:01.080 --> 01:09:05.640
there's nothing really there for
SharePoint or OneDrive or videos
01:09:05.690 --> 01:09:06.470
or whatever.
01:09:07.350 --> 01:09:10.350
So before you move, maybe one to
think about what is the back-out
01:09:10.400 --> 01:09:14.420
plan just in case. I hope you never
get to here. Very few people
01:09:14.470 --> 01:09:18.620
once they go over to Office 365 want
to come back out, but there
01:09:18.670 --> 01:09:20.360
are going to be situations.
01:09:23.600 --> 01:09:27.670
In closing, there are some
keys to success I think.
01:09:29.600 --> 01:09:31.970
Clearly, it's good to know what
you are getting into, good to
01:09:32.020 --> 01:09:36.220
know how you want to use the service,
01:09:37.540 --> 01:09:40.500
and you can only do that by figuring
out exactly how you use
01:09:40.550 --> 01:09:44.560
on premises software today, and how
you can map that into the cloud.
01:09:46.520 --> 01:09:50.140
Make the decision to go to the
cloud for the right reasons.
01:09:50.190 --> 01:09:54.470
Don't just go because some sales
guy tells you it's six dollars
01:09:54.730 --> 01:09:59.590
a mailbox a month. That is
the worst possible reason.
01:10:00.860 --> 01:10:06.090
Have good business, yes economic,
but also technology and business
01:10:06.140 --> 01:10:09.020
centric reasons for going to the
cloud and you will be okay.
01:10:10.000 --> 01:10:12.590
I said earlier solid project management
is important. I will
01:10:12.640 --> 01:10:17.840
repeat it again. Solid project management
gets you to the cloud successfully.
01:10:18.940 --> 01:10:22.620
Don't underestimate the migration
effort because it is the detail
01:10:22.670 --> 01:10:26.170
that catches you. Moving mailboxes
is easy. It's all the detail
01:10:26.220 --> 01:10:29.950
around it, like making sure all of
the users have the right clients,
01:10:30.000 --> 01:10:31.060
that kind of thing.
01:10:32.480 --> 01:10:36.590
Move workload at a rate that is
acceptable to the company.
01:10:38.020 --> 01:10:41.310
Some parts of the company might be more
amenable to change then others.
01:10:41.360 --> 01:10:44.660
They are great candidates to go
first. And remember, by the
01:10:44.710 --> 01:10:49.310
way, the old thing that we've done
for years was on premises
01:10:49.360 --> 01:10:53.890
migrations, always move
delegates together.
01:10:56.350 --> 01:11:00.730
If somebody has got a delegated
access to a mailbox, they go
01:11:00.780 --> 01:11:05.650
with that mailbox. Don't try to
do cross premises delegation.
01:11:06.550 --> 01:11:10.350
Don't try it. Something will break.
It may not break immediately,
01:11:10.400 --> 01:11:13.350
but you can be guaranteed it will
break over time and you will
01:11:13.400 --> 01:11:14.310
be responsible.
01:11:16.750 --> 01:11:21.120
After all of that, that was quite
a quick run through. I really
01:11:21.170 --> 01:11:24.980
think that Office 365 is on a roll.
It's got tremendous velocity.
01:11:25.260 --> 01:11:28.310
It's a tremendous service. There
is no doubt about that.
01:11:28.360 --> 01:11:31.480
Exchange is by far the easiest
workload to move
01:11:32.890 --> 01:11:37.230
and it's the reason why I think Office
365 has that velocity today.
01:11:37.280 --> 01:11:38.720
And that's pretty good.
01:11:39.460 --> 01:11:42.300
There is lots of potential once you
are over there. There's lots
01:11:42.350 --> 01:11:43.550
of good stuff happening,
01:11:44.900 --> 01:11:48.030
but planning is absolutely critical.
01:11:48.540 --> 01:11:51.560
With that, and with one minute left,
01:11:52.810 --> 01:11:53.540
I'm done.
01:12:00.680 --> 01:12:03.720
But there's more. There's more.
We have two T-shirts to give
01:12:03.770 --> 01:12:07.010
out to those that ask questions.
You have to ask questions.
01:12:07.720 --> 01:12:08.390
Who is first?
01:12:09.130 --> 01:12:11.060
Who's first? There's a microphone.
01:12:12.050 --> 01:12:16.350
>> I have a question. You said that
whether so many 365 servers
01:12:16.400 --> 01:12:19.060
and so any new updates
rollout over time.
01:12:19.750 --> 01:12:22.710
How long before the first update
is applied to the last one for
01:12:22.760 --> 01:12:23.960
a particular build?
01:12:24.010 --> 01:12:27.480
>> Okay. Given that we have this
huge infrastructure, tons and
01:12:27.530 --> 01:12:31.620
tons and tons of servers, how long
does it take to get out an update?
01:12:33.210 --> 01:12:37.150
I don't do the updates and someone
else would be in a better
01:12:38.160 --> 01:12:43.020
position, but my observation is
that it probably could take up
01:12:43.070 --> 01:12:47.090
to a couple of months depending on
the complexity to get everywhere.
01:12:47.140 --> 01:12:49.800
I mean there are some people and
Delve is a good example.
01:12:49.850 --> 01:12:52.860
It went general availability in
mid-April. I was talking to
01:12:52.910 --> 01:12:55.430
a guy today and he still hasn't
seen it in his tenant.
01:12:56.440 --> 01:12:58.320
So it can take a while.
01:12:59.240 --> 01:12:59.590
Sir?
01:13:00.730 --> 01:13:04.800
>> We are in the process right now of
integrating the online archiving
01:13:05.090 --> 01:13:07.320
and we are going through the hurdle
of getting rid of all the
01:13:07.370 --> 01:13:08.140
PST files.
01:13:08.700 --> 01:13:13.090
One of the things that we are facing
right now is a lot of the
01:13:13.140 --> 01:13:16.920
people that are using Apple Mail
and they are having inbox files
01:13:16.970 --> 01:13:20.140
as their archives. Have you ever
run across any situations where
01:13:20.190 --> 01:13:23.290
you have had to try to get those
inbox files moved over to the
01:13:23.340 --> 01:13:24.410
online archiving?
01:13:25.910 --> 01:13:27.060
>> Their inbox files?
01:13:27.820 --> 01:13:30.980
>> It's .mbox is the extension.
01:13:32.020 --> 01:13:35.100
>> It's a different format.
I don't do that.
01:13:36.370 --> 01:13:37.280
Sorry, no.
01:13:38.940 --> 01:13:40.230
But you can have a T-shirt.
01:13:41.780 --> 01:13:49.250
The wonderful Exchange team tells me
that there are books, printed books?
01:13:51.190 --> 01:13:53.630
There are still some printed books
at the Expo floor for people
01:13:53.680 --> 01:13:55.410
who would want them.
Thank you Brian.
01:13:56.150 --> 01:13:59.600
Expo floor. Next question?
It's downstairs.
01:13:59.650 --> 01:14:04.790
>> Is dedicated Office 365
staying or going away?
01:14:06.090 --> 01:14:08.380
>> Did you have an impression
that I work for Microsoft?
01:14:10.030 --> 01:14:12.710
As an observer, as an independent
observer, I think.
01:14:12.760 --> 01:14:15.630
>> Because if I talk to Microsoft
they are pushing me towards
01:14:15.680 --> 01:14:17.320
multitenant, that is
why I am asking.
01:14:17.370 --> 01:14:20.920
>> Okay. I would think that there
are particular advantages to
01:14:20.970 --> 01:14:24.060
using a dedicated Office 365 tenant.
It's going to cost you
01:14:24.110 --> 01:14:27.060
more money, but you will have more
control, specifically, about
01:14:27.110 --> 01:14:29.990
what hardware you use and what
storage you use et cetera, and
01:14:30.040 --> 01:14:34.590
you get what they call the white
glove service. People are making
01:14:34.640 --> 01:14:37.190
sure that your every wishes
are taking care of.
01:14:38.010 --> 01:14:42.670
Whether or not there is significant
advantage in that, you're
01:14:42.720 --> 01:14:46.170
going to have to tell me. For me,
I think a couple of years ago
01:14:46.220 --> 01:14:50.270
there was great advantage in it.
Now as we have had a really
01:14:50.320 --> 01:14:55.480
good success rate with the
multitenant service,
01:14:56.770 --> 01:14:59.550
I don't know. It's a good question
to have a discussion about,
01:14:59.600 --> 01:15:03.120
but you need context. I don't
have enough context.
01:15:03.170 --> 01:15:06.850
>> Okay. At least Microsoft is pushing
me towards multitenant
01:15:06.900 --> 01:15:10.270
saying that dedicated would be deprecated
sometime, but to avoid
01:15:10.320 --> 01:15:12.140
those surprises for users.
01:15:12.190 --> 01:15:16.370
>> Yeah. A Microsoft person making
this is a bold statement that
01:15:16.420 --> 01:15:21.250
dedicated Office 365 will be deprecated
in the future is an interesting
01:15:21.300 --> 01:15:22.840
position for them to take.
01:15:23.640 --> 01:15:26.920
I haven't heard that from any of
my contacts, but what I suggest
01:15:26.970 --> 01:15:29.970
you do, because I don't work for
Microsoft, is you go down to
01:15:30.020 --> 01:15:33.620
the Expo floor, go to the Office
365 area and find somebody who
01:15:33.670 --> 01:15:35.270
can give you an official answer.
01:15:35.830 --> 01:15:36.340
That's what I would do.
01:15:36.390 --> 01:15:37.300
>> Can I ask one more question?
01:15:37.350 --> 01:15:41.330
>> Well, there are lots of people waiting.
We will be going outside
01:15:41.380 --> 01:15:44.230
a moment because they are
going to turn me off.
01:15:44.280 --> 01:15:49.760
>> Compliance, like international companies,
Germany in particular,
01:15:50.180 --> 01:15:53.910
they all want to get the data outside,
but we share the same namespace.
01:15:53.960 --> 01:15:57.800
How do we move to the cloud?
Microsoft doesn't have.
01:15:57.850 --> 01:16:01.660
>> So this is a common problem when
you have country boundaries
01:16:01.710 --> 01:16:05.480
and you want to maintain data inside
a country. The Microsoft
01:16:05.530 --> 01:16:08.160
answer is they are putting data centers
out as quickly as possible
01:16:08.210 --> 01:16:11.330
to try to get around that. For Germany,
I guess they are going
01:16:11.380 --> 01:16:14.110
to have the Austria data center.
Now that might be helpful,
01:16:15.390 --> 01:16:18.080
but it's really a thing to sit down
with the Microsoft guys in
01:16:18.130 --> 01:16:20.540
a particular country and figure
out what is going to happen.
01:16:21.190 --> 01:16:25.500
I don't have a great answer for it.
And every country is different
01:16:25.550 --> 01:16:29.930
and every company is different
because, you know, if you are
01:16:29.980 --> 01:16:33.200
in the pharmaceutical industry you
are going to be under specific
01:16:33.600 --> 01:16:37.070
regulatory requirements and it
is different if you are in the
01:16:37.120 --> 01:16:39.720
finance industry or working in
agriculture or something like
01:16:39.770 --> 01:16:41.760
that and so it's kind
of hard to say.
01:16:41.810 --> 01:16:46.580
Sorry. Did you notice me dancing
around the answer there? I was
01:16:46.630 --> 01:16:48.000
a consultant for years.
01:16:48.600 --> 01:16:54.430
Sorry, yeah? Here. You can
have the last T-shirt.
01:16:55.840 --> 01:16:57.760
>> What about AV and anti-spam?
01:16:58.480 --> 01:16:58.820
>> What about?
01:16:58.870 --> 01:17:02.090
>> AV and anti-spam.
01:17:03.100 --> 01:17:03.850
>> Anti-spam.
01:17:06.240 --> 01:17:08.150
>> Specific rules, did
01:17:09.390 --> 01:17:11.820
we lose control of that?
01:17:11.870 --> 01:17:14.770
>> If it's a third-party cloud service
you can always keep on
01:17:14.820 --> 01:17:16.710
routing stuff to that.
01:17:17.420 --> 01:17:18.260
You can keep it.
01:17:18.990 --> 01:17:21.390
Out-of-the-box Microsoft is going
to give you Exchange Online
01:17:21.440 --> 01:17:25.600
protection, but if you decide that
Exchange Online section isn't
01:17:25.650 --> 01:17:29.240
for you, then you just wrap your mail
stream through the third-party
01:17:29.290 --> 01:17:32.820
service, have it cleansed and have
it then be delivered to Office
01:17:32.870 --> 01:17:36.430
365 and it will be as clean as a
whistle. And you'll be as happy
01:17:36.480 --> 01:17:37.440
as the day is long.
01:17:37.490 --> 01:17:42.950
>> What about the other way? From,
can you configure your e-mail
01:17:43.000 --> 01:17:49.910
flow from your Exchange tenant through
cloud service third-party?
01:17:50.800 --> 01:17:54.600
>> It depends on the cloud service
and it depends if you are hybrid
01:17:54.650 --> 01:17:57.080
or pure cloud. Are you
hybrid or pure cloud?
01:17:57.130 --> 01:17:58.350
>> No. We are on prem.
01:17:59.030 --> 01:18:00.930
>> Right. So you are on prem, so
you are probably going to be
01:18:00.980 --> 01:18:04.730
hybrid eventually, so in that case
you can figure stuff so that
01:18:04.780 --> 01:18:07.450
is always going to go back through
your on prem servers.
01:18:07.900 --> 01:18:10.680
Once a goes to those servers you
can put it wherever you like.
01:18:10.730 --> 01:18:16.880
>> Sure, but when we go up to the
cloud do they have flexibility
01:18:17.830 --> 01:18:20.350
for your e-mail to go through.
01:18:20.400 --> 01:18:23.020
>> I don't have a good answer for
that straightaway, but again,
01:18:23.070 --> 01:18:25.910
down on the Expo floor you actually
have realized engineers.
01:18:26.490 --> 01:18:28.320
They are the ones wearing the pointy
hats. Now. They are not
01:18:28.370 --> 01:18:30.660
the ones wearing the pointy hats.
They are great guys down on
01:18:30.710 --> 01:18:33.320
the floor. And I would ask
them. Is that fair?
01:18:33.370 --> 01:18:33.720
>> Yes.
01:18:35.820 --> 01:18:41.730
>> No. It's not fair. All right.
I am going to close down now
01:18:41.780 --> 01:18:44.920
because they are going to get the
room ready for the next session.
01:18:45.530 --> 01:18:46.210
Thank you.