WEBVTT
00:00:00.590 --> 00:00:03.380
All right, we are almost at time,
about a minute.
00:00:03.380 --> 00:00:05.470
And certainly the introduction
will take a little bit, so
00:00:05.470 --> 00:00:07.440
it's okay if folks
are still rolling in.
00:00:08.510 --> 00:00:09.555
Welcome to the end of Ignite.
00:00:10.700 --> 00:00:12.650
Great job, I think, on all parts.
00:00:12.650 --> 00:00:16.890
I think the attendees and
feedback and questions and
00:00:16.890 --> 00:00:20.700
everything throughout the event has
been really, really energizing for
00:00:20.700 --> 00:00:21.690
myself and the team.
00:00:21.690 --> 00:00:24.810
I've talked to a lot of
the engineering folks over the days
00:00:24.810 --> 00:00:27.342
and they just are really inspired
certainly to get the right
00:00:27.342 --> 00:00:30.270
questions, get the right feedback.
00:00:30.270 --> 00:00:32.230
They're very much taking
a humble approach, and
00:00:32.230 --> 00:00:34.020
I think they have already.
00:00:34.020 --> 00:00:35.270
But from the leadership,
00:00:35.270 --> 00:00:39.050
top down, hopefully you're seeing
what feels like a new Microsoft.
00:00:39.050 --> 00:00:40.490
I don't think it's net new.
00:00:40.490 --> 00:00:42.630
I actually think we've been
moving this direction.
00:00:42.630 --> 00:00:45.290
But with a lot of what Satya
is doing on down through
00:00:45.290 --> 00:00:47.440
some of the new leaders,
even for SharePoint and
00:00:47.440 --> 00:00:50.610
OneDrive, they're under a new
engineering leadership.
00:00:50.610 --> 00:00:54.870
They definitely are able
to go at a pace that works,
00:00:54.870 --> 00:00:57.570
working with the right
communication work streams.
00:00:57.570 --> 00:01:00.480
And certainly my job is to work
with engineering to make sure that
00:01:00.480 --> 00:01:05.830
what they're doing is well known and
timely so we're not falling behind.
00:01:05.830 --> 00:01:09.880
But the intent of the session today
is really to be that catch-all.
00:01:09.880 --> 00:01:12.260
Any questions that you didn't
find the right person,
00:01:12.260 --> 00:01:14.490
I may not be that right person,
just to be very clear.
00:01:14.490 --> 00:01:19.280
I'm not your deep hardcore developer
and I'm not a deep IT pro.
00:01:19.280 --> 00:01:21.680
But I work with all of them and
I'm certainly on the team and
00:01:21.680 --> 00:01:22.880
I've been for a while.
00:01:22.880 --> 00:01:24.800
So I'm pretty aware of
everything that we're doing.
00:01:24.800 --> 00:01:29.230
I may lightly answer a question and
refer you to either somebody else or
00:01:29.230 --> 00:01:30.830
some other set of materials.
00:01:30.830 --> 00:01:33.690
But certainly, hopefully, it's more
of a question of did I hear this,
00:01:33.690 --> 00:01:37.100
did I hear that, or
what about this, or I don't know.
00:01:37.100 --> 00:01:41.030
So I'm really gonna open it up after
about ten minutes for questions.
00:01:41.030 --> 00:01:43.420
It's a format I think
you've seen the MVP's do,
00:01:43.420 --> 00:01:48.380
it's a format that I've seen a
number of other teams cross Office,
00:01:48.380 --> 00:01:51.550
and I think in Windows and
Azure they did similar things.
00:01:51.550 --> 00:01:53.440
It's something I've done internally,
so
00:01:53.440 --> 00:01:56.180
really my mantra is,
if you have a question ask it.
00:01:56.180 --> 00:01:57.090
I will have an answer.
00:01:57.090 --> 00:01:58.700
I'll absolutely answer anything.
00:01:58.700 --> 00:02:01.810
You might not like my answer,
but I will answer it and
00:02:01.810 --> 00:02:05.970
I'll try to answer it in a way that
gives context to what we're doing,
00:02:05.970 --> 00:02:08.450
give context to what you may
have missed across the week or
00:02:08.450 --> 00:02:10.010
where we're going.
00:02:10.010 --> 00:02:12.010
So hopefully you'll get
a lot out of this session.
00:02:12.010 --> 00:02:15.150
If anything, just to make sure you
get that last question before you
00:02:15.150 --> 00:02:17.590
leave to wherever
you're going back to.
00:02:17.590 --> 00:02:21.980
I feel like at the end of Ignite,
it's that end where Ferris Bueller
00:02:21.980 --> 00:02:25.360
walks out in his robe and he kinda
says, what are you still doing here?
00:02:25.360 --> 00:02:26.988
So I ask you,
what are you still doing here?
00:02:26.988 --> 00:02:29.181
[LAUGH] But then, of course,
I say thank you for
00:02:29.181 --> 00:02:31.150
coming to the last session.
00:02:31.150 --> 00:02:33.170
And, oh, there goes the timer.
00:02:33.170 --> 00:02:36.010
And then, throughout,
I've got a couple of give-aways.
00:02:36.010 --> 00:02:38.230
Some might be a little small sized.
00:02:38.230 --> 00:02:39.530
Some of these shirts
are a little bit small.
00:02:39.530 --> 00:02:42.120
I've got a special one I won't
tell you too much about.
00:02:42.120 --> 00:02:46.424
It may look a little plain but
it's got something of significance,
00:02:46.424 --> 00:02:50.422
and then I've got a little friend
that can wave his own paw, and
00:02:50.422 --> 00:02:53.007
then a couple of fun
things I'll get to.
00:02:53.007 --> 00:02:55.062
It's more oriented around,
certainly if you have a question,
00:02:55.062 --> 00:02:56.250
I don't have that much to give away.
00:02:56.250 --> 00:02:58.880
Hopefully there's a lot of questions
more than I can give away.
00:02:58.880 --> 00:03:02.110
But the special ones, hopefully
you'll see how we narrow it down to
00:03:02.110 --> 00:03:03.920
hopefully get to the right person.
00:03:03.920 --> 00:03:06.770
One other note just to call
out sort of the how we're
00:03:06.770 --> 00:03:07.600
doing the presentation.
00:03:07.600 --> 00:03:08.810
Hopefully you're here
in the right place.
00:03:08.810 --> 00:03:12.250
This is SharePoint Unplugged and
my name is Mark Kashman,
00:03:12.250 --> 00:03:14.710
senior product manager
on the SharePoint team.
00:03:14.710 --> 00:03:17.680
I've been doing SharePoint stuff for
the last seven years.
00:03:17.680 --> 00:03:20.761
I started building a media and
entertainment solution on top of
00:03:20.761 --> 00:03:23.679
SharePoint 2007, and
we brought that into 2010.
00:03:23.679 --> 00:03:26.956
And then I joined the team to
focus on SharePoint Online and,
00:03:26.956 --> 00:03:29.260
most recently, NextGen Portals.
00:03:29.260 --> 00:03:33.235
A lot of what we're doing
around SharePoint 2016 that
00:03:33.235 --> 00:03:36.164
isn't Bill Baer,
I get everything else.
00:03:36.164 --> 00:03:38.395
And this whole presentation
is being done in Sway, so
00:03:38.395 --> 00:03:40.390
it's a little bit of a new
public thing for me.
00:03:40.390 --> 00:03:43.610
I've done it internally one time and
it seemed to go okay.
00:03:43.610 --> 00:03:45.750
And it's something you can actually
follow along with right now.
00:03:45.750 --> 00:03:50.280
I've got a short URL here,
the aka.ms/SharePointUNPLUGGED.
00:03:50.280 --> 00:03:53.710
You don't have to capitalize but
I just kept consistent visually.
00:03:53.710 --> 00:03:56.200
But if you hit that on your
mobile phone, whatever device,
00:03:56.200 --> 00:04:00.100
operating system, browser,
it's meant to really be when you see
00:04:00.100 --> 00:04:02.810
the format that I've put together,
it's really just a oh,
00:04:02.810 --> 00:04:05.970
okay, yeah, maybe I do have
a question on that or that or that.
00:04:05.970 --> 00:04:08.990
And you'll see I've kind of got
main sections, lots of bullets and
00:04:08.990 --> 00:04:11.400
then links to lots of other things.
00:04:11.400 --> 00:04:13.190
Some I'll reference and
cover in depth and
00:04:13.190 --> 00:04:17.330
some that I will really just
have as a reference point.
00:04:17.330 --> 00:04:19.600
But of course, everything
is starting to fall online.
00:04:19.600 --> 00:04:21.970
So if there's something that
I do refer to or link to,
00:04:21.970 --> 00:04:25.980
most likely is to the channel nine
recording of that session, and
00:04:25.980 --> 00:04:29.230
I'll certainly probably add more
even after the session because
00:04:29.230 --> 00:04:31.000
not everything is online.
00:04:31.000 --> 00:04:33.250
And some of the links are active but
the video's not there yet.
00:04:34.400 --> 00:04:37.920
So if you go to the first link
where it says related content here,
00:04:37.920 --> 00:04:40.420
that's literally everything that
was tagged with SharePoint.
00:04:40.420 --> 00:04:44.440
And it's over 150 sessions, hands-on
labs, those kinds of things, so
00:04:44.440 --> 00:04:47.220
you can refer back to that and the
way that they built the conference
00:04:47.220 --> 00:04:49.380
is you can do a lot
after the conference.
00:04:49.380 --> 00:04:52.040
And then the one where
here on channel nine,
00:04:52.040 --> 00:04:56.860
that specifically just a filtered
URL on the keyword SharePoint
00:04:57.920 --> 00:05:00.690
for every video that's
been posted there.
00:05:00.690 --> 00:05:04.280
So if we travel down on the Sway
just a little bit more,
00:05:04.280 --> 00:05:06.500
I don't know exactly how
your week started, but
00:05:06.500 --> 00:05:08.340
this is just a little bit
on how my week started.
00:05:08.340 --> 00:05:10.050
I got here Saturday.
00:05:10.050 --> 00:05:12.960
Lots of people got here on
Sunday for the pre-days.
00:05:12.960 --> 00:05:17.160
We had two pre-days where we covered
hybrid and end-to-end OneDrive for
00:05:17.160 --> 00:05:17.950
Business setup.
00:05:17.950 --> 00:05:20.770
We had a lot of great speakers,
a lot of new material.
00:05:20.770 --> 00:05:23.450
Even though it was sort
of a deep dive training,
00:05:23.450 --> 00:05:26.070
there were also some announcements
that came out of those pre-days.
00:05:26.070 --> 00:05:29.280
But this is just sort of how I spent
my first day getting to know Chicago
00:05:29.280 --> 00:05:32.030
and hopefully everybody now
knows Chicago very well.
00:05:32.030 --> 00:05:35.100
This in particular was a really good
Guinness at a really good Irish Bar
00:05:36.170 --> 00:05:38.260
and that burger made it harder
to walk back to my hotel.
00:05:40.290 --> 00:05:44.210
So if we look at
SharePoint Server 2016,
00:05:44.210 --> 00:05:46.770
obviously that's a big thing that
we've been talking about here.
00:05:46.770 --> 00:05:48.840
Some people have been giving
us feedback we didn't talk
00:05:48.840 --> 00:05:50.070
enough about it.
00:05:50.070 --> 00:05:52.740
But to be very transparent,
where we are with the release cycle,
00:05:52.740 --> 00:05:54.350
obviously we're not yet at beta.
00:05:54.350 --> 00:05:55.000
That's coming.
00:05:55.000 --> 00:05:56.880
That's the date that you see here,
and
00:05:56.880 --> 00:06:01.090
looking to release in Q2
of 2016 calendar year.
00:06:01.090 --> 00:06:03.210
So the intent for
00:06:03.210 --> 00:06:06.120
us was to start to peel back
a little bit more of the onion.
00:06:06.120 --> 00:06:09.760
We have put a blog post which you'll
see linked at the bottom here,
00:06:09.760 --> 00:06:11.940
SharePoint Server 2016 update.
00:06:11.940 --> 00:06:14.720
So there's a lot of information
leading into MS Ignite, and
00:06:14.720 --> 00:06:17.980
then here we shared
a larger session.
00:06:17.980 --> 00:06:20.660
We had a IT pro session
specifically with Bill Baer, and
00:06:20.660 --> 00:06:22.560
that's that picture
that you see here.
00:06:22.560 --> 00:06:26.870
Where I don't know if anybody went
to it or has been to that room, but
00:06:26.870 --> 00:06:27.860
he filled it pretty well.
00:06:27.860 --> 00:06:30.330
And you know Bill,
he does a great job.
00:06:30.330 --> 00:06:33.980
So a lot of stuff
that came from him.
00:06:33.980 --> 00:06:36.110
Where we focused,
to share the information,
00:06:36.110 --> 00:06:38.920
this next level of information for
SharePoint 2016, was
00:06:38.920 --> 00:06:42.990
really to focus on some of the new
user experiences that are coming.
00:06:42.990 --> 00:06:45.990
Some of the cloud-inspired
infrastructure which is really,
00:06:45.990 --> 00:06:49.850
there's a ton of value and I land on
a couple here just as reference, and
00:06:49.850 --> 00:06:53.030
then around what we're doing around
compliance and reporting, and
00:06:53.030 --> 00:06:54.040
this is all in the box.
00:06:55.210 --> 00:06:57.630
When I get to the next section
you'll see where we're continuing to
00:06:57.630 --> 00:07:01.210
extend what we're doing with
SharePoint and the value in 2016.
00:07:01.210 --> 00:07:03.840
But really this first part
is just to consolidate
00:07:05.200 --> 00:07:06.490
what's actually in 2016.
00:07:06.490 --> 00:07:09.250
The most important thing
about 2016 to understand is
00:07:09.250 --> 00:07:10.820
it's coming from the cloud.
00:07:10.820 --> 00:07:11.960
It used to be the other way around.
00:07:11.960 --> 00:07:16.660
We started BPOS with SharePoint
2007 and we stuck a product and
00:07:16.660 --> 00:07:17.745
tried to make it a service.
00:07:17.745 --> 00:07:20.590
And it was pretty good,
did really well with team sites,
00:07:20.590 --> 00:07:24.140
did well with some other workloads,
certainly from a MySite perspective.
00:07:24.140 --> 00:07:27.214
But some of the other areas,
when you think of some of the deeper
00:07:27.214 --> 00:07:30.578
level of customization, deeper
search like FAST and other things,
00:07:30.578 --> 00:07:34.245
and on through the years, it really
has been, now let's put in 2010.
00:07:34.245 --> 00:07:36.140
Let's upgrade it to 2013.
00:07:36.140 --> 00:07:41.250
What really we have in the cloud
right now is SharePoint 2016++, and
00:07:41.250 --> 00:07:44.790
what we're gonna cut for on premises
will be a lot of that value.
00:07:44.790 --> 00:07:47.700
Ton of value for IT,
good value for end users.
00:07:47.700 --> 00:07:50.510
I'll walk through some of that and
certainly from a lot of what
00:07:50.510 --> 00:07:54.000
the development team has been doing,
everything applies.
00:07:54.000 --> 00:07:56.970
But not to discount that you
can still do full trust code,
00:07:56.970 --> 00:07:59.000
if you choose to move
to the new app model.
00:07:59.000 --> 00:08:01.970
And a lot of what the team
shared at Build and this week,
00:08:01.970 --> 00:08:05.880
there's a lot of new patterns around
add-ins, and certainly all of
00:08:05.880 --> 00:08:09.680
the new Office 365 API endpoints,
I'll talk about that a little more.
00:08:09.680 --> 00:08:13.491
But SharePoint 2016 really benefits
from everything that we've been
00:08:13.491 --> 00:08:16.211
doing in the cloud really
since November 2012 and
00:08:16.211 --> 00:08:18.403
that's when we cut SharePoint 2013.
00:08:18.403 --> 00:08:22.560
I mean, not cut it, but cut a build
and made it available as a version.
00:08:22.560 --> 00:08:25.290
So everything from there on, I'm
watching my words because Mark in
00:08:25.290 --> 00:08:28.558
the front here wants to make sure
that I don't ever infer that
00:08:28.558 --> 00:08:32.740
SharePoint is [FOREIGN],
or dead or anything.
00:08:32.740 --> 00:08:36.240
Because if you haven't noticed,
we have a new version coming.
00:08:36.240 --> 00:08:38.290
We have a whole team
behind building and
00:08:38.290 --> 00:08:41.340
making that new version awesome, and
some of the stuff we do in the cloud
00:08:41.340 --> 00:08:43.850
is just gonna land there first and
then come down.
00:08:43.850 --> 00:08:45.480
And if you don't believe me,
00:08:45.480 --> 00:08:47.730
you should really see all
the sessions we've had.
00:08:47.730 --> 00:08:50.010
And if you've talked with
all of the engineers,
00:08:50.010 --> 00:08:52.570
they're pretty jazzed about
what's landing on-premises.
00:08:52.570 --> 00:08:55.470
There's a whole team thinking on
how they take that forward for
00:08:55.470 --> 00:08:58.160
service packs and
other things into the future.
00:08:58.160 --> 00:09:01.730
Our two biggest sessions were
the foundational session with
00:09:01.730 --> 00:09:03.100
Seth and Bill.
00:09:03.100 --> 00:09:06.510
And then the what's new for IT pros
where Bill covered a ton of stuff.
00:09:06.510 --> 00:09:09.170
Some of the things that he covered
from an IT pro perspective was
00:09:09.170 --> 00:09:12.720
the new MinRole so there are fewer
roles that you need to define.
00:09:12.720 --> 00:09:15.550
Making that hopefully easier
to manage, lesser footprint.
00:09:15.550 --> 00:09:17.945
From a MinDB perspective,
00:09:17.945 --> 00:09:21.230
anytime you can have fewer content
databases that's a good thing.
00:09:21.230 --> 00:09:24.100
Usually it means fewer servers,
easier to manage.
00:09:24.100 --> 00:09:26.650
And then specifically around
zero-downtime patching,
00:09:26.650 --> 00:09:30.040
it's something we've been doing
in the cloud for a long time.
00:09:30.040 --> 00:09:32.760
Quick raise of hands, who's been
here since the the BPOS days,
00:09:32.760 --> 00:09:34.060
as far as the cloud is concerned?
00:09:35.300 --> 00:09:37.100
Who remembers the amount
of read-only or
00:09:37.100 --> 00:09:38.730
downtime we took during an upgrade?
00:09:40.280 --> 00:09:42.680
So yeah, usually groans and moans.
00:09:42.680 --> 00:09:45.480
Who remembers in the last six
months where we took a read-only?
00:09:45.480 --> 00:09:49.050
I don't mean that we didn't have
bumps and bruises here and there.
00:09:49.050 --> 00:09:52.095
We certainly recover that from
a service SLA perspective.
00:09:52.095 --> 00:09:56.514
But the last time that we had
to take a 30-minute planned
00:09:56.514 --> 00:09:59.500
downtime for patching, for upgrade.
00:09:59.500 --> 00:10:01.218
Hopefully no hands go up.
00:10:01.218 --> 00:10:02.401
All of that benefit.
00:10:02.401 --> 00:10:05.513
Course benefits SharePoint
online in Office 365.
00:10:05.513 --> 00:10:09.260
But it's coming to the on premises
version of SharePoint as well.
00:10:09.260 --> 00:10:12.280
Which for an IT pro is like yeah.
00:10:12.280 --> 00:10:13.760
Go to the business unit and
say you know what,
00:10:13.760 --> 00:10:17.330
I'm going to disturb you a lot less
when I need to do a security fix or
00:10:17.330 --> 00:10:18.838
a sequel thing.
00:10:18.838 --> 00:10:21.200
But certainly they've made
a lot of innovation there and
00:10:21.200 --> 00:10:24.680
it's because we just can't
keep doing that in the cloud.
00:10:24.680 --> 00:10:26.460
So I encourage you to look
at some of these materials.
00:10:26.460 --> 00:10:30.290
Of course, there's a ton more
coming as we get near to Beta.
00:10:30.290 --> 00:10:34.590
Our biggest goal is that we will
have documentation at Beta time.
00:10:34.590 --> 00:10:37.420
In 2007, it came six months later.
00:10:37.420 --> 00:10:40.890
In 2010, it came right at release.
00:10:40.890 --> 00:10:43.090
In 2013, it came with Beta.
00:10:43.090 --> 00:10:46.230
And best feedback we've gotten
is when it comes with Beta.
00:10:46.230 --> 00:10:48.980
And certainly in some of our early
tap engagements there will be enough
00:10:48.980 --> 00:10:50.420
information to get people started,
but
00:10:50.420 --> 00:10:52.987
the real documentation will
land at beta timeframe.
00:10:54.170 --> 00:10:58.230
So if that sets the stage, let's
talk a little bit about hybrid, and
00:10:58.230 --> 00:11:00.580
again, I just want to reiterate this
is not going to be me talking for
00:11:00.580 --> 00:11:01.630
the whole 75 minutes.
00:11:01.630 --> 00:11:04.680
It might feel like it for the first
10 or 15, but I'm really just trying
00:11:04.680 --> 00:11:07.960
to seed you with what happened this
week, what have we talked about, and
00:11:07.960 --> 00:11:10.500
certainly maybe you
came with a question.
00:11:10.500 --> 00:11:13.460
But if you didn't this will
seed you with some ideas of
00:11:13.460 --> 00:11:16.930
what can I hammer Mark, I mean,
what can I ask Mark about.
00:11:18.220 --> 00:11:20.650
So Hybrid, I think we've been
doing a lot of great work.
00:11:20.650 --> 00:11:25.330
The rumblings I heard is we're not
doing enough, but at the same time,
00:11:25.330 --> 00:11:28.730
my personal opinion is we
are doing more than we ever have.
00:11:28.730 --> 00:11:32.020
And some of it is improving, even
stuff that we've had for a while.
00:11:32.020 --> 00:11:34.735
A lot of it is making it so
that when 2016 lands,
00:11:34.735 --> 00:11:38.870
it'll be the most Hybrid potential,
if you go that direction.
00:11:38.870 --> 00:11:40.300
But we started off
with the pre day for
00:11:40.300 --> 00:11:42.270
Hybrid, that's
the picture you see here.
00:11:42.270 --> 00:11:47.470
And we had, I think, seven or eight
presenters, across multiple modules.
00:11:47.470 --> 00:11:49.980
And they were all really great new
information that kicked off with
00:11:49.980 --> 00:11:54.332
one of our engineers talking about
the overview future of Hybrid.
00:11:54.332 --> 00:11:56.730
There are a lot of great
nuggets to find there.
00:11:56.730 --> 00:12:00.750
At the helm, was Bill Baer again,
and he was driving
00:12:00.750 --> 00:12:03.980
through with a lot of our deep
sneeze going through how to do this,
00:12:03.980 --> 00:12:07.190
how to do that, and certainly all
of that material will be available.
00:12:07.190 --> 00:12:10.720
But we did talk about Hybrid Search.
00:12:10.720 --> 00:12:14.090
It started out Hybrid Search
was a federated query.
00:12:14.090 --> 00:12:18.460
Now it's a singular index with
a specific component that ships in
00:12:18.460 --> 00:12:22.390
2016 that's called, new name for me,
they used to have a different name.
00:12:22.390 --> 00:12:24.000
Cloud Search Service Application.
00:12:25.040 --> 00:12:26.430
So that's gonna be pretty exciting.
00:12:26.430 --> 00:12:28.580
Where your Index lives is the Cloud.
00:12:28.580 --> 00:12:30.790
But effectively, you can
search from across OnPrem and
00:12:30.790 --> 00:12:34.700
online and have that singular index
that gives you that relevancy
00:12:34.700 --> 00:12:37.210
that's been lacking
in Hybrid Search.
00:12:37.210 --> 00:12:39.940
Still, there's configuration and
setup to accomplish it, but
00:12:39.940 --> 00:12:41.380
that's gonna get easier.
00:12:41.380 --> 00:12:42.770
And certainly, out of the box,
00:12:42.770 --> 00:12:45.230
a lot easier to connect with
your cloud environment.
00:12:45.230 --> 00:12:48.510
And it could also be
applicable to a VM.
00:12:48.510 --> 00:12:50.880
Business connectivity
services is getting a lot of
00:12:50.880 --> 00:12:52.020
investments as well.
00:12:52.020 --> 00:12:53.820
It's something that
we're continuing,
00:12:53.820 --> 00:12:55.660
it's something that's
supported in online and
00:12:55.660 --> 00:12:59.580
on premises and in 2016, and then
certainly it's already in the cloud.
00:12:59.580 --> 00:13:01.260
It will just be a lot easier and
00:13:01.260 --> 00:13:03.990
a lot more reliable to
connect to back end systems.
00:13:05.490 --> 00:13:09.700
One of the things that we
shift in SharePoint 2013 SP1
00:13:09.700 --> 00:13:12.730
was the ability to, if you're
on premises in the new look and
00:13:12.730 --> 00:13:16.640
feel as a common top navigation,
like there is in Office 365,
00:13:16.640 --> 00:13:20.190
and a lot of those elements can now
be programmed to go to Office 365.
00:13:20.190 --> 00:13:25.170
The first two that we introduced was
OneDrive and Yammer, and in 2016 we
00:13:25.170 --> 00:13:29.930
are bringing that ability to connect
to Delve and Office 365 Video.
00:13:29.930 --> 00:13:31.580
And that's relatively
lightweight hybrid.
00:13:31.580 --> 00:13:34.800
We're not trying to fool anybody and
my job today is to make sure,
00:13:34.800 --> 00:13:37.040
absolutely clear,
that doesn't mean that Delve and
00:13:37.040 --> 00:13:40.670
the Office Graph are coming
inside of anything on-premises.
00:13:40.670 --> 00:13:44.140
They will live in the cloud same
as Yammer, same as OneDrive for
00:13:44.140 --> 00:13:45.030
Business.
00:13:45.030 --> 00:13:49.190
But managing who you are through the
on-premises site you logged into,
00:13:49.190 --> 00:13:52.760
on through to whatever service of
those four you may wire up and
00:13:52.760 --> 00:13:54.400
connect from a hybrid perspective.
00:13:54.400 --> 00:13:57.620
You land as who you are and it's
a nice user experience and a lot of
00:13:57.620 --> 00:14:00.600
that authentication handling
is really what that is about.
00:14:00.600 --> 00:14:05.380
We also announced that we will
be back porting the support for
00:14:05.380 --> 00:14:09.470
Delve as a Hybrid redirect
in SharePoint server 2013.
00:14:09.470 --> 00:14:12.820
I don't wanna claim it's
gonna be Service Pack 2, but
00:14:12.820 --> 00:14:13.960
I believe that's the plan.
00:14:13.960 --> 00:14:16.210
So, the next service pack or
the next cumulative update,
00:14:16.210 --> 00:14:18.440
you will get that capability for
2013,
00:14:18.440 --> 00:14:22.700
so it's not a requirement
to upgrade to 2016.
00:14:22.700 --> 00:14:27.615
So a couple of sessions that
were pretty important here.
00:14:27.615 --> 00:14:30.683
First time we talked about this
new Hybrid Search component,
00:14:30.683 --> 00:14:34.105
if you wanted to review that, they
did a really nice job showcasing it
00:14:34.105 --> 00:14:36.410
and demoing it,
that was breakout 3134.
00:14:36.410 --> 00:14:39.765
And then, all of the innovation
they've been putting into BCS
00:14:39.765 --> 00:14:42.750
certainly lands in 2016 and
the cloud is 4113.
00:14:42.750 --> 00:14:47.110
If you're interested in running the
labs, I think I have this right, but
00:14:47.110 --> 00:14:50.460
for the next 30 days, you can
go into a virtual environment,
00:14:50.460 --> 00:14:54.190
load up the labs, keep trying them,
so keep hammering away at those.
00:14:54.190 --> 00:14:58.070
There were about six or seven new
hybrid hands on labs that were built
00:14:58.070 --> 00:15:03.710
specifically for Ignite, so
definitely make sure you get those.
00:15:03.710 --> 00:15:06.300
So next section was Nextgen portals.
00:15:06.300 --> 00:15:09.600
This is actually something I'm
pretty close to working with Adam,
00:15:09.600 --> 00:15:12.820
who you see pictured here,
and his team, and
00:15:12.820 --> 00:15:15.470
really Adam is focused
on Nextgen portals.
00:15:15.470 --> 00:15:18.230
He's also going to be focusing
on what we're doing around ECM
00:15:18.230 --> 00:15:19.460
going forward.
00:15:19.460 --> 00:15:23.610
And he contributes also to some of
the SharePoint elements that you'll
00:15:23.610 --> 00:15:25.420
see in Office 365 Groups.
00:15:25.420 --> 00:15:28.400
So we had a pretty good turnout, and
shared a lot of information about
00:15:28.400 --> 00:15:32.650
this new motion, which is really
building portals that are ready to
00:15:32.650 --> 00:15:35.920
go, intelligent cuz they're
connected to the Office graph.
00:15:35.920 --> 00:15:38.490
Social because they're
inherently connected to Yammer
00:15:38.490 --> 00:15:40.540
in a more inline experience.
00:15:40.540 --> 00:15:42.720
They're mobile because we're
shipping mobile apps and
00:15:42.720 --> 00:15:44.570
focused on responsive design.
00:15:44.570 --> 00:15:47.230
And then that ready to go motion is,
these are things that we've been
00:15:47.230 --> 00:15:49.970
watching people do for
the last 10 years,
00:15:49.970 --> 00:15:52.520
that typically take six to
eight months of development,
00:15:52.520 --> 00:15:56.050
lots of budget and time and
then change management overtime.
00:15:56.050 --> 00:15:58.230
It doesn't just stop,
though, at the ready to go.
00:15:58.230 --> 00:16:00.470
We also are starting to talk
about what we're gonna do for
00:16:00.470 --> 00:16:01.580
custom going forward.
00:16:01.580 --> 00:16:05.390
And that could be, as is today,
the publishing infrastructure or
00:16:05.390 --> 00:16:09.660
going forward custom portals that
you might build in a more Azure way,
00:16:09.660 --> 00:16:14.740
but connected through the APIs,
maybe a CMS Service that we put in.
00:16:14.740 --> 00:16:18.240
So it helps you build faster and
then that big focus on mobile.
00:16:18.240 --> 00:16:20.640
Hopefully helping you get quicker
00:16:20.640 --> 00:16:24.600
responsive pages to market rather
than spending your time doing that.
00:16:24.600 --> 00:16:28.130
So, we had a lot of sessions and
got a lot of good feedback.
00:16:28.130 --> 00:16:31.930
The team here is very open because
we've shipped one of them.
00:16:31.930 --> 00:16:35.140
The other, we're about halfway done
shipping and then the two that we
00:16:35.140 --> 00:16:38.920
want to do next, are coming over
the next year, year and a half.
00:16:38.920 --> 00:16:41.490
And we laid the foundation of
what those building blocks are,
00:16:41.490 --> 00:16:42.620
got a good reception.
00:16:42.620 --> 00:16:45.200
Hopefully making the right
connections of what they were and
00:16:45.200 --> 00:16:48.500
not trying to make it confusing.
00:16:48.500 --> 00:16:51.450
One of my favorite things that I saw
through the week was this t-shirt.
00:16:51.450 --> 00:16:54.520
I don't know if you can see it here
and one thing with Sway is you
00:16:54.520 --> 00:16:57.380
can't zoom in too easily, so
I'm not gonna try to break anything.
00:16:57.380 --> 00:17:00.960
But it basically says Office
365 Next Gen Portals Rock.
00:17:00.960 --> 00:17:04.230
Not planted by Microsoft,
made it before he came here.
00:17:04.230 --> 00:17:05.840
That was kind of fun to see.
00:17:05.840 --> 00:17:09.350
And then this was the session that
we had with the Office 365 video,
00:17:09.350 --> 00:17:12.250
where we were working with the Azure
media services team to really
00:17:12.250 --> 00:17:14.580
kind of go to that
next level of detail.
00:17:14.580 --> 00:17:19.270
But the two other things that we
talked about besides the general
00:17:19.270 --> 00:17:23.310
overview, which is this session
2173 video that I just mentioned.
00:17:23.310 --> 00:17:25.910
We talked about a new knowledge
management portal and
00:17:25.910 --> 00:17:28.280
the building blocks and
methods of how we'll get there.
00:17:28.280 --> 00:17:31.140
And the team behind that really
starts in a very methodical way,
00:17:31.140 --> 00:17:33.800
what do they need,
what are they used to, and
00:17:33.800 --> 00:17:37.750
what can we do that's maybe a little
different to add to that experience?
00:17:37.750 --> 00:17:40.590
And then we've been working pretty
closely with the Delve team,
00:17:40.590 --> 00:17:43.740
specifically on the new profile
experience in Office 365 and
00:17:43.740 --> 00:17:46.850
this is meant to really focus
on the types of portals
00:17:46.850 --> 00:17:49.330
people would build
around people expertise.
00:17:49.330 --> 00:17:53.590
Certainly a feature of search and
really bringing that into when you
00:17:53.590 --> 00:17:55.810
find somebody,
what is it you discover about them?
00:17:55.810 --> 00:17:57.820
And it doesn't mean always
go to their profile.
00:17:57.820 --> 00:18:00.490
And it doesn't mean that
the person always needed to
00:18:00.490 --> 00:18:03.270
fill out a bunch of stuff
that they never do anyway.
00:18:03.270 --> 00:18:05.310
A lot of this is driven
by machine learning and
00:18:05.310 --> 00:18:07.600
of course intelligent design.
00:18:07.600 --> 00:18:09.380
And then this is a really fun
session if you missed it.
00:18:09.380 --> 00:18:11.710
These are two of our engineers.
00:18:11.710 --> 00:18:13.990
One of them who reports
directly to Adam.
00:18:13.990 --> 00:18:15.620
They really just dove
under the covers and
00:18:15.620 --> 00:18:18.090
showed you how we're doing all
this stuff with a little teaser at
00:18:18.090 --> 00:18:20.820
the end on what does custom
look like in the future.
00:18:20.820 --> 00:18:22.870
They did a really nice job.
00:18:22.870 --> 00:18:26.130
Two recent blog posts that we put
out for a little further reading,
00:18:26.130 --> 00:18:29.040
the most recent one on video
when we brought into production,
00:18:29.040 --> 00:18:30.480
it's now worldwide.
00:18:30.480 --> 00:18:32.940
We announced that here,
that we're now at 100%.
00:18:32.940 --> 00:18:35.650
And then people experiences that
really kinda show what we're doing
00:18:35.650 --> 00:18:37.370
there and
what we're planning to do next.
00:18:39.000 --> 00:18:41.850
So, next level of things you
might have questions on, or
00:18:41.850 --> 00:18:44.410
heard throughout the week,
was Custom development.
00:18:45.900 --> 00:18:48.012
Quick question and
I'll throw out something,
00:18:48.012 --> 00:18:49.341
the guy pointing, who is he?
00:18:49.341 --> 00:18:50.310
>> Paolo.
>> Paolo, okay.
00:18:50.310 --> 00:18:51.345
>> What size shirt generally?
00:18:51.345 --> 00:18:55.245
>> Pardon?
00:18:55.245 --> 00:18:56.753
>> What size shirt do you wear,
generally?
00:18:56.753 --> 00:19:00.110
>> Medium.
>> All right I'll find one,
00:19:00.110 --> 00:19:02.370
I don't have it.
00:19:02.370 --> 00:19:05.050
>> So Paolo, Paleorisi,
If I get his name right.
00:19:06.650 --> 00:19:07.310
>> Can we see the shirt?
00:19:07.310 --> 00:19:08.005
>> Oh, sorry. Yeah.
00:19:08.005 --> 00:19:09.452
[LAUGH] You don't want this, maybe?
00:19:09.452 --> 00:19:12.961
>> [LAUGH]
>> All right, so
00:19:12.961 --> 00:19:15.930
it's not SharePoint related,
those I'm saving for the other ones.
00:19:15.930 --> 00:19:18.080
But it's the Office
365 network shirt.
00:19:18.080 --> 00:19:20.590
So, I don't wanna disappoint
that this is not all SharePoint.
00:19:20.590 --> 00:19:25.000
But, the team behind that has given
us a lot of great foundational ways
00:19:25.000 --> 00:19:26.820
to connect with the community.
00:19:26.820 --> 00:19:28.020
So I support them heavily.
00:19:28.020 --> 00:19:32.050
And I think they're at about 60,000
users on the public network.
00:19:32.050 --> 00:19:34.550
So, I'm doing a lot of
advertising for them.
00:19:34.550 --> 00:19:37.480
And then, the other things I have
to throw out are these watches.
00:19:37.480 --> 00:19:39.270
And I'll explain it,
and then I'll move on.
00:19:39.270 --> 00:19:41.670
These watches are the dumbest
watch I've ever seen.
00:19:44.230 --> 00:19:45.330
They're so dumb.
00:19:45.330 --> 00:19:46.630
They do nothing.
00:19:46.630 --> 00:19:48.128
There's no checking Twitter on them.
00:19:48.128 --> 00:19:50.664
There's absolutely no following
the Sway that I have here,
00:19:50.664 --> 00:19:51.963
if you follow that Bitly link.
00:19:51.963 --> 00:19:55.540
What it does, though,
is it tells the time.
00:19:55.540 --> 00:19:57.941
>> [LAUGH]
>> Push of a button.
00:19:57.941 --> 00:19:58.742
It tells the time.
00:19:58.742 --> 00:20:00.113
Pretty dumb, huh?
00:20:00.113 --> 00:20:02.493
So I've got four of
those to hand out.
00:20:02.493 --> 00:20:04.160
And those are good for throwing.
00:20:05.240 --> 00:20:06.420
Interaction in the back.
00:20:08.010 --> 00:20:10.540
So obviously,
Paulo was here at the booth.
00:20:10.540 --> 00:20:13.290
He's a really great developer
that works outside of Microsoft.
00:20:13.290 --> 00:20:16.040
The team behind it though,
if you're a developer,
00:20:16.040 --> 00:20:17.400
you can't miss who they are.
00:20:17.400 --> 00:20:20.960
They've been doing really great
work, sharing last week at Build,
00:20:20.960 --> 00:20:22.280
this week at Ignite.
00:20:22.280 --> 00:20:27.160
But, they're also really
reinventing dev.office.com podcast.
00:20:27.160 --> 00:20:29.300
We've got Jeremy Thicke on our side.
00:20:29.300 --> 00:20:32.150
He's great for evangelism,
but he's also super deep.
00:20:32.150 --> 00:20:36.082
He's the right guy.
00:20:36.082 --> 00:20:37.300
And the team that he's on,
he's not on the same team anymore.
00:20:37.300 --> 00:20:39.614
He's on a really good team no
matter who he is reporting to, but
00:20:39.614 --> 00:20:42.540
since I'm guessing a lot of you
have some SharePoint history here.
00:20:42.540 --> 00:20:45.400
He used to report to Arpan Shah
when he first joined.
00:20:45.400 --> 00:20:47.506
And if you know Arpan,
he's great at doing this.
00:20:47.506 --> 00:20:48.390
Hm, and you.
00:20:48.390 --> 00:20:50.531
>> [LAUGH]
>> And
00:20:50.531 --> 00:20:54.750
he put a really nice team together,
and they're working really hard.
00:20:54.750 --> 00:20:58.180
So, a lot of what they focused on,
both at Build and here, and
00:20:58.180 --> 00:20:59.980
there is a blog at the end.
00:20:59.980 --> 00:21:01.880
Scroll one more time,
00:21:01.880 --> 00:21:04.280
that really captures a lot
of this more in-depth.
00:21:04.280 --> 00:21:07.200
And like I said in the beginning,
I am not your deep developer.
00:21:07.200 --> 00:21:11.226
I just like what they do because
sometimes they build nice,
00:21:11.226 --> 00:21:12.620
cool demos for me.
00:21:12.620 --> 00:21:14.330
But, I usually work for them.
00:21:14.330 --> 00:21:17.927
So they're obviously talking about
this consolidation of APIs at
00:21:17.927 --> 00:21:21.920
the Office 365 level, so that it's
more of a singular rest endpoint.
00:21:21.920 --> 00:21:25.400
The new app model certainly
has matured a lot.
00:21:25.400 --> 00:21:27.220
If you reviewed a year or two ago,
00:21:27.220 --> 00:21:31.170
when we started talking about it
with 2013, you might have thought
00:21:31.170 --> 00:21:33.320
whoa, I can't do all of my
full trust code like that.
00:21:33.320 --> 00:21:35.570
That's just gonna fall
short in many ways.
00:21:35.570 --> 00:21:37.250
But, cut to six months later.
00:21:37.250 --> 00:21:39.760
Six months later,
keep going forward.
00:21:39.760 --> 00:21:41.930
More and
more people are starting to think,
00:21:41.930 --> 00:21:45.020
if I can build it in
the new app model, I will.
00:21:45.020 --> 00:21:46.950
If I can't,
maybe I should wait a little bit and
00:21:46.950 --> 00:21:50.792
just do more of a hybrid approach,
or just keep it where it's at.
00:21:50.792 --> 00:21:53.770
And then, we're not trying to
limit there on what's possible.
00:21:53.770 --> 00:21:56.760
In this team with Rob Lefferts,
who's our lead engineer now across,
00:21:56.760 --> 00:22:00.070
not just SharePoint, but Office, I
think it's doing a really great job.
00:22:00.070 --> 00:22:01.050
And we've got, of course,
00:22:01.050 --> 00:22:04.990
ten years of full trust code
innovation to try to leap ahead.
00:22:04.990 --> 00:22:08.990
But again,
full trust code not going away.
00:22:08.990 --> 00:22:12.850
From an API specific perspective,
we started to show and
00:22:12.850 --> 00:22:17.590
talk about the Office Graph APIs,
Groups APIs, and Video.
00:22:17.590 --> 00:22:19.130
I believe all of
them are in preview,
00:22:19.130 --> 00:22:20.270
I don't think anything's
been released.
00:22:20.270 --> 00:22:22.500
I'm not Quite sure where
they're at with groups.
00:22:22.500 --> 00:22:25.580
I know some of them are gonna
go a little faster than others.
00:22:25.580 --> 00:22:28.340
But there's all now,
new information on MSDN.
00:22:28.340 --> 00:22:29.867
A lot of what you saw here,
00:22:29.867 --> 00:22:34.104
especially if you went to the Office
Graph battle, was pretty clever and
00:22:34.104 --> 00:22:38.870
pretty interesting solutions people
are building with those now.
00:22:38.870 --> 00:22:41.420
APIs that we've been building
off are made public.
00:22:41.420 --> 00:22:43.250
And there also is a really
great session about, or
00:22:43.250 --> 00:22:45.580
there is a couple of sessions
one that I linked here,
00:22:45.580 --> 00:22:48.570
around how do you build
full trust code today
00:22:48.570 --> 00:22:50.870
with the intent that it may
sometime go to the cloud.
00:22:50.870 --> 00:22:54.000
So it really revolves around
you're still doing full trust type
00:22:54.000 --> 00:22:55.760
solutions on premises.
00:22:55.760 --> 00:22:59.310
But, the footprint of the full trust
component might be a lot smaller,
00:22:59.310 --> 00:23:00.860
and you're really breaking it apart.
00:23:00.860 --> 00:23:04.200
And we had Bob German, and I believe
Chris O'Brien he was paired with,
00:23:04.200 --> 00:23:07.260
that had a really nice session that
grounds it in the reality of we know
00:23:07.260 --> 00:23:08.960
not everybody is in the Cloud.
00:23:08.960 --> 00:23:10.840
And may never be or
may not be for a while.
00:23:10.840 --> 00:23:13.875
Whatever the case,
there's new patterns that are very
00:23:13.875 --> 00:23:16.390
Cloud-oriented patterns that
you can benefit for on-prem.
00:23:16.390 --> 00:23:20.140
And if you do move to that
solution online or into Azure,
00:23:20.140 --> 00:23:23.000
then you will have less of
a lift to get it there.
00:23:24.130 --> 00:23:25.990
And then certainly, there's a team.
00:23:25.990 --> 00:23:28.610
The one that I work closely
with is a guy named Vessa.
00:23:28.610 --> 00:23:31.930
I won't try to pronounce his
last name in front of you.
00:23:31.930 --> 00:23:33.950
But if you know Vessa,
he's a great resource.
00:23:33.950 --> 00:23:35.630
He's very community oriented.
00:23:35.630 --> 00:23:38.660
And he really was here at Ignite
to share everything that he's been
00:23:38.660 --> 00:23:41.470
doing with the team,
like Steve Walker and a lot of folks
00:23:41.470 --> 00:23:45.030
from the MVP community,
to really push the PnP out.
00:23:45.030 --> 00:23:46.650
So there's a ton of sessions.
00:23:46.650 --> 00:23:48.760
Again, a couple that I
just linked to here.
00:23:48.760 --> 00:23:51.736
The biggest one that we had was
the foundational session with
00:23:51.736 --> 00:23:54.960
Rob Leffertz and Jeremy around
how Office development matters.
00:23:54.960 --> 00:23:58.503
And looking at the full
trust conversion and
00:23:58.503 --> 00:24:03.111
looking at how to take advantage
of the Office app model.
00:24:03.111 --> 00:24:04.070
And then, we had one on branding.
We actually had a couple sessions on branding.
00:24:04.070 --> 00:24:05.940
This one was more for developers.
00:24:05.940 --> 00:24:08.080
The other was more around
performance tuning for
00:24:08.080 --> 00:24:09.500
IT and design.
00:24:10.740 --> 00:24:14.450
And then, just a grounding around
how we can do this life-cycle
00:24:14.450 --> 00:24:19.410
management much better, and
not have the Cloud move be so scary.
00:24:19.410 --> 00:24:21.630
They did come out with a blog
post shortly after Build.
00:24:21.630 --> 00:24:23.470
I took the whack Build off,
00:24:23.470 --> 00:24:26.170
because its relevant whether
you're at Build or Ignite.
00:24:26.170 --> 00:24:28.590
And it gives a lot of nice visuals
and a lot of nice read through.
00:24:28.590 --> 00:24:30.795
And then of course, if you
haven't looked at this recently,
00:24:30.795 --> 00:24:34.800
dev.office.com is really
got this guy behind it now.
00:24:34.800 --> 00:24:37.640
And hopefully, that's not
being stretched like I see it.
00:24:37.640 --> 00:24:38.940
I think he was being
stretched this week.
00:24:40.210 --> 00:24:40.920
Anybody know Jeremy?
00:24:42.260 --> 00:24:45.000
All right, so if you don't,
great resource.
00:24:45.000 --> 00:24:47.150
If you are a Twitterer,
00:24:47.150 --> 00:24:49.750
he's a good one to follow from
a developers perspective.
00:24:49.750 --> 00:24:50.286
And then, who's this guy?
00:24:52.506 --> 00:24:54.420
[LAUGH] That was just
me trying to learn,
00:24:54.420 --> 00:24:57.679
what do I need to learn about dev
just so I can be a little dangerous?
00:24:59.050 --> 00:25:04.040
So then last section here, and then
really to kind of go into your Q&A.
00:25:04.040 --> 00:25:08.400
And hopefully, I haven't gone too
much over than what I thought,
00:25:08.400 --> 00:25:11.840
is there's a lot that we're
doing with SharePoint in online.
00:25:11.840 --> 00:25:13.830
And it's not just SharePoint online.
00:25:13.830 --> 00:25:16.790
And we're really in this
middle point where we're
00:25:16.790 --> 00:25:19.770
thinking maybe we don't brand
everything SharePoint online.
00:25:19.770 --> 00:25:21.740
Maybe it just is
powered by SharePoint,
00:25:21.740 --> 00:25:23.420
maybe it's a service
here's the shirt.
00:25:23.420 --> 00:25:24.580
Oh no, it's that's not the shirt.
00:25:24.580 --> 00:25:26.330
I showed you a shirt earlier.
00:25:26.330 --> 00:25:29.750
This is Martin everybody,
who had the NextGen portals rocks.
00:25:29.750 --> 00:25:33.780
But, it's this concept of
powered by SharePoint.
00:25:33.780 --> 00:25:35.140
You all have been doing it for
years.
00:25:35.140 --> 00:25:36.864
You're building your solutions
on top of SharePoint.
00:25:36.864 --> 00:25:39.686
Guaranteed that when your end
user hit your business solution,
00:25:39.686 --> 00:25:42.939
you didn't front and center and say
hey, you're in a SharePoint thing.
00:25:42.939 --> 00:25:45.640
And we're taking that tact,
and other teams are as well.
00:25:45.640 --> 00:25:49.680
One of the most significant types
of moves wasn't a SharePoint one.
00:25:49.680 --> 00:25:53.150
But if you go to the App Launcher in
Office 365, and you click it out and
00:25:53.150 --> 00:25:54.500
you see all the services.
00:25:54.500 --> 00:25:55.850
There used to be one
that said Outlook
00:25:55.850 --> 00:25:57.850
with the common Outlook logo.
00:25:57.850 --> 00:25:58.560
What is it called now?
00:25:59.820 --> 00:26:04.700
Mail, and talked to the Outlook Team
and tried to figure how many hours
00:26:04.700 --> 00:26:06.655
they went over that one,
just from a branding perspective.
00:26:06.655 --> 00:26:10.170
[LAUGH] But,
the intent was it's just your mail,
00:26:10.170 --> 00:26:11.120
it's just your calendar.
00:26:11.120 --> 00:26:11.970
It's just this.
00:26:11.970 --> 00:26:14.250
There's a lot of new
brands certainly, and
00:26:14.250 --> 00:26:17.370
we think there's room for
brand and sometimes room for
00:26:17.370 --> 00:26:19.710
the brand to disappear
into the background.
00:26:19.710 --> 00:26:22.190
But, it's a fully functioning
SharePoint 2016+++,
00:26:22.190 --> 00:26:25.530
that's really powering
a lot of new things.
00:26:25.530 --> 00:26:28.640
So I thought we could
sort of end on,
00:26:28.640 --> 00:26:31.395
not only seeing our booth
before you guys messed it up.
00:26:31.395 --> 00:26:33.636
>> [LAUGH]
>> So clean, so clean, so
00:26:33.636 --> 00:26:37.365
many devices without
thumb prints on them.
00:26:37.365 --> 00:26:38.661
>> [LAUGH]
>> But here,
00:26:38.661 --> 00:26:44.260
powered by SharePoint is my list,
obviously SharePoint Online.
00:26:44.260 --> 00:26:46.010
Some of these weren't direct
announcements that we had
00:26:46.010 --> 00:26:46.530
in sessions.
00:26:46.530 --> 00:26:49.494
That's one thing that I struggled
with a little bit when we did
00:26:49.494 --> 00:26:50.178
the lineup for
00:26:50.178 --> 00:26:53.030
what SharePoint sessions with
the allocation that we had.
00:26:53.030 --> 00:26:55.710
We were thinking of having
a SharePoint Online session.
00:26:55.710 --> 00:26:58.380
At the end of the day, it didn't
seem to make sense because we had so
00:26:58.380 --> 00:27:01.450
many sessions that had so many
components of SharePoint Online.
00:27:01.450 --> 00:27:04.320
And it's no longer this one
singular thing it's, again,
00:27:04.320 --> 00:27:06.710
this thing that's powering
a lot of experiences.
00:27:06.710 --> 00:27:09.184
But, some of the specific things
that are soon to roll out, or
00:27:09.184 --> 00:27:11.087
certainly we would have
been talking about it,
00:27:11.087 --> 00:27:12.860
would have there been
a SharePoint Online.
00:27:12.860 --> 00:27:17.740
We're moving from a 2GB
file limit up to 10GB.
00:27:17.740 --> 00:27:22.715
We also have an initial amount
of storage that we're giving to
00:27:22.715 --> 00:27:26.860
our Office 365 customers,
small and large.
00:27:26.860 --> 00:27:30.369
Education, government, anything in
a multi-tenant space is gonna get
00:27:30.369 --> 00:27:32.720
a terabyte instead
of a 10 GB default.
00:27:32.720 --> 00:27:36.360
Still the calculation of 500 MB or
what we're trying
00:27:36.360 --> 00:27:39.530
to re-frame around,
you get a half a GB per person.
00:27:39.530 --> 00:27:41.036
Still, lots of storage,
00:27:41.036 --> 00:27:44.937
but for our customers that weren't
quite as large as a 5,000,
00:27:44.937 --> 00:27:49.470
10,000 seat or above, at least they
get a little bit more to start with.
00:27:49.470 --> 00:27:52.561
Especially when we start to
introduce things like video that
00:27:52.561 --> 00:27:54.510
will eat up a little
bit more storage.
00:27:55.700 --> 00:27:58.082
We also had a great session
with a guy named Surat,
00:27:58.082 --> 00:28:01.338
who talked about external sharing
and all that we're doing there.
00:28:01.338 --> 00:28:04.669
And that's an area where
feels like full trust code.
00:28:04.669 --> 00:28:05.980
W we're not there, but
we're getting there.
00:28:05.980 --> 00:28:09.676
And it's gonna be a lot, lot better,
and a lot more connected to Office
00:28:09.676 --> 00:28:13.360
365 instead of being this
SharePoint siloed experience.
00:28:13.360 --> 00:28:16.520
And it'll pull in the other
things that calendaring, IM, and
00:28:16.520 --> 00:28:17.110
whatnot are doing.
00:28:17.110 --> 00:28:21.340
And then finally, we've been doing
a lot to optimize the pages.
00:28:21.340 --> 00:28:24.930
I'll throw out a watch to anybody
that can guess if you stretched
00:28:24.930 --> 00:28:29.120
where the boundaries are based on
this list, what's the most perfor?
00:28:29.120 --> 00:28:29.920
Let me make sure it's on here.
00:28:31.490 --> 00:28:32.880
Yes, it is.
00:28:32.880 --> 00:28:38.150
What is the most performant page
based on SharePoint in Office365?
00:28:38.150 --> 00:28:40.710
And it's in this list.
00:28:40.710 --> 00:28:41.260
>> OneDrive.
00:28:41.260 --> 00:28:42.540
>> OneDrive, nice.
00:28:42.540 --> 00:28:43.390
Watch coming your way.
00:28:43.390 --> 00:28:44.248
Apologize for any bruises.
00:28:47.650 --> 00:28:49.770
So OneDrive for Business, the UI.
00:28:49.770 --> 00:28:53.231
And they talked about the next
level of UI changes coming here is
00:28:53.231 --> 00:28:54.811
the most performant thing.
00:28:54.811 --> 00:28:57.605
And the kind of proof point there is
when you call support, you say my
00:28:57.605 --> 00:29:00.720
portal or my site is running
a little slow, what's the deal?
00:29:00.720 --> 00:29:02.590
The first thing they are going to
ask you to do is to launch your
00:29:02.590 --> 00:29:04.220
OneDrive for Business page.
00:29:04.220 --> 00:29:06.080
Whoever is calling, their page.
00:29:06.080 --> 00:29:09.320
And that page should load as fast
as anything SharePoint running can.
00:29:09.320 --> 00:29:11.510
And then,
they say is that running slow?
00:29:11.510 --> 00:29:13.450
If not,
then they start to troubleshoot and
00:29:13.450 --> 00:29:16.250
navigate what might be going
on with that custom this,
00:29:16.250 --> 00:29:18.180
custom that that you've
done to the team or portal.
00:29:18.180 --> 00:29:21.580
So there's been a lot of innovation
around obviously, OneDrive for
00:29:21.580 --> 00:29:25.580
Business, Team Sites, and
anything that loads up and
00:29:25.580 --> 00:29:26.420
comes from SharePoint.
00:29:26.420 --> 00:29:28.320
We want that to be super fast.
00:29:28.320 --> 00:29:31.490
But, Office365 has it's
roots in SharePoint online.
00:29:31.490 --> 00:29:33.740
A lot of that is around storage,
00:29:33.740 --> 00:29:38.230
meta data, obviously where the pages
themselves are loaded from.
00:29:38.230 --> 00:29:38.745
And then,
00:29:38.745 --> 00:29:42.130
the back end site collections where
every channel has their videos and
00:29:42.130 --> 00:29:45.470
some of the permissions model that
applies to individual channels.
00:29:45.470 --> 00:29:48.681
OneDrive for
Business certainly has it's roots.
00:29:48.681 --> 00:29:53.830
It used to be called what when it
was first introduced in MySites?
00:29:53.830 --> 00:29:54.502
Watch?
00:29:54.502 --> 00:29:56.022
One person raise their hand and
yell it.
00:29:56.022 --> 00:29:58.938
>> [INAUDIBLE]
>> Ooh, before that.
00:29:58.938 --> 00:30:00.283
What was it used to be called?
00:30:00.283 --> 00:30:02.943
[INAUDIBLE]
>> In my sites it used to be called?
00:30:02.943 --> 00:30:04.335
>> [INAUDIBLE]
>> My documents.
00:30:04.335 --> 00:30:05.079
Where was that?
00:30:05.079 --> 00:30:06.021
All right.
00:30:06.021 --> 00:30:07.621
Oh gosh.
00:30:07.621 --> 00:30:11.000
>> [LAUGH]
>> I knew that was a bad idea.
00:30:11.000 --> 00:30:12.479
I'll walk it back next time.
00:30:12.479 --> 00:30:14.239
>> [INAUDIBLE]
>> Exactly.
00:30:14.239 --> 00:30:18.059
They may be dumb but
I bet they're hurt so I apologize.
00:30:18.059 --> 00:30:22.700
[INAUDIBLE]
>> So, obviously OneDrive for
00:30:22.700 --> 00:30:26.080
Business is going through
a herculean effort in areas that I
00:30:26.080 --> 00:30:27.290
am staying away from.
00:30:27.290 --> 00:30:29.370
When I call it SharePoint Unplugged,
this is not OneDrive for
00:30:29.370 --> 00:30:30.550
Business Unplugged.
00:30:30.550 --> 00:30:31.715
Please don't ask me about sync.
00:30:31.715 --> 00:30:35.872
>> [LAUGH]
>> There's a whole session on that,
00:30:35.872 --> 00:30:38.230
and Jason Moore did actually
a really great job.
00:30:38.230 --> 00:30:39.420
But it does Office 365.
00:30:39.420 --> 00:30:43.060
One Drive for Business is of
course built on SharePoint and
00:30:43.060 --> 00:30:44.640
it benefits from that greatly.
00:30:44.640 --> 00:30:47.790
And it certainly is the business
side of something that also
00:30:47.790 --> 00:30:48.520
has consumer.
00:30:48.520 --> 00:30:51.330
And it's really interesting
to see where those are going.
00:30:51.330 --> 00:30:53.090
But Delve and Office Graph.
00:30:53.090 --> 00:30:55.360
And this will be a t-shirt.
00:30:55.360 --> 00:30:57.440
And I'll try to save some
things during the thing.
00:30:57.440 --> 00:30:59.815
What is the office
graph built on top of.
00:30:59.815 --> 00:31:04.500
>> [INAUDIBLE]
>> Search, yep so is fast.
00:31:06.200 --> 00:31:09.190
So fast is getting some
innovation certainly.
00:31:09.190 --> 00:31:11.940
A lot of the innovation though
is in the Office Graph, but
00:31:11.940 --> 00:31:15.409
without the fast search index, or
just the enterprise search index,
00:31:16.460 --> 00:31:20.760
the Office Graph is just
a layer on top of a mud pile.
00:31:20.760 --> 00:31:25.260
But it of course, Delve has some of
the experience in the profile and
00:31:25.260 --> 00:31:28.400
we talked about that a little bit
from a portal perspective and
00:31:28.400 --> 00:31:31.090
a lot of things that we're doing to
pull in information from a lot of
00:31:31.090 --> 00:31:33.670
different areas are based
on some of those hooks.
00:31:33.670 --> 00:31:36.760
We're taking signals to the graph,
but it's based on some of the work
00:31:36.760 --> 00:31:40.418
certainly fasting and it is that
team that's building the graph.
00:31:40.418 --> 00:31:43.060
One non SharePoint thing
that's fed by the graph which
00:31:43.060 --> 00:31:46.910
obviously then feeds off of
the fast index is Clutter.
00:31:46.910 --> 00:31:50.480
Clutter's a new exchange thing that
helps you manage your mailbox,
00:31:50.480 --> 00:31:53.130
so the SharePoint has
a few hooks into clutter.
00:31:54.270 --> 00:31:57.710
Groups, Office 365
Groups specifically,
00:31:57.710 --> 00:31:59.960
benefits from the files
side of things,
00:31:59.960 --> 00:32:03.990
get files based on SharePoint
teamsites, the document libraries.
00:32:03.990 --> 00:32:06.740
And some of the sites that they
talked about here that's coming
00:32:06.740 --> 00:32:09.250
will have some of its
grounding around SharePoint.
00:32:09.250 --> 00:32:12.500
They won't just look like a teamsite
you've seen in the past, but
00:32:12.500 --> 00:32:16.820
certainly derived and built on
top of that same infrastructure.
00:32:16.820 --> 00:32:19.540
People Experiences, I think
I've talked that one through.
00:32:19.540 --> 00:32:21.230
Modern Attachments.
00:32:21.230 --> 00:32:25.048
I watched a throw,
why does Modern Attachments have
00:32:25.048 --> 00:32:28.809
any significance to
SharePoint in Office 365?
00:32:28.809 --> 00:32:32.447
>> [INAUDIBLE]
>> Where specifically?
00:32:32.447 --> 00:32:33.850
>> [INAUDIBLE]
>> All right,
00:32:33.850 --> 00:32:36.770
I'll give it to you because you
weren't too far behind having it.
00:32:36.770 --> 00:32:37.600
These don't fly straight.
00:32:38.950 --> 00:32:39.720
I apologize.
00:32:41.770 --> 00:32:46.560
So when you are in today outlook
web app and you go and navigate and
00:32:46.560 --> 00:32:50.190
attach a file and send it on
through so it goes to somebody.
00:32:50.190 --> 00:32:52.440
Hopefully the intent is you just
keep the file where it is and
00:32:52.440 --> 00:32:54.340
you're just providing
a link back to it.
00:32:54.340 --> 00:32:57.160
Not a new thing that we invented but
the way that we're doing,
00:32:57.160 --> 00:33:00.130
I think is very smart in that
if the file that doesn't yet
00:33:00.130 --> 00:33:01.990
live in OneDrive, it goes there.
00:33:01.990 --> 00:33:05.360
And anybody on the to line gets
permission so that they can view it.
00:33:05.360 --> 00:33:08.390
A lot easier way to share content
and I guarantee if you start playing
00:33:08.390 --> 00:33:11.760
with it a little bit,
it's a much easier way to do it.
00:33:11.760 --> 00:33:13.300
And it's coming to Office 2016,
00:33:13.300 --> 00:33:15.770
so you'll have that same
experience on the desktop.
00:33:15.770 --> 00:33:17.900
But again, grounded in
the file disc to OneDrive for
00:33:17.900 --> 00:33:19.980
Business if it's not there already.
00:33:19.980 --> 00:33:23.060
And then Document Conversations is
just something that we benefit by
00:33:23.060 --> 00:33:24.250
connecting to Yammer.
00:33:24.250 --> 00:33:27.550
We also do it for videos, so we
don't call it video conversations,
00:33:27.550 --> 00:33:29.040
but you can think of it that way.
00:33:29.040 --> 00:33:33.370
If I'm looking at a document using
office online there's a little slide
00:33:33.370 --> 00:33:37.210
out to have Yammer conversation
side by side for that document and
00:33:37.210 --> 00:33:40.630
of course that's powered by office
online, Yammer and then ultimately
00:33:40.630 --> 00:33:43.590
where the document lives doesn't
have to be anything but it's usually
00:33:43.590 --> 00:33:47.290
going to be a SharePoint document
library or OneDrive for Business.
00:33:47.290 --> 00:33:50.260
>> So there's a lot of things that
should be attributed to SharePoint
00:33:50.260 --> 00:33:51.540
but we don't lead with it.
00:33:51.540 --> 00:33:54.460
But hopefully back to Mark's
question before we got started.
00:33:54.460 --> 00:33:58.700
If you still think SharePoint
is dead, good luck killing it.
00:33:58.700 --> 00:34:00.420
This horse is still racing.
00:34:00.420 --> 00:34:03.320
So I can scroll up and down.
00:34:03.320 --> 00:34:04.300
That's really the end.
00:34:04.300 --> 00:34:07.090
The last thing I was going to
click into is just a couple of fun
00:34:07.090 --> 00:34:07.840
pictures I took.
00:34:07.840 --> 00:34:12.270
And this is just for me to buy time
until our hosts with the mics.
00:34:12.270 --> 00:34:15.640
If you have any questions,
this is really to open it up.
00:34:15.640 --> 00:34:17.290
Whatever questions you have.
00:34:17.290 --> 00:34:19.880
If we can't hustle a mic to you,
I will repeat it.
00:34:19.880 --> 00:34:21.570
I try to do pretty well at that.
00:34:21.570 --> 00:34:26.040
And I'll just say,
thanks to Mavention for
00:34:26.040 --> 00:34:28.025
the stroopwafels they
brought from the Netherlands.
00:34:28.025 --> 00:34:30.930
>> [LAUGH]
>> Almost everybody represented.
00:34:30.930 --> 00:34:32.890
The only tag they didn't have
was OneDrive for Business, and
00:34:32.890 --> 00:34:35.135
I think that's just because
it wasn't synced over here.
00:34:35.135 --> 00:34:38.990
>> [LAUGH]
>> And
00:34:38.990 --> 00:34:42.690
if you didn't see the monkey, you'll
see one today flying to somebody.
00:34:42.690 --> 00:34:44.670
There was a big monkey,
he was pretty fun.
00:34:44.670 --> 00:34:46.610
And we'll make sure
to bring him back.
00:34:46.610 --> 00:34:49.890
And then did everybody
enjoy Fall Out last night?
00:34:49.890 --> 00:34:50.450
It's pretty fun.
00:34:50.450 --> 00:34:52.590
I certainly feel a little older,
00:34:52.590 --> 00:34:54.585
I kept referring to they sounded
a little bit like Bon Jovi.
00:34:54.585 --> 00:34:57.340
[LAUGH] And that just revealed me.
00:34:58.370 --> 00:35:01.820
So with that first question,
if it's at the microphone,
00:35:01.820 --> 00:35:04.870
if not, we'll have time to
make it all the way around.
00:35:04.870 --> 00:35:05.784
Question.
00:35:05.784 --> 00:35:08.660
>> All right, so
not exactly a OneDrive sync
00:35:08.660 --> 00:35:09.600
question but-
>> Okay.
00:35:09.600 --> 00:35:13.330
>> We see any of the selective
sync capabilities from OneDrive
00:35:13.330 --> 00:35:15.180
coming into SharePoint
document libraries?
00:35:15.180 --> 00:35:16.210
>> Yeah, it's a good question.
00:35:16.210 --> 00:35:17.910
So I'll answer what they did say,
and
00:35:17.910 --> 00:35:20.880
then I'll try to kind of formulate
I think where we're going.
00:35:20.880 --> 00:35:22.080
And what I can say.
00:35:22.080 --> 00:35:23.550
So the question around sync.
00:35:24.580 --> 00:35:27.580
The consumer version of OneDrive,
for consumers,
00:35:27.580 --> 00:35:31.400
even though we just call it
OneDrive does have selective sync.
00:35:31.400 --> 00:35:34.300
Meaning you could have a terrabyte
of content, but on your little
00:35:34.300 --> 00:35:37.980
tablet that has 250 megs of
SSD that's super precious for
00:35:37.980 --> 00:35:40.970
your next movie on the plane,
we don't want to take up that space.
00:35:40.970 --> 00:35:43.940
So you can obviously opt
out of things to sync over.
00:35:43.940 --> 00:35:47.210
In OneDrive for
Business today it's all or none.
00:35:47.210 --> 00:35:49.650
So that is coming to OneDrive for
Business.
00:35:49.650 --> 00:35:51.480
From a team site perspective,
00:35:51.480 --> 00:35:54.900
the team is really at a stage where
they're trying to look at this next
00:35:54.900 --> 00:35:56.670
gen sync client that
they talked about here.
00:35:56.670 --> 00:35:59.150
If that will be
applied to team sites.
00:35:59.150 --> 00:36:04.780
Both is on premises and that's
both SharePoint online team sites.
00:36:04.780 --> 00:36:08.320
Where I think we are is that
will continue to be Groove,
00:36:08.320 --> 00:36:11.060
which is the sync client
that we know today.
00:36:11.060 --> 00:36:13.380
Which is gonna get
continued investments.
00:36:13.380 --> 00:36:15.370
And if you tried that thing,
which we all joke about, and
00:36:15.370 --> 00:36:16.600
there's a reason for it.
00:36:16.600 --> 00:36:21.100
We're not aside to what
the problems are, but
00:36:21.100 --> 00:36:23.860
if you looked at it about six
months ago it was really bad.
00:36:23.860 --> 00:36:27.400
And a lot of that is just
because we hit scale.
00:36:27.400 --> 00:36:30.450
We've had a 500% growth
of content coming in.
00:36:30.450 --> 00:36:32.550
And that technology is you know.
00:36:32.550 --> 00:36:35.010
But there is a team that will be
investing to continue that for
00:36:35.010 --> 00:36:35.610
on premises.
00:36:35.610 --> 00:36:37.030
SharePoint 2016, SharePoint 2013,
00:36:37.030 --> 00:36:40.840
and of course SharePoint Online
on the team side.
00:36:40.840 --> 00:36:42.860
What I think they will review, but
00:36:42.860 --> 00:36:45.670
I don't think it'll be in the first
iteration of the next gen sync,
00:36:45.670 --> 00:36:49.400
is how can we do what we did for
OneDrive for team.
00:36:49.400 --> 00:36:53.990
But a lot of our why we need to keep
it as is is because of on premises,
00:36:53.990 --> 00:36:56.800
nobody's, not everybody's
gonna run the 2016 right away.
00:36:56.800 --> 00:36:58.400
So of course we will maintain that.
00:36:58.400 --> 00:37:01.700
And with that not need
to shift too quickly,
00:37:01.700 --> 00:37:04.670
it'll apply to the online
team sites as well.
00:37:04.670 --> 00:37:06.995
Good question.
>> PowerPoint is my mojo.
00:37:06.995 --> 00:37:07.630
>> [LAUGH]
>> All right,
00:37:07.630 --> 00:37:10.290
that means he gets a prize.
00:37:10.290 --> 00:37:12.428
So if you didn't know why
Daniel just stood up,
00:37:12.428 --> 00:37:15.473
it's because there was just a tweet
that went out that said the first
00:37:15.473 --> 00:37:17.141
person that stands up and says that.
00:37:17.141 --> 00:37:21.280
>> [LAUGH]
>> So thank you for playing.
00:37:21.280 --> 00:37:22.930
All right, next question.
00:37:22.930 --> 00:37:24.610
>> Hi, I have two questions.
00:37:24.610 --> 00:37:25.330
>> Okay.
00:37:25.330 --> 00:37:27.920
>> Our first question is we in
Germany there's a big problem.
00:37:27.920 --> 00:37:30.041
Everybody loves Office 365.
00:37:30.041 --> 00:37:31.460
>> Yeah.
>> CEO's and
00:37:31.460 --> 00:37:33.730
other management don't
trust the cloud to us.
00:37:33.730 --> 00:37:36.071
>> Yep.
>> Our managers travel and
00:37:36.071 --> 00:37:38.380
how do you convince people?
00:37:38.380 --> 00:37:41.080
>> Yeah, I don't know if it's only
because it's the data center is not
00:37:41.080 --> 00:37:41.605
in Germany.
00:37:41.605 --> 00:37:42.930
>> [LAUGH]
>> Maybe.
00:37:42.930 --> 00:37:46.476
I know that Germany,
maybe France, not France, Japan.
00:37:46.476 --> 00:37:49.492
I know Germany for sure,
has data sovereignty,
00:37:49.492 --> 00:37:52.980
where they want everything
within the country.
00:37:52.980 --> 00:37:55.800
To be honest it feels like the
conversations are sometimes around
00:37:55.800 --> 00:37:59.701
that, sometimes around the EU model
class like is this American company
00:37:59.701 --> 00:38:02.040
that has my data,
what they are going to do with it.
00:38:02.040 --> 00:38:05.358
A lot of it is just a transparency,
we do talk about the feature set,
00:38:05.358 --> 00:38:07.645
there is lot of interest
in the what you can do.
00:38:07.645 --> 00:38:10.010
There's a lot that you
can do around hybrid.
00:38:10.010 --> 00:38:13.089
The thing that I've seen make the
most motion, not just with Germany,
00:38:13.089 --> 00:38:16.030
but for anybody that's reserved
about going to the cloud
00:38:16.030 --> 00:38:18.460
is from a hybrid model,
especially search.
00:38:18.460 --> 00:38:21.340
All it's doing is it's putting
the metadata on the elements up into
00:38:21.340 --> 00:38:24.050
the cloud and giving you a view
on where is my stuff and
00:38:24.050 --> 00:38:25.420
how can I find it?
00:38:25.420 --> 00:38:27.510
But we're making, seems like
some of the feedback we're
00:38:27.510 --> 00:38:30.300
getting is the progress is
we don't move the content.
00:38:30.300 --> 00:38:32.520
You may be thinking
of a migration but
00:38:32.520 --> 00:38:35.030
there are ways that you
don't have to migrate.
00:38:35.030 --> 00:38:38.880
The other area of investment that I
think we've been investing in more
00:38:38.880 --> 00:38:42.660
than people realize is just plain
security and that's at every level.
00:38:43.990 --> 00:38:47.420
So, we like to challenge a little
bit, look at what we're doing.
00:38:47.420 --> 00:38:50.070
We're super open and
have workshops and
00:38:50.070 --> 00:38:51.820
we'll go as deep as anybody wants.
00:38:51.820 --> 00:38:54.730
That just purely talks about
how your data is secure.
00:38:54.730 --> 00:38:55.790
How it's private.
00:38:55.790 --> 00:38:57.290
The SLAs that are behind that.
00:38:57.290 --> 00:38:59.040
The people that are behind that.
00:38:59.040 --> 00:39:02.110
So it's hard to move to needle
on when somebody just says
00:39:02.110 --> 00:39:04.430
we won't do it if
it's not in Germany.
00:39:04.430 --> 00:39:06.805
And to that I say ich bin,
I don't know something.
00:39:06.805 --> 00:39:09.980
>> [APPLAUSE]
>> But,
00:39:09.980 --> 00:39:12.740
the reality is exactly it
could be in SharePoint.
00:39:14.010 --> 00:39:16.290
The reality is,
it's just a conversation, and
00:39:16.290 --> 00:39:18.640
sometimes the needle moves,
and sometimes it doesn't.
00:39:18.640 --> 00:39:20.080
And it's different in
different sectors and
00:39:20.080 --> 00:39:24.120
different kind of customers but
we have seen folks interested and
00:39:24.120 --> 00:39:27.640
okay about certain type of
workloads moving to the cloud.
00:39:27.640 --> 00:39:32.260
And some of that is, is it HBI,
which is it super critical and
00:39:32.260 --> 00:39:34.330
highly confidential
type information?
00:39:34.330 --> 00:39:37.761
All the way down to LBI and
these are our internal terms so
00:39:37.761 --> 00:39:41.995
I apologize, but LBI meaning it's
probably just a team site offsite
00:39:41.995 --> 00:39:44.340
photo type thing, but those levels.
00:39:44.340 --> 00:39:45.860
And LBI and
00:39:45.860 --> 00:39:51.300
MBI were actually the first things
to be okayed by our internal teams.
00:39:51.300 --> 00:39:52.362
One of them is sitting here so
00:39:52.362 --> 00:39:54.413
he'll raise his hand if I'm
saying something wrong.
00:39:54.413 --> 00:39:58.163
But the MSIT team at our
organization, within Microsoft,
00:39:58.163 --> 00:40:02.069
our own tenant in the multi
tenant space just like everybody.
00:40:02.069 --> 00:40:05.859
It also took some time to get to
where they would be okay with where
00:40:05.859 --> 00:40:07.710
HBI content lived.
00:40:07.710 --> 00:40:11.320
And they did some unique things
around some app model and
00:40:11.320 --> 00:40:12.450
user awareness.
00:40:12.450 --> 00:40:15.130
And of course with DLP and
encryption at rest and
00:40:15.130 --> 00:40:18.380
some other things coming, there's
just a ton of reasons why people
00:40:18.380 --> 00:40:20.580
should look again,
ask the question again.
00:40:20.580 --> 00:40:24.210
And if it's still just because then,
we'll just
00:40:24.210 --> 00:40:26.780
talk to them in six months again and
see where they're at.
00:40:26.780 --> 00:40:27.640
Cuz I think the value
00:40:27.640 --> 00:40:30.100
that they get by moving to
the cloud will erase some of that.
00:40:30.100 --> 00:40:32.440
Some of that is law based and,
00:40:32.440 --> 00:40:34.310
there's some things we
can't do about that.
00:40:34.310 --> 00:40:35.440
So, second question?
00:40:35.440 --> 00:40:37.147
>> Second question is
Sharepoint related.
00:40:37.147 --> 00:40:40.488
We have a big Sharepoint environment
in our company with a lot of
00:40:40.488 --> 00:40:41.060
service.
00:40:41.060 --> 00:40:45.050
And, right now, evaluate if we
should stay in the future on PREM,
00:40:45.050 --> 00:40:48.346
if you should move in a hybrid
solution or on the cloud.
00:40:48.346 --> 00:40:51.468
What are the main arguments or
the main topics
00:40:51.468 --> 00:40:55.669
that we should take in consideration
to make this decision?
00:40:55.669 --> 00:40:58.519
>> So I think there's reality that's
surfaced over the last couple of
00:40:58.519 --> 00:41:01.590
years, you just can't move
everything all at once.
00:41:01.590 --> 00:41:05.140
And there may be specific groups
that need it more than others.
00:41:05.140 --> 00:41:08.100
And certain workloads just
work better in the cloud.
00:41:08.100 --> 00:41:12.490
A lot of those is because mobile is
really important to access news,
00:41:12.490 --> 00:41:15.110
to access your documents that
you work with all the time.
00:41:15.110 --> 00:41:18.650
And some of it is because
it's internet facing,
00:41:18.650 --> 00:41:21.590
you don't have to go through
some of the same hurdles.
00:41:21.590 --> 00:41:24.904
But we do support things like
two-factor authentication, so
00:41:24.904 --> 00:41:27.663
you can still move relatively
critical workloads.
00:41:27.663 --> 00:41:31.637
The way that they did it, and again,
I'm kinda using this as a reference,
00:41:31.637 --> 00:41:33.152
my documents to One Drive for
00:41:33.152 --> 00:41:36.960
Business for Microsoft at the time
it wasn't 120,000 people.
00:41:36.960 --> 00:41:40.950
But I believe now that's roughly
the number, at least 100,000 plus.
00:41:40.950 --> 00:41:42.920
That was one of the first
workloads to move.
00:41:42.920 --> 00:41:46.240
Then all of our team calibration
sites was the next thing to move.
00:41:46.240 --> 00:41:49.940
And then what David and team shared
here, is they had a whole session on
00:41:49.940 --> 00:41:52.330
how Microsoft is moving
all of their portals.
00:41:52.330 --> 00:41:53.920
And there's a company Internet.
00:41:53.920 --> 00:41:57.360
There's what we are using for
our media distribution.
00:41:57.360 --> 00:42:00.220
And then there's also talk about
moving that to Office 365 video.
00:42:00.220 --> 00:42:02.210
And it's been incremental.
00:42:02.210 --> 00:42:06.020
And they've had some hooks to
connect with the systems back on
00:42:06.020 --> 00:42:08.240
premises just from
a hybrid perspective.
00:42:08.240 --> 00:42:12.488
And then transparently there's just
things that haven't moved yet or
00:42:12.488 --> 00:42:14.480
maybe won't move for some time.
00:42:15.610 --> 00:42:18.290
I don't think Hybrid is
scary as it used to be.
00:42:18.290 --> 00:42:21.340
We have a lot of great documentation
on how to do single sign on.
00:42:21.340 --> 00:42:23.590
We got a lot of great people
that have been trained on it so
00:42:23.590 --> 00:42:24.760
that they can accomplish that more.
00:42:24.760 --> 00:42:26.520
That's the foundational thing.
00:42:26.520 --> 00:42:29.450
And then is it a pilot phase?
00:42:29.450 --> 00:42:31.790
Do you want to just try
the cloud to see what it's like?
00:42:31.790 --> 00:42:33.190
That's very possible.
00:42:33.190 --> 00:42:35.420
Pull back any time you want.
00:42:35.420 --> 00:42:38.520
But from a cost model,
you know the effort certainly
00:42:38.520 --> 00:42:41.880
we don't hide there is
effort to migrate content.
00:42:41.880 --> 00:42:44.490
If there's anything that's been
customized to make sure it lands
00:42:44.490 --> 00:42:47.620
intact and to be aware along the way
00:42:47.620 --> 00:42:49.370
what are going to be some
of the common pitfalls.
00:42:49.370 --> 00:42:52.010
And that's a lot of what we
shared here at the conference.
00:42:52.010 --> 00:42:53.980
So I think it's more
of just get started.
00:42:53.980 --> 00:42:58.010
And it's not listen to me because,
of course, would love it if you did.
00:42:58.010 --> 00:42:59.650
The reality is there's
benefits to it.
00:42:59.650 --> 00:43:03.850
And we're not hiding the services
in Office 365 so you move there.
00:43:03.850 --> 00:43:05.700
That is not a winning strategy.
00:43:05.700 --> 00:43:08.590
That's why we have all of
the APIs we're turning out.
00:43:08.590 --> 00:43:11.200
That's why we're doing
the hybrid motion.
00:43:11.200 --> 00:43:14.177
The reality, though, is some of the
things that we do in the cloud we
00:43:14.177 --> 00:43:17.052
can't put in the box, and know
your environment to test them well
00:43:17.052 --> 00:43:20.267
enough, and then support them over
time with the changes that you make.
00:43:20.267 --> 00:43:24.385
So we hope that connecting to them,
or potentially moving to them,
00:43:24.385 --> 00:43:26.843
is something you can
do incrementally,
00:43:26.843 --> 00:43:29.609
if not maybe significantly,
at some point.
00:43:29.609 --> 00:43:32.232
But just getting started
is usually a great thing.
00:43:32.232 --> 00:43:34.220
And then tell us what you like,
tell us what you don't like.
00:43:35.550 --> 00:43:36.620
You're welcome.
00:43:36.620 --> 00:43:38.743
All right, next question.
00:43:38.743 --> 00:43:43.290
>> I had a question about what seems
to be missing so far at Ignite, and that's-
00:43:43.290 --> 00:43:43.905
>> Yep.
00:43:43.905 --> 00:43:45.904
>> That's-
>> Oh, there you go [LAUGH]
00:43:45.904 --> 00:43:47.123
>> That's InfoPath.
00:43:47.123 --> 00:43:48.063
>> Oh, yeah, good.
00:43:48.063 --> 00:43:51.936
>> I know it's deprecated, but
I know how heavily it's used under
00:43:51.936 --> 00:43:56.480
the hood by things like Workflow, so
it's not gonna go away anytime soon.
00:43:56.480 --> 00:43:58.520
What's the recommendation
going forward?
00:43:58.520 --> 00:44:02.300
And if that recommendation is
JS Link and Client-Side Rendering,
00:44:02.300 --> 00:44:04.620
is there gonna be more
documentation and
00:44:04.620 --> 00:44:07.040
information coming out
of Microsoft about that?
00:44:07.040 --> 00:44:07.540
>> Yep.
00:44:08.570 --> 00:44:10.386
So I'll take a deep breath.
00:44:10.386 --> 00:44:13.317
And I'll say I am not Sonya Katya,
but
00:44:13.317 --> 00:44:16.349
I certainly will try
to copy her today.
00:44:16.349 --> 00:44:18.869
The key thing is InfoPath
is not going away.
00:44:18.869 --> 00:44:23.502
And if this sounds a little bit like
regurgitation of what we put out
00:44:23.502 --> 00:44:25.570
about two or three weeks ago,
00:44:25.570 --> 00:44:29.560
InfoPath 2013 will be
supported through 2023.
00:44:29.560 --> 00:44:33.885
So starting and using InfoPath
today is not a terrible idea for
00:44:33.885 --> 00:44:36.306
continuing for what's up there.
00:44:36.306 --> 00:44:37.901
But there won't be a version next,
00:44:37.901 --> 00:44:39.824
we're trying to be
very clear about that.
00:44:39.824 --> 00:44:42.895
The other thing is
in SharePoint 2016,
00:44:42.895 --> 00:44:47.377
there will still be InfoPath form
services as you know it today,
00:44:47.377 --> 00:44:51.611
so upgrade won't break anything
from a forms perspective.
00:44:51.611 --> 00:44:54.466
Of course it'll continue
to be supported in 2013 and
00:44:54.466 --> 00:44:57.975
it will continue to be supported in
SharePoint online which started in
00:44:57.975 --> 00:45:02.100
its instance as recently as 2013,
but it was really beyond that.
00:45:02.100 --> 00:45:06.880
So the other area that a lot of
people ask about is Workflow,
00:45:06.880 --> 00:45:09.630
like he said,
Workflow doesn't also go away.
00:45:09.630 --> 00:45:11.340
You know, SharePoint 2010 Workflows,
00:45:11.340 --> 00:45:14.150
which are Workflows running inside
of SharePoint, hopefully you've
00:45:14.150 --> 00:45:17.460
maybe more of been playing around
with SharePoint 2013 Workflows,
00:45:17.460 --> 00:45:20.130
which means the Workflows
run in Azure.
00:45:20.130 --> 00:45:23.200
Both of those in those patterns
are sometimes choices,
00:45:23.200 --> 00:45:26.300
we have preferences, but we don't
expect everybody to jump ship and
00:45:26.300 --> 00:45:28.550
go one way, so fast.
00:45:28.550 --> 00:45:30.960
And those same patterns
will be in 2016 and
00:45:30.960 --> 00:45:34.490
going forward, connected to
Visual Studio, writing some hardcore
00:45:34.490 --> 00:45:38.120
Workflow activities and having them
run, and then of course, the K2s and
00:45:38.120 --> 00:45:41.389
Nintex of the world, adding a ton
of value and that continues.
00:45:42.660 --> 00:45:44.130
Next question?
00:45:44.130 --> 00:45:47.660
>> I'm glad that we are going
towards the multi-device support,
00:45:47.660 --> 00:45:52.770
but what I have not heard is are the
SharePoints provided features and
00:45:52.770 --> 00:45:53.380
functions.
00:45:53.380 --> 00:45:55.890
Do they work across
multiple devices?
00:45:55.890 --> 00:45:58.700
An example I can give you
is the Explorer view.
00:45:58.700 --> 00:46:02.849
A lot of people still think
that SharePoint is nothing but
00:46:02.849 --> 00:46:07.602
a shared drive and map it at the
SharePoint site as a network map and
00:46:07.602 --> 00:46:09.503
drag and drop the files and
00:46:09.503 --> 00:46:13.770
losing a lot of [INAUDIBLE]
without saving functionality.
00:46:13.770 --> 00:46:15.230
Automatically check load to them.
00:46:15.230 --> 00:46:18.240
They never know the document
has been checked out.
00:46:18.240 --> 00:46:19.895
And the function
doesn't work on Mac.
00:46:19.895 --> 00:46:20.550
>> Yep.
00:46:20.550 --> 00:46:22.300
>> So what are these pads?
00:46:22.300 --> 00:46:27.510
So make all the functions and
features work the same
00:46:27.510 --> 00:46:31.685
way on all the devices or
shut them out.
00:46:31.685 --> 00:46:34.445
>> Yeah,
we don't have the 100% answer.
00:46:34.445 --> 00:46:38.465
A lot of it was routed that there
was so much based on ActiveX and
00:46:38.465 --> 00:46:42.915
certainly beyond ActiveX, anything
that was a SharePoint specific
00:46:44.595 --> 00:46:46.775
feature or development pattern.
00:46:46.775 --> 00:46:50.005
So if you look across the various
versions across the years,
00:46:50.005 --> 00:46:52.810
we've been lessening the amount
of requirement for ActiveX.
00:46:52.810 --> 00:46:56.340
So there's a lot more you
can do across the browsers.
00:46:56.340 --> 00:46:59.780
When you land on specific
things that you mentioned, I
00:46:59.780 --> 00:47:02.780
think the same development patterns
that we're promoting for people to
00:47:02.780 --> 00:47:05.690
build their own custom solution,
the team is also adhering to.
00:47:05.690 --> 00:47:08.654
And specifically you can look at
that as what they're doing for
00:47:08.654 --> 00:47:11.100
One Drive for
business NextGen portals and
00:47:11.100 --> 00:47:12.665
some of the working groups.
00:47:12.665 --> 00:47:14.900
They're following the same patterns,
which at the end of the day,
00:47:14.900 --> 00:47:20.630
equates to there's more based on
not SharePoint proprietary methods,
00:47:20.630 --> 00:47:22.320
more based on open standards.
00:47:22.320 --> 00:47:23.897
Which our intent is to make it so
00:47:23.897 --> 00:47:26.931
that you can do a lot common
experiences across browsers and
00:47:26.931 --> 00:47:29.570
certainly across
the larger platforms.
00:47:29.570 --> 00:47:31.952
When it drills into
a specific one and
00:47:31.952 --> 00:47:34.110
when is that going to be resolved?
00:47:34.110 --> 00:47:36.708
I can follow up with the team
if you send me an email.
00:47:36.708 --> 00:47:40.898
I don't know exactly, but
the footprint is getting smaller and
00:47:40.898 --> 00:47:44.476
smaller for where we require
things that required IE.
00:47:44.476 --> 00:47:48.052
We do an inStream experiment, if you
look at what the experience is on
00:47:48.052 --> 00:47:51.310
Project Spartan now
known as Microsoft Edge.
00:47:51.310 --> 00:47:55.070
It also is in that same camp,
it's not IE, certainly grounded and
00:47:55.070 --> 00:47:55.800
rooted in it.
00:47:55.800 --> 00:47:58.290
And I'm not fluent in it so
don't quote me on anything,
00:47:58.290 --> 00:48:02.610
but I was a little hesitant to load
my machine up with Windows 10 and
00:48:02.610 --> 00:48:04.710
Office 2016 and go for Spartan.
00:48:04.710 --> 00:48:05.550
That was the booth.
00:48:05.550 --> 00:48:09.030
And it was pretty good, but
still hit some areas that were like,
00:48:09.030 --> 00:48:10.340
okay maybe they're not finished and
00:48:10.340 --> 00:48:12.300
they're not shipped yet,
so give them that.
00:48:12.300 --> 00:48:16.380
But it's built in a way that is
not to adhere to these backend
00:48:16.380 --> 00:48:19.320
services that are specifically
Microsoft to Microsoft.
00:48:19.320 --> 00:48:21.790
They are built with
open standards in mind.
00:48:21.790 --> 00:48:26.530
So, why I'm saying that is I think
that if it doesn't work in Spartan,
00:48:26.530 --> 00:48:31.191
of course if it doesn't work in
Chrome, Firefox, Safari, other but
00:48:31.191 --> 00:48:33.966
we think of them as
more modern browsers.
00:48:33.966 --> 00:48:36.752
We want our experience to
be common across them.
00:48:36.752 --> 00:48:41.557
Maybe I'd say a 50 to 75% answer,
but hopefully indicative of
00:48:41.557 --> 00:48:45.108
what I'm aware of and
where I think we're going.
00:48:45.108 --> 00:48:45.731
>> So.
00:48:45.731 --> 00:48:47.714
>> [INAUDIBLE]
>> All right, ready?
00:48:47.714 --> 00:48:49.083
>> Okay.
>> All right so
00:48:49.083 --> 00:48:52.182
I have two more specific questions.
00:48:52.182 --> 00:48:53.191
Is this possible?
00:48:53.191 --> 00:48:53.772
>> Yes.
00:48:53.772 --> 00:48:54.410
>> Can I do this?
00:48:54.410 --> 00:48:55.866
>> Is this possible, okay?
00:48:55.866 --> 00:48:57.270
Yes, you can do
anything on SharePoint.
00:48:57.270 --> 00:49:03.670
>> [LAUGH] If only that were true.
00:49:03.670 --> 00:49:06.519
My first question is regarding
drop off libraries and
00:49:06.519 --> 00:49:10.329
maintaining the link to documents
when routed to their file location.
00:49:10.329 --> 00:49:14.844
Specially, if I publish
a link to a central drop off
00:49:14.844 --> 00:49:19.990
library to my users Office
application via Word or Excel.
00:49:22.840 --> 00:49:27.170
Can they send all those Docs to that
drop off library, but then have
00:49:27.170 --> 00:49:32.810
the system set up a link to
the file within a separate library,
00:49:32.810 --> 00:49:36.230
based on that documents content
type, with the final location of
00:49:36.230 --> 00:49:41.270
the document going to a third
library based on specific metadata?
00:49:42.340 --> 00:49:44.304
>> So you wanna take
the A train to the B train,
00:49:44.304 --> 00:49:46.390
and you're not gonna
make it to the airport.
00:49:46.390 --> 00:49:47.772
>> Yes.
00:49:47.772 --> 00:49:50.871
>> I think there are things
that would play into it.
00:49:50.871 --> 00:49:51.643
I'll be honest, I am.
00:49:51.643 --> 00:49:53.886
>> If it's yes or no, and
I will find out if it's a yes.
00:49:53.886 --> 00:49:57.960
>> The reality is when a file drops
into a location, which it sounds
00:49:57.960 --> 00:50:02.184
like not the first stop There
are a lot of move-type scenarios, so
00:50:02.184 --> 00:50:06.160
if a workflow triggered and
was to transfer to move that.
00:50:06.160 --> 00:50:08.610
It's an on-premises, I think,
for sure, and online.
00:50:08.610 --> 00:50:13.180
I don't think we support site
collection to site collection yet.
00:50:13.180 --> 00:50:14.260
>> Okay.
>> So that move,
00:50:14.260 --> 00:50:16.850
if you think about my
common repository,
00:50:16.850 --> 00:50:18.850
where if it's in an education space.
00:50:18.850 --> 00:50:20.480
Here's all the students homework.
00:50:20.480 --> 00:50:22.000
I do all the grading.
00:50:22.000 --> 00:50:24.127
I trigger something that sends
it to the record center.
00:50:24.127 --> 00:50:25.900
I don't know what you would
call that in education.
00:50:25.900 --> 00:50:29.340
You know that would be the final
grade that they get so
00:50:29.340 --> 00:50:30.250
they can't challenge it.
00:50:30.250 --> 00:50:32.873
That thing we didn't change, nobody
can touch it, can't be deleted,
00:50:32.873 --> 00:50:34.080
all those policies.
00:50:34.080 --> 00:50:37.256
Getting it from there to there might
not make sense for a teacher and
00:50:37.256 --> 00:50:40.275
student, because obviously
somebody would have to set it up.
00:50:40.275 --> 00:50:42.730
It's not for everybody to establish.
00:50:42.730 --> 00:50:46.420
But I think if you talk to some
folks like our mic runners.
00:50:46.420 --> 00:50:47.110
You know, they'll tell you,
00:50:47.110 --> 00:50:51.340
that's a great solution that
I think would be custom dev.
00:50:51.340 --> 00:50:54.440
And you may have a component in
between that's sort of a listening
00:50:54.440 --> 00:50:56.130
mechanism for workflow.
00:50:56.130 --> 00:51:00.750
But moving, you can certainly do
file movement with API calls and
00:51:00.750 --> 00:51:03.160
make it so it's not so
scary developer once it's set up.
00:51:03.160 --> 00:51:05.250
It just happens and goes.
00:51:05.250 --> 00:51:07.680
So that's, I think,
a pretty common pattern.
00:51:07.680 --> 00:51:12.000
But I don't want to oversell it all,
so if anybody disagrees any time
00:51:12.000 --> 00:51:13.630
just call my-
>> I will see you after.
00:51:13.630 --> 00:51:14.400
>> Call my initials,
00:51:14.400 --> 00:51:16.510
which are not B.S.
>> Perfect.
00:51:16.510 --> 00:51:20.330
So my second question,
also as specific as the first.
00:51:20.330 --> 00:51:21.510
>> Okay.
>> Is regarding
00:51:21.510 --> 00:51:24.050
content search web parts and
site templates.
00:51:24.050 --> 00:51:27.040
So if I'm utilizing site
templates to mass produce sites.
00:51:27.040 --> 00:51:28.490
>> Yep.
>> Is there a way to set
00:51:28.490 --> 00:51:29.720
the default term for
00:51:29.720 --> 00:51:33.460
that page within the content search
web part to be dynamic and set to
00:51:33.460 --> 00:51:37.200
a metadata tag that matches a unique
element within the site's URL?
00:51:37.200 --> 00:51:37.700
>> Mm.
00:51:38.950 --> 00:51:42.360
All right, so you get your
choice of either a watch or
00:51:42.360 --> 00:51:43.940
a really tiny t-shirt.
00:51:43.940 --> 00:51:45.290
>> [LAUGH]
>> And
00:51:45.290 --> 00:51:49.830
I at least have some friends that
are some pretty deep search experts.
00:51:49.830 --> 00:51:53.950
My first instinct would be, if you
have a common terms store, where
00:51:53.950 --> 00:51:56.630
you're feeding not just at a site
collection level but at a tenant
00:51:56.630 --> 00:51:59.600
level, and certainly on-prem
it might be at the farm level.
00:51:59.600 --> 00:52:03.660
We haven't done anything from
a cross-hybrid metadata management.
00:52:03.660 --> 00:52:05.760
I think there are third
party solutions that can
00:52:05.760 --> 00:52:06.940
help you get a common term set.
00:52:06.940 --> 00:52:09.290
It's a little bit more
from a replication today.
00:52:09.290 --> 00:52:13.110
But if that's true, and I'll wait
till anybody says it's not true,
00:52:14.300 --> 00:52:17.800
then that term that you have
that may be the trigger or
00:52:17.800 --> 00:52:20.530
the commonality should
be the same term.
00:52:20.530 --> 00:52:23.240
No matter where it appears or
how you leverage it.
00:52:23.240 --> 00:52:25.850
That being said, I would certainly
turn you to somebody who would be
00:52:25.850 --> 00:52:28.110
able to go,
what are you trying to do?
00:52:28.110 --> 00:52:29.640
So watch or shirt?
00:52:29.640 --> 00:52:31.033
>> I'll take the tiny shirt please.
00:52:31.033 --> 00:52:32.026
>> [LAUGH] Okay.
00:52:32.026 --> 00:52:33.089
All right.
00:52:33.089 --> 00:52:34.810
Good questions.
00:52:34.810 --> 00:52:36.252
Oh hey.
All right.
00:52:36.252 --> 00:52:38.899
I don't know if there's a mic.
00:52:38.899 --> 00:52:39.944
There you go.
00:52:39.944 --> 00:52:41.360
>> Okay.
00:52:41.360 --> 00:52:42.790
Mine's on hybrid.
00:52:42.790 --> 00:52:45.590
We typically tend to
be a version behind.
00:52:45.590 --> 00:52:48.390
So we're gonna just
be upgrading to 2013.
00:52:48.390 --> 00:52:50.510
But we want to use the hybrid.
00:52:50.510 --> 00:52:52.110
So how will that work?
00:52:52.110 --> 00:52:54.790
You're going to go
to 2016 online now.
00:52:54.790 --> 00:52:56.430
We'll be 2013 on prem.
00:52:56.430 --> 00:53:01.637
And so if we stay a version behind
consistently, how will that work?
00:53:01.637 --> 00:53:04.030
>> Yeah, so it'll just work, really.
00:53:04.030 --> 00:53:07.640
It doesn't jump over the fact
that you have work to do
00:53:07.640 --> 00:53:09.340
to set it up and manage it.
00:53:09.340 --> 00:53:14.050
And then obviously when you go from
2013 to 2016 and first, just a small
00:53:14.050 --> 00:53:17.330
round of applause that you're on
2013, that's not that far behind.
00:53:17.330 --> 00:53:21.580
But, the reality is we've been
supporting hybrid back to 2010.
00:53:21.580 --> 00:53:23.980
Some things you can and
can't do very easily.
00:53:23.980 --> 00:53:26.070
There's a lot of ease
on 2013 because,
00:53:26.070 --> 00:53:28.478
by the way the infrastructures
are relatively common.
00:53:28.478 --> 00:53:29.410
You know, 2013-2016,
00:53:29.410 --> 00:53:33.840
from an infrastructure perspective,
those types of connections, isn't
00:53:33.840 --> 00:53:36.870
changing in the way that it would
break those types of solutions.
00:53:36.870 --> 00:53:38.650
But you're setting
up single sign on,
00:53:38.650 --> 00:53:43.250
you're setting up a part of the
component called ADFS on premises.
00:53:43.250 --> 00:53:45.900
Once that's connected,
then the next level of work is,
00:53:45.900 --> 00:53:49.330
am I using BCS to connect
to backend data source?
00:53:49.330 --> 00:53:52.600
Am I doing power BI stuff that
isn't really US related anymore,
00:53:52.600 --> 00:53:54.200
but it's the same pattern.
00:53:54.200 --> 00:53:58.240
And when you move from 2013 to 2016,
there's a lot of things to check and
00:53:58.240 --> 00:53:59.200
do during the upgrade.
00:53:59.200 --> 00:54:00.880
And we'll have that
heavily documented.
00:54:00.880 --> 00:54:05.150
And there's a lot of hybrid
documentation during an upgrade that
00:54:05.150 --> 00:54:07.110
Bill and
obviously the engineering and
00:54:07.110 --> 00:54:09.220
some of our writers are working on.
00:54:09.220 --> 00:54:12.870
So I don't think the issue is what
you should be concerned about.
00:54:12.870 --> 00:54:15.510
Whether it version x or
y here and there.
00:54:15.510 --> 00:54:18.970
What we support is that
you can accomplish hybrid.
00:54:18.970 --> 00:54:21.290
Some of it is don't worry about
the version in the cloud,
00:54:21.290 --> 00:54:23.648
cuz we don't version it.
00:54:23.648 --> 00:54:27.030
But we're cognizant of what we put
out as far as a hybrid potential,
00:54:27.030 --> 00:54:29.600
is something that would of
course work with 2013 to
00:54:29.600 --> 00:54:31.740
whatever you might
think is in the cloud.
00:54:31.740 --> 00:54:34.380
You should still
think of it as 2013,
00:54:34.380 --> 00:54:36.860
2016 going forward,
especially in the cloud.
00:54:36.860 --> 00:54:40.660
That is the foundation we're
building off of with our intent that
00:54:40.660 --> 00:54:43.960
we don't go through a significant
upgrade in the cloud again.
00:54:43.960 --> 00:54:46.490
>> So, if we stayed on 2013 for
the next five,
00:54:46.490 --> 00:54:48.550
six years-
>> Two years.
00:54:48.550 --> 00:54:50.055
>> We'd be okay?
00:54:50.055 --> 00:54:52.200
[LAUGH] Yeah.
00:54:52.200 --> 00:54:52.730
>> I think so.
00:54:52.730 --> 00:54:57.010
I mean certainly five years from now
Bill Gates could be the CEO again.
00:54:57.010 --> 00:54:57.670
But no.
00:54:57.670 --> 00:55:01.880
The patterns will be there and
00:55:01.880 --> 00:55:05.250
we'll be very transparent about
changes that we're making.
00:55:05.250 --> 00:55:08.880
But in that space you are really
trying to make a connection.
00:55:08.880 --> 00:55:10.980
It's a solid connection
to your AD environments,
00:55:10.980 --> 00:55:12.290
or your user when they get pinged.
00:55:12.290 --> 00:55:13.190
Who are you?
Who are you?
00:55:13.190 --> 00:55:14.020
Who are you?
00:55:14.020 --> 00:55:16.486
It's the same source, so
you're not getting blocked there.
00:55:16.486 --> 00:55:19.820
And then making the connections to
your data sources in a way that,
00:55:19.820 --> 00:55:22.245
again, doesn't break with
what we do in the cloud,
00:55:22.245 --> 00:55:23.750
cuz we know people are doing it.
00:55:23.750 --> 00:55:27.114
And the way that you maintain on
premises I think is just more of
00:55:27.114 --> 00:55:29.504
a you need to know x and
y before you do it, but
00:55:29.504 --> 00:55:31.073
it's not a you can't do it.
00:55:34.835 --> 00:55:35.996
>> Hi.
00:55:35.996 --> 00:55:36.739
Quick question.
00:55:36.739 --> 00:55:40.851
I've got a number of large customers
who've expressed interest recently
00:55:40.851 --> 00:55:43.080
in Access services,
believe it or not.
00:55:43.080 --> 00:55:44.470
>> Okay, yeah.
00:55:44.470 --> 00:55:50.071
My question is will
Access Services still exist in 2016-
00:55:50.071 --> 00:55:50.440
>> Yep.
00:55:50.440 --> 00:55:55.048
>> If it does, has there been
any investment made in it?
00:55:55.048 --> 00:55:57.910
>> Good question.
00:55:57.910 --> 00:56:01.960
One broader statement I'll try
to make and hold true by nature
00:56:01.960 --> 00:56:04.920
of I've got Bill Baer who said
something similar in his sessions or
00:56:04.920 --> 00:56:05.960
if you had asked him.
00:56:05.960 --> 00:56:08.810
And Bill is ten times smarter
than I am when it comes to under
00:56:08.810 --> 00:56:10.010
the cover stuff.
00:56:10.010 --> 00:56:13.822
But nothing is being deprecated from
what you knew as SharePoint 2013
00:56:13.822 --> 00:56:15.060
moving into 2016.
00:56:15.060 --> 00:56:18.890
Only the improvements, or
there may be a little feature.
00:56:18.890 --> 00:56:21.830
And maybe not so little in terms
of how people built on it,
00:56:21.830 --> 00:56:25.170
which we've communicated heavily,
that got deprecated from the cloud.
00:56:25.170 --> 00:56:29.660
And the two that I can land on there
are Tags and Notes and My Tasks.
00:56:29.660 --> 00:56:32.830
Beyond that, those do have
replacements in terms of,
00:56:32.830 --> 00:56:35.680
one we haven't yet talked a lot
about and you'll hear about it.
00:56:35.680 --> 00:56:38.228
Shame on us for kind of pulling
the plug a little early, but
00:56:38.228 --> 00:56:41.244
beyond that, Access service is
there, InfoPath service is there,
00:56:41.244 --> 00:56:42.390
Excel services is there.
00:56:42.390 --> 00:56:44.640
If you're on prem,
Full Trust Code will still work,
00:56:44.640 --> 00:56:46.040
PerformancePoint still there.
00:56:47.390 --> 00:56:48.000
Specifically for
00:56:48.000 --> 00:56:50.800
Access services I don't think there
has been a lot of investment made,
00:56:50.800 --> 00:56:54.050
except for, make sure it works,
make sure it's tested.
00:56:54.050 --> 00:56:56.670
And I think it's indicative of,
00:56:56.670 --> 00:57:01.950
we've been trying to leverage Access
a lot more and we're sort of at that
00:57:01.950 --> 00:57:05.700
crux where we're not quite getting
the developer love for it yet.
00:57:05.700 --> 00:57:08.170
Cuz it just isn't a developer tool,
and
00:57:08.170 --> 00:57:11.620
it maybe isn't quite yet
easy enough for me.
00:57:11.620 --> 00:57:17.000
Again, me representative of somebody
who's not your Laura Rogers or
00:57:17.000 --> 00:57:18.610
Jennifer Mason type folk.
00:57:18.610 --> 00:57:20.660
But that being said,
00:57:20.660 --> 00:57:24.440
I think there is a lot of investment
in that space in the future.
00:57:24.440 --> 00:57:29.290
And that team, I wouldn't be
allowed to say a whole, lot and
00:57:29.290 --> 00:57:32.590
probably not as deep as you'd
want me to answer, confidently.
00:57:32.590 --> 00:57:36.305
But I do think it is an area that
will get a lot more focus, again,
00:57:36.305 --> 00:57:39.080
cuz we're targeting something
that's not your deep developer
00:57:39.080 --> 00:57:41.970
Visual Studio, everybody has
to use that to do everything.
00:57:41.970 --> 00:57:43.810
So, good question,
the main thing is yes,
00:57:43.810 --> 00:57:45.759
it's totally supported
Access services.
00:57:47.270 --> 00:57:51.680
The newest thing from Access 2013
is that the database goes to Azure,
00:57:51.680 --> 00:57:52.400
that doesn't change.
00:57:52.400 --> 00:57:56.150
So again, no real change,
I guess is my easy answer.
00:57:56.150 --> 00:57:56.680
>> Thank you.
00:57:56.680 --> 00:57:57.702
>> You're welcome.
00:57:57.702 --> 00:57:59.110
All right,
whoever gets the mic next,
00:57:59.110 --> 00:58:01.305
it doesn't mean you get the monkey,
it just means I'm flinging it.
00:58:01.305 --> 00:58:04.020
>> [LAUGH]
>> And
00:58:04.020 --> 00:58:06.100
I'm gonna do it
during your question.
00:58:06.100 --> 00:58:07.420
>> Yeah, perfect.
00:58:07.420 --> 00:58:10.260
An additional question to
the hybrid scenarios, yeah?
00:58:10.260 --> 00:58:10.790
>> Okay.
00:58:10.790 --> 00:58:14.150
>> One thing which is nice on hybrid
00:58:14.150 --> 00:58:18.100
scenarios is that you can use
your work wherever they are best.
00:58:18.100 --> 00:58:24.740
But the user experience is
different to on prem and hybrid.
00:58:24.740 --> 00:58:28.620
And when I think about the colleague
here with we say one version behind.
00:58:28.620 --> 00:58:33.560
>> Yep.
>> It can be or it will be a problem
00:58:33.560 --> 00:58:39.440
if users coming to a on prem
solution which acts differently.
00:58:39.440 --> 00:58:40.100
>> Yep.
>> So
00:58:40.100 --> 00:58:46.010
what is your plan about getting
a more consistent user experience
00:58:46.010 --> 00:58:51.540
between on prem and O 365 or
SharePoint online or whatever.
00:58:51.540 --> 00:58:54.382
>> Good question and let's see what
the monkey has to say about that.
00:58:55.913 --> 00:58:59.110
>> [LAUGH]
>> All right next question.
00:58:59.110 --> 00:58:59.809
>> Oh thanks.
00:58:59.809 --> 00:59:02.020
[LAUGH] Good answer.
00:59:02.020 --> 00:59:04.020
[LAUGH]
>> No.
00:59:04.020 --> 00:59:07.610
When we started the journey around
hybrid, the big thing around it was
00:59:07.610 --> 00:59:11.990
there is still a lot that is on
customer or partner to accomplish.
00:59:11.990 --> 00:59:13.970
And so if you connect
these environments and
00:59:13.970 --> 00:59:17.640
you navigate between team sites in
the cloud, and maybe even team sites
00:59:17.640 --> 00:59:20.680
or portals on prem, there is gonna
be a different look and feel.
00:59:20.680 --> 00:59:23.270
And there are things that
you can do about that.
00:59:23.270 --> 00:59:25.200
But certainly that's the onus.
00:59:25.200 --> 00:59:25.930
The second half.
00:59:25.930 --> 00:59:29.380
And so that's, I think,
both design and navigation.
00:59:29.380 --> 00:59:33.080
And I remember one customer we met
with, they were really excited.
00:59:33.080 --> 00:59:34.290
They connected up hybrid search,
00:59:34.290 --> 00:59:36.500
which at the time was
just federated query.
00:59:36.500 --> 00:59:38.370
And search resolved,
and all was good.
00:59:38.370 --> 00:59:41.380
But then they started on their next
level, which was navigation between.
00:59:41.380 --> 00:59:45.440
And I was just listening to
an architect who was like,
00:59:45.440 --> 00:59:49.110
you might wanna put in a link
back to where they came from,
00:59:49.110 --> 00:59:50.010
based on where they landed.
00:59:50.010 --> 00:59:51.520
And, you can't do that
across everything.
00:59:51.520 --> 00:59:53.909
It doesn't make sense on a team site
if you just came from a portal.
00:59:53.909 --> 00:59:58.404
But, maybe it does,
depending on what you keep as your
00:59:58.404 --> 01:00:01.943
master page elements
across more places.
01:00:01.943 --> 01:00:05.122
The other area of that
is as we move to 2016,
01:00:05.122 --> 01:00:09.968
if you upgrade with us there, you're
gonna get some of the user elements
01:00:09.968 --> 01:00:14.030
that came from the Cloud,
where that destination might be.
01:00:14.030 --> 01:00:17.890
So Hybrid and On Prem over
time will be more similar.
01:00:17.890 --> 01:00:21.050
And I think that's strongest
in OneDrive for Business.
01:00:21.050 --> 01:00:23.470
Again, not saying that
that's the name or
01:00:23.470 --> 01:00:27.040
not the name in SharePoint 2016, but
effectively, where you have your
01:00:27.040 --> 01:00:31.810
personal work documents, should look
a lot more like what's in the Cloud.
01:00:31.810 --> 01:00:35.325
And that might not be so
exciting because not everybody does
01:00:35.325 --> 01:00:37.660
a split deployment of OneDrive for
business, but you can.
01:00:37.660 --> 01:00:40.830
But most of the time it's everybody
eventually ends in the Cloud.
01:00:40.830 --> 01:00:42.610
But the same will be true for
team sites.
01:00:42.610 --> 01:00:45.900
So a lot of the innovation we've
done in team sites in the Cloud,
01:00:45.900 --> 01:00:49.120
more around performance and
some around UX tuning, and
01:00:49.120 --> 01:00:51.520
some of the elements
around friendlier UI for
01:00:51.520 --> 01:00:54.060
document libraries will come down.
01:00:54.060 --> 01:00:56.693
So I think there's sort
of a leapfrog effect.
01:00:56.693 --> 01:01:01.548
As you get more years down the road,
hopefully it will become less and
01:01:01.548 --> 01:01:04.654
less disturbing going
from place to place.
01:01:04.654 --> 01:01:06.210
>> What about the app launcher?
01:01:06.210 --> 01:01:07.208
>> The app launcher.
01:01:07.208 --> 01:01:10.690
Oh, I don't know if I got a pay
grade coming out of Ignite.
01:01:10.690 --> 01:01:14.400
So the question down here was will
the app launcher be consistent
01:01:14.400 --> 01:01:15.680
if you're in a hybrid state?
01:01:17.160 --> 01:01:20.460
As far as I know it'll
still be a top navigation.
01:01:20.460 --> 01:01:22.830
Similarly, if you're a 2013 hybrid.
01:01:22.830 --> 01:01:26.250
I'm not aware of plans to
bring the app launcher down.
01:01:26.250 --> 01:01:28.860
But, when we talk about hybrid and
the new elements that come when you
01:01:28.860 --> 01:01:33.680
wire them up, either in 2013 for
Dell, OneDrive and Yammer, or
01:01:33.680 --> 01:01:37.180
in 2016 including video, it's more
of a top navigation element that
01:01:37.180 --> 01:01:40.620
lights up, and
then is wired into the Cloud.
01:01:40.620 --> 01:01:42.140
I don't think there's
an announcement,
01:01:42.140 --> 01:01:45.729
I don't think I'm breaking anything,
but that's my awareness.
01:01:47.550 --> 01:01:49.010
>> Hello.
01:01:49.010 --> 01:01:50.560
>> Take here, and
then back in the front.
01:01:50.560 --> 01:01:55.260
>> Yeah, so thanks for this
session here and taking questions, but-
01:01:55.260 --> 01:01:55.542
>> You're welcome.
01:01:55.542 --> 01:02:00.547
>> So, I have clients who
are pretty hesitant about moving
01:02:00.547 --> 01:02:06.407
beyond the base level threshold
guidances in SharePoint because
01:02:06.407 --> 01:02:11.734
they operate their SharePoint
farms as a shared service for
01:02:11.734 --> 01:02:15.075
all the various people who use this.
01:02:15.075 --> 01:02:17.955
They don't want to bog it down if
they extend thresholds too far.
01:02:17.955 --> 01:02:23.659
So they've stayed with the base 50
megabytes default file threshold,
01:02:23.659 --> 01:02:25.501
which can be a problem.
01:02:25.501 --> 01:02:28.791
So when you're expanding
thresholds like this,
01:02:28.791 --> 01:02:33.177
we talked about the ultimate file
size and maybe list thresholds,
01:02:33.177 --> 01:02:34.997
that 5000 item limit.
01:02:34.997 --> 01:02:35.860
>> Yep.
01:02:35.860 --> 01:02:41.510
>> Is there any new guidance or
base level recommendations for
01:02:41.510 --> 01:02:46.450
that, that would affect
clients like this, in terms
01:02:46.450 --> 01:02:49.620
of scaling because yeah sure it can
go all the way up to that level.
01:02:49.620 --> 01:02:51.624
But, is it really
what's recommended and
01:02:51.624 --> 01:02:54.461
are we going to have clients who
are going to be uncomfortable
01:02:54.461 --> 01:02:56.978
moving down that base
recommendation to something?
01:02:56.978 --> 01:03:01.082
>> Yeah it's actually I think one
of the slides that Bill showed and
01:03:01.082 --> 01:03:05.414
some of it is, if you go to 2016
all the limits that have gone up,
01:03:05.414 --> 01:03:07.100
so, there's that view.
01:03:07.100 --> 01:03:09.960
If they move to 2016 then it
does change the conversation.
01:03:09.960 --> 01:03:12.310
There's a lot of scale
improvements and
01:03:12.310 --> 01:03:17.488
I'll just land on the 5,000 view
limit is completely resolved.
01:03:17.488 --> 01:03:20.840
Maybe not completely, I won't say
millions and millions of things but,
01:03:20.840 --> 01:03:23.750
certainly way above what
is considered an issue.
01:03:23.750 --> 01:03:27.820
There's also just your basic
site collection type limits.
01:03:27.820 --> 01:03:29.790
How many sites in a site collection,
those types of things,
01:03:29.790 --> 01:03:31.050
everything does go up.
01:03:31.050 --> 01:03:34.870
I'll just refer, if you go
to Bill's on demand session,
01:03:34.870 --> 01:03:38.610
there a nice section where he has
four boxes of not exact numbers.
01:03:38.610 --> 01:03:40.652
We're working on what those
final numbers will be.
01:03:40.652 --> 01:03:45.390
But definitely introducing this
idea of yes we've heard plenty.
01:03:45.390 --> 01:03:49.090
There was also a lot of work in 2013
where they went back and retested
01:03:49.090 --> 01:03:52.640
a bunch of stuff, at a scale
that was kind of off the charts,
01:03:52.640 --> 01:03:54.650
based on when they did
their original testing.
01:03:54.650 --> 01:03:56.450
It doesn't mean the original
testing wasn't good and
01:03:56.450 --> 01:03:59.580
it might have been where they
kind of hit the initial baseline.
01:03:59.580 --> 01:04:02.100
But a guy that used to be
on the SharePoint team,
01:04:02.100 --> 01:04:06.420
a guy name Paul Andrew, he's now on
the Office 365 team, headed that.
01:04:06.420 --> 01:04:09.840
And he's kind of your deep,
let's get it right, and if there's
01:04:09.840 --> 01:04:13.205
better numbers to publish, let's
prove it and then put it out there.
01:04:13.205 --> 01:04:16.100
And I think it's just
the SharePoint boundaries and
01:04:16.100 --> 01:04:18.050
limits article on TechNet.
01:04:18.050 --> 01:04:19.670
There's a similar one for
SharePoint Online.
01:04:19.670 --> 01:04:22.060
And those will get refreshed and
updated.
01:04:22.060 --> 01:04:22.760
And again,
01:04:22.760 --> 01:04:26.170
if they haven't look recently,
our supported guidance is there.
01:04:26.170 --> 01:04:27.380
Hard numbers.
01:04:27.380 --> 01:04:31.290
Some of them pretty large, some of
them limiting, but to be improved.
01:04:31.290 --> 01:04:32.970
And all the work we're
doing in SharePoint online,
01:04:32.970 --> 01:04:36.220
again accrues back to
the SharePoint 2016 footprint.
01:04:36.220 --> 01:04:39.380
So they'll cover some big
ones to get the applause, but
01:04:39.380 --> 01:04:41.560
there's a lot of work.
01:04:41.560 --> 01:04:44.580
In the online world, today we
support up to one terabyte site
01:04:44.580 --> 01:04:48.300
collections, and
people use them big time.
01:04:48.300 --> 01:04:51.660
We've got one customer coming in
who has 120 terabytes of data and
01:04:51.660 --> 01:04:54.550
has not a single tenant on
the multi tenant space.
01:04:54.550 --> 01:04:58.170
They are within
everybody that's there.
01:04:59.300 --> 01:05:01.900
Those types of things, we don't
want to have those limits anymore.
01:05:01.900 --> 01:05:03.460
So a lot of work is being
done to remove them.
01:05:03.460 --> 01:05:06.670
And that's why I've got this one
line, where there's a whole team
01:05:06.670 --> 01:05:09.460
that's focused on the online
infrastructure, and
01:05:09.460 --> 01:05:11.208
it's their code you're
getting on PREM.
01:05:11.208 --> 01:05:14.250
So, there's a lot of
innovation there.
01:05:14.250 --> 01:05:17.646
I think the answer is no, and
certainly no in 2016 in a big way.
01:05:17.646 --> 01:05:19.581
Good question.
01:05:19.581 --> 01:05:20.228
Yeah?
01:05:20.228 --> 01:05:22.320
>> [INAUDIBLE].
01:05:22.320 --> 01:05:22.845
>> I'll repeat it.
01:05:22.845 --> 01:05:30.226
>> [INAUDIBLE]
>> Yep.
01:05:30.226 --> 01:05:34.450
>> [INAUDIBLE]
>> Yep, so
01:05:34.450 --> 01:05:38.720
the question was if you are using
some of the innovation around using
01:05:38.720 --> 01:05:43.280
the office graph API's or just maybe
some of the next gen portals that
01:05:43.280 --> 01:05:46.790
we're putting out, he was curious
on where do those pages live.
01:05:46.790 --> 01:05:49.010
And currently they're in SharePoint,
because that's where they should be.
01:05:49.010 --> 01:05:51.470
But they're done in a way
that's a lot less bound
01:05:51.470 --> 01:05:55.250
to the publish infrastructure,
common around leveraging portals.
01:05:55.250 --> 01:06:00.010
So the mantra used to be for pages,
they have to be simple, they have to
01:06:00.010 --> 01:06:03.840
be fast and maybe they don't have to
be built at all, you just get them.
01:06:03.840 --> 01:06:05.490
But certainly those
patterns will accrue so
01:06:05.490 --> 01:06:07.670
that people could build
their own pages in that way.
01:06:07.670 --> 01:06:11.800
How that will change is just the
fact that, yeah, it might change.
01:06:11.800 --> 01:06:13.760
Because there might be better
ways to accomplish it,
01:06:13.760 --> 01:06:15.450
and we don't want to hang so
01:06:15.450 --> 01:06:18.150
many deep hooks into SharePoint
where it just doesn't make sense.
01:06:18.150 --> 01:06:21.240
And the front end is
one of them that maybe,
01:06:21.240 --> 01:06:24.690
I don't know if I'll get the quote
just right, but Daniel Cogan,
01:06:24.690 --> 01:06:28.370
who's one of our main next
gen portals engineers at
01:06:28.370 --> 01:06:31.940
a relatively senior level, and he's
got support all the way through.
01:06:31.940 --> 01:06:34.620
Our kind of new Jeff Teper,
a guy named Phil Smoot who,
01:06:34.620 --> 01:06:38.200
if you saw him here, he was kind of
new into role about two months, so
01:06:38.200 --> 01:06:39.820
he didn't come up on stage.
01:06:39.820 --> 01:06:41.330
But anyway,
we've got a new Jeff Teper,
01:06:41.330 --> 01:06:44.130
who's got a lot of interesting ways
that he wants to support his team to
01:06:44.130 --> 01:06:45.760
go and do what they need to do.
01:06:45.760 --> 01:06:48.780
Don't be bound to
what they had to do.
01:06:48.780 --> 01:06:51.280
And one of the areas is
what you do on the front
01:06:51.280 --> 01:06:56.120
end may be something that at some
point in time put into GitHub, and
01:06:56.120 --> 01:07:00.300
we may do some open
source type activities.
01:07:00.300 --> 01:07:04.500
Nothing to announce clearly,
but they are thinking of that.
01:07:04.500 --> 01:07:06.850
Maybe we don't just want to own
the front end because we want to own
01:07:06.850 --> 01:07:09.350
the rest points to get to the data
that's on the back end and
01:07:09.350 --> 01:07:12.150
be, of course,
the service of choice.
01:07:12.150 --> 01:07:13.920
So that's kind of the today answer.
01:07:13.920 --> 01:07:16.590
The tomorrow answer may just be
dictated by what's the best pattern
01:07:16.590 --> 01:07:19.534
we can follow and
certainly prescribe after that.
01:07:19.534 --> 01:07:20.210
And whatever he said.
01:07:20.210 --> 01:07:25.341
All right, here and
then in the back.
01:07:25.341 --> 01:07:26.641
>> Super Powershell question.
01:07:26.641 --> 01:07:27.732
>> Powershell, uh-huh.
01:07:27.732 --> 01:07:33.080
>> Any planned support to
get content from On Prem,
01:07:33.080 --> 01:07:39.300
SharePoint to the Cloud at
the site library file level?
01:07:39.300 --> 01:07:42.160
And then once that content's on
there to be able to manage that
01:07:42.160 --> 01:07:46.200
content via Powershell check-in
checkouts and moves and so on.
01:07:46.200 --> 01:07:48.990
>> Yeah, from a Powershell and
really an API perspective,
01:07:48.990 --> 01:07:52.770
we support in the cloud everything
from the tenant level down.
01:07:52.770 --> 01:07:55.350
But specifically the content
is everything you can do
01:07:55.350 --> 01:07:57.230
within a site collection down.
01:07:57.230 --> 01:07:59.770
And there's a lot of motions
around how to get content into
01:07:59.770 --> 01:08:00.530
the Cloud, and
01:08:00.530 --> 01:08:05.660
certainly we are supported greatly
by a third party from a MassMotion.
01:08:05.660 --> 01:08:07.370
But what they introduced
at the conference, and
01:08:07.370 --> 01:08:09.110
I should have listed it because
it was pretty important,
01:08:09.110 --> 01:08:11.350
but it really was just
a part of a session,
01:08:11.350 --> 01:08:13.208
was we now have a new Migration API.
01:08:13.208 --> 01:08:17.360
That makes it so that at least
you're more reliable in how you talk
01:08:17.360 --> 01:08:23.500
to our service, and it really routes
it to an Azure temporary store.
01:08:23.500 --> 01:08:25.190
To then go around the front end so
01:08:25.190 --> 01:08:27.680
that it sneaks into the back
end a lot more performantly.
01:08:27.680 --> 01:08:31.389
Meaning, when someone migrates to
the Cloud they're not tanking other
01:08:31.389 --> 01:08:31.947
tenants.
01:08:31.947 --> 01:08:33.363
>> And that was one of
the sessions on your list?
01:08:33.363 --> 01:08:34.424
>> Yeah, there's one and
01:08:34.424 --> 01:08:37.652
it's not too hard to find if you
just do SharePoint migration.
01:08:37.652 --> 01:08:42.420
The guy you want to listen for,
his name is Simon Bradoges.
01:08:42.420 --> 01:08:45.760
He's, I think mostly Russian, so
01:08:45.760 --> 01:08:48.660
I might have gotten
his last name wrong.
01:08:48.660 --> 01:08:52.580
But they kind of show the real
world of getting content in and
01:08:52.580 --> 01:08:54.740
certainly just introducing
the new migration API.
01:08:54.740 --> 01:08:56.918
Primarily, these days,
it's working with our ISV's.
01:08:56.918 --> 01:08:59.490
So, they stopped using
our web services,
01:08:59.490 --> 01:09:01.520
that are completely supported.
01:09:01.520 --> 01:09:05.170
But when they start a migration, our
guys on the infrastructure team know
01:09:05.170 --> 01:09:08.060
it, sometimes, and it is impacting.
01:09:08.060 --> 01:09:11.600
So, we sometimes have to throttle
and that's not the best way we want
01:09:11.600 --> 01:09:14.690
to treat them or, ultimately,
our customers through them.
01:09:14.690 --> 01:09:17.930
So introducing this new API will be
good for ISVs, we think good for
01:09:17.930 --> 01:09:21.720
business units and there's some work
that the FastTrack team is doing,
01:09:21.720 --> 01:09:24.470
which is a service
that we provide for
01:09:24.470 --> 01:09:27.760
our customers when they first
onboard into Office 365.
01:09:27.760 --> 01:09:30.770
Primarily that team is
focused on mailbox migration.
01:09:30.770 --> 01:09:32.793
And they're starting
to work through,
01:09:32.793 --> 01:09:35.239
a gentleman if you know
him his name is Kymo Fors.
01:09:35.239 --> 01:09:38.605
Kymo is really trying to launch,
through FastTrack,
01:09:38.605 --> 01:09:41.250
a better way to get
content into the Cloud.
01:09:41.250 --> 01:09:43.020
And, to be honest,
they're doing it for
01:09:43.020 --> 01:09:48.160
one of our internal portals to get
content out more successfully.
01:09:48.160 --> 01:09:51.415
Once it's in, it should be
pretty straight forward.
01:09:51.415 --> 01:09:55.285
Powershell, activities, or again, if
you want to more develop a solution
01:09:55.285 --> 01:09:57.471
that's either leveraging that or
other.
01:09:57.471 --> 01:10:01.701
We have been transparent and
open about the files API And
01:10:01.701 --> 01:10:03.231
how to leverage it.
01:10:03.231 --> 01:10:06.110
And I'll stop there,
because I'm not your PowerShell guy.
01:10:06.110 --> 01:10:09.243
But, that's, everything is a yes.
01:10:09.243 --> 01:10:11.588
It's a matter of how and
01:10:11.588 --> 01:10:17.150
there's lots of good places
to go to get docs for that.
01:10:17.150 --> 01:10:17.970
>> Great. Thanks. >> Cool.
01:10:17.970 --> 01:10:18.470
>> [INAUDIBLE]
>> Okay.
01:10:18.470 --> 01:10:19.210
Yeah, and Kimo, I think at
01:10:19.210 --> 01:10:21.520
the conference,
was talking about how he might share
01:10:21.520 --> 01:10:24.150
some of the things that he's working
on to accelerate what you're doing.
01:10:24.150 --> 01:10:25.435
So he's in the back, next.
01:10:25.435 --> 01:10:26.185
>> [INAUDIBLE]
01:10:26.185 --> 01:10:27.400
>> [INAUDIBLE] In one the sessions
01:10:27.400 --> 01:10:30.310
we heard the demo is going away.
01:10:30.310 --> 01:10:32.280
>> Fem yep.
>> In terms of two way export.
01:10:32.280 --> 01:10:36.364
But I didn't hear sort of
a path to either replace fem or
01:10:36.364 --> 01:10:41.170
[INAUDIBLE] vendor product that
you're looking for the add on after.
01:10:41.170 --> 01:10:48.860
Because we do some bidirectional
sync work now [INAUDIBLE].
01:10:48.860 --> 01:10:51.458
>> I will claim that I don't know.
01:10:51.458 --> 01:10:55.960
I do know that the identity team who
owns kind of the thin V-necks or
01:10:55.960 --> 01:10:58.420
whatever we're doing in the cloud.
01:10:58.420 --> 01:11:01.950
The ultimate owner is
the Azure AD team.
01:11:01.950 --> 01:11:04.530
They are the ones that
are driving to factor off.
01:11:04.530 --> 01:11:07.102
They're driving obviously the store
and the connection to when you
01:11:07.102 --> 01:11:10.140
dirsync and the replacement
that is coming for dirsync.
01:11:10.140 --> 01:11:13.750
So I have to lean on if you
send that same question to me
01:11:13.750 --> 01:11:15.930
I'll make sure to loop
in the right folks.
01:11:15.930 --> 01:11:19.080
I know that they're changing
things significantly and
01:11:19.080 --> 01:11:23.247
it's primarily for the better, but
I don't know much more than that.
01:11:23.247 --> 01:11:25.950
>> Two short questions.
01:11:25.950 --> 01:11:30.340
Will you support metadata syncing
for OneDrive for Business?
01:11:30.340 --> 01:11:34.800
Second question, will you
support proxy server support for
01:11:34.800 --> 01:11:38.050
web applications that they can
easily connect to the Internet.
01:11:38.050 --> 01:11:39.630
>> The first one I know more about.
01:11:39.630 --> 01:11:43.740
I believe in the sync
session that Jason Moore led.
01:11:43.740 --> 01:11:47.280
I don't think they have
a hard date that they've set.
01:11:47.280 --> 01:11:48.540
But it's certainly a lot of feedback
01:11:48.540 --> 01:11:50.970
that they're trying to
land on their road map.
01:11:50.970 --> 01:11:55.060
Is to be able to have content
that comes from and lands in.
01:11:55.060 --> 01:11:56.860
Have more metadata intact.
01:11:56.860 --> 01:11:58.820
Especially from
a syncing perspective.
01:11:58.820 --> 01:12:00.930
But also migration perspective.
01:12:00.930 --> 01:12:03.740
The second one I don't
think I know the answer.
01:12:03.740 --> 01:12:07.740
I think that's more in
the developer realm.
01:12:07.740 --> 01:12:10.610
I wouldn't want to lead you astray.
01:12:10.610 --> 01:12:12.462
I can get to the answer
pretty quickly, but
01:12:12.462 --> 01:12:14.530
I don't think I know it
off of the top of my head.
01:12:14.530 --> 01:12:15.700
>> Great, thanks.
01:12:15.700 --> 01:12:17.820
>> Yep.
01:12:17.820 --> 01:12:19.110
>> Two questions.
01:12:19.110 --> 01:12:23.528
What is the,
01:12:23.528 --> 01:12:27.950
[INAUDIBLE].
01:12:27.950 --> 01:12:30.793
>> So the question is, are there
going to be any services in
01:12:30.793 --> 01:12:34.607
SharePoint 2016, that aren't
available in SharePoint Online, and
01:12:34.607 --> 01:12:38.358
the easy answer is, if they aren't
today, they won't be tomorrow, and
01:12:38.358 --> 01:12:41.950
the big ones again are Performance
Point, is not moving to the cloud.
01:12:41.950 --> 01:12:46.883
But again, we think we have a pretty
good solution there around power BI
01:12:46.883 --> 01:12:50.530
and the way that their
direction are going.
01:12:50.530 --> 01:12:53.372
There's some motion around social,
which maybe not quite what you're
01:12:53.372 --> 01:12:56.540
asking, but I'll kind of cut it
off at the knees if it was there.
01:12:56.540 --> 01:12:57.610
Social isn't going away.
01:12:57.610 --> 01:12:59.460
Certainly the same motion around.
01:12:59.460 --> 01:13:00.760
We're not deprecating.
01:13:00.760 --> 01:13:04.860
But from a go forward pattern,
it's Yammer.
01:13:04.860 --> 01:13:08.000
And so there's a lot of around how
do we connect better to Yammer.
01:13:08.000 --> 01:13:11.060
And I think that will be
iterative after 2016 ships
01:13:11.060 --> 01:13:14.740
just from the nature of
where things are at.
01:13:14.740 --> 01:13:17.200
Full trust code isn't
necessarily a service per se but
01:13:17.200 --> 01:13:20.060
that same thing is true.
01:13:20.060 --> 01:13:22.360
And then the last thing,
which again is not a services,
01:13:22.360 --> 01:13:25.760
anything you have control over
in central administration, we're
01:13:25.760 --> 01:13:28.710
trying to give you more and more
access to, to control and manage.
01:13:28.710 --> 01:13:30.800
But the first things that we're
doing is really opening it
01:13:30.800 --> 01:13:31.560
up per service.
01:13:31.560 --> 01:13:34.970
So if we turn on Delve, it's not
anything you can do on Prim, but it
01:13:34.970 --> 01:13:38.050
is something we wanna make sure you
have the right things to turn it on.
01:13:38.050 --> 01:13:39.190
Obviously, it'll be on by default.
01:13:39.190 --> 01:13:40.370
You can turn it off and
01:13:40.370 --> 01:13:43.030
then different levels of how you
can manage it and control it.
01:13:43.030 --> 01:13:47.690
But, outside of that, what is true
today doesn't change with 2016.
01:13:47.690 --> 01:13:51.610
But there are some things
that aren't coming still.
01:13:51.610 --> 01:13:54.840
And usually it's because there are
other teams that are providing it.
01:13:57.252 --> 01:14:02.789
[INAUDIBLE]
>> Mm-hm
01:14:02.789 --> 01:14:06.577
>> [INAUDIBLE]
01:14:06.577 --> 01:14:07.452
>> Yep
01:14:07.452 --> 01:14:11.240
>> [INAUDIBLE]
01:14:11.240 --> 01:14:12.115
>> Yep
01:14:12.115 --> 01:14:16.780
>> What would you say [INAUDIBLE].
01:14:21.130 --> 01:14:24.850
>> So our first reference we had a
nice session with Richard Harbridge
01:14:24.850 --> 01:14:27.500
and Conwall Kippell who gave
a really nice perspective,
01:14:27.500 --> 01:14:30.110
not a Microsoft perspective, even
though we sort of reviewed their
01:14:30.110 --> 01:14:32.390
session we didn't
dictate the session.
01:14:32.390 --> 01:14:35.450
And there's a lot of awareness
around really what is Office
01:14:35.450 --> 01:14:35.960
365 Groups.
01:14:35.960 --> 01:14:38.020
Not that that's my answer,
01:14:38.020 --> 01:14:40.519
but there is more material
than what my answer will be.
01:14:41.560 --> 01:14:44.340
A big thing around team and
groups is, if you've done
01:14:44.340 --> 01:14:48.590
anything in a team site, it's not
a rush over and move it into groups.
01:14:49.960 --> 01:14:50.500
It just isn't.
01:14:50.500 --> 01:14:52.700
They aren't the same.
01:14:52.700 --> 01:14:53.980
If you have a new need for
01:14:53.980 --> 01:14:56.570
a team, certainly review
what are the requirements.
01:14:56.570 --> 01:14:58.720
If it's lightweight conversation,
01:14:58.720 --> 01:15:00.650
storage of files in
a shared calendar.
01:15:00.650 --> 01:15:02.050
Groups is gonna do that really well.
01:15:02.050 --> 01:15:04.230
And they're designing it
to do that really well.
01:15:04.230 --> 01:15:06.880
And it's built around the ten
people that you pulled together.
01:15:06.880 --> 01:15:09.040
Not the site that you created,
and you invite people in and
01:15:09.040 --> 01:15:10.720
you have to go through
a lot of hurdles.
01:15:10.720 --> 01:15:14.700
But the other area where a team
site usually isn't going away is
01:15:14.700 --> 01:15:16.760
if you customize a team site.
01:15:16.760 --> 01:15:19.390
Whether that's something
like what you were asking,
01:15:19.390 --> 01:15:22.190
around a drop folder, or
just some level of customization.
01:15:22.190 --> 01:15:23.660
Or a business application that
01:15:23.660 --> 01:15:25.200
just happened to use
a team site template.
01:15:25.200 --> 01:15:27.020
Or maybe it was a full blown portal.
01:15:28.380 --> 01:15:31.090
Groups is not trying to be that.
01:15:31.090 --> 01:15:34.490
They certainly have APIs,
which will be helpful and useful.
01:15:34.490 --> 01:15:38.780
But it's not intended to go that
direction, so if you have a team set
01:15:38.780 --> 01:15:42.210
on premises, moving it to online,
don't migrate to groups.
01:15:42.210 --> 01:15:44.260
But if it's important,
migrate is a team set.
01:15:44.260 --> 01:15:46.130
There's no harm in that.
01:15:46.130 --> 01:15:49.940
But the group's paradigm is really
an active directory construct and
01:15:49.940 --> 01:15:52.840
I'm just repeating
what our messaging
01:15:52.840 --> 01:15:55.000
seems to be landing more clearly.
01:15:55.000 --> 01:15:57.230
That when I have a group
of ten people and
01:15:57.230 --> 01:16:00.090
I enable a next level of
functionality in groups like we
01:16:00.090 --> 01:16:03.200
start using the calendar,
it just works for everybody.
01:16:03.200 --> 01:16:05.740
If I put a file into cuz
I started the file and
01:16:05.740 --> 01:16:07.440
we all started to collaborate on it.
01:16:07.440 --> 01:16:10.910
And then I walk away, I leave
the company, I get cancelled or what
01:16:10.910 --> 01:16:15.340
not, the file is not mine and people
have just a fine time with it.
01:16:15.340 --> 01:16:18.230
And so Groups is really
trying to tackle that but
01:16:18.230 --> 01:16:22.090
they're not replacing Team and I
think actually you'll see an element
01:16:22.090 --> 01:16:23.680
of Team that comes to groups.
01:16:23.680 --> 01:16:25.618
Same as,
might be kind of weird to hear,
01:16:25.618 --> 01:16:28.360
there's an element of Yammer
that's coming to groups.
01:16:28.360 --> 01:16:31.755
I think that will make more sense
when you actually see it or
01:16:31.755 --> 01:16:34.820
if you listen to a talk that
Christoph Eisinger did.
01:16:34.820 --> 01:16:38.646
He's the one that's really
providing a ton of clarity
01:16:38.646 --> 01:16:43.150
around what groups is because we
got off to a little rocky start.
01:16:43.150 --> 01:16:45.940
I'll kind of talk this up but I need
everybody to stand up for a second.
01:16:45.940 --> 01:16:46.980
Don't leave but stand up.
01:16:48.760 --> 01:16:51.780
What I have here unfortunately
is going to be not a size
01:16:51.780 --> 01:16:52.840
for everybody.
01:16:52.840 --> 01:16:55.590
But it is from the original
engineering team for
01:16:55.590 --> 01:16:59.528
SharePoint portal server 2001.
01:16:59.528 --> 01:17:02.606
>> [APPLAUSE]
>> Yeah.
01:17:02.606 --> 01:17:04.670
And I have to go on honesty.
01:17:04.670 --> 01:17:05.960
And I know a lot of
your know each other.
01:17:05.960 --> 01:17:08.890
So if you see anybody
who is telling me a lie,
01:17:08.890 --> 01:17:11.780
then we'll kick him in the rear and
move on to the next.
01:17:11.780 --> 01:17:14.390
I don't know if this is
the best way to give it up but,
01:17:14.390 --> 01:17:18.120
certainly if you've been with
SharePoint since 2013 or
01:17:18.120 --> 01:17:20.250
using SharePoint online
just keep standing.
01:17:21.250 --> 01:17:23.570
If you've been with us
since SharePoint 2010, so
01:17:23.570 --> 01:17:25.990
if you haven't you gotta sit down,
so
01:17:25.990 --> 01:17:30.957
if 2013 was sorta the first
time you came into SharePoint.
01:17:30.957 --> 01:17:37.032
2010, 2007, remember going for
honesty here.
01:17:37.032 --> 01:17:39.250
>> [LAUGH]
>> 2003,
01:17:39.250 --> 01:17:42.440
oh little in and out a little bit.
01:17:44.350 --> 01:17:45.780
So obviously we're down to 2001,
01:17:45.780 --> 01:17:47.720
there's a lot of
people standing here.
01:17:47.720 --> 01:17:49.180
So I just am going to ask.
01:17:49.180 --> 01:17:50.630
And it's the first person
who raises their hand.
01:17:50.630 --> 01:17:52.240
You can't raise it right away.
01:17:52.240 --> 01:17:55.654
But I want to know what your
first project was on 2001 and
01:17:55.654 --> 01:17:57.862
you're willing to share that story.
01:17:57.862 --> 01:18:03.400
>> [INAUDIBLE]
>> And how did it go?
01:18:03.400 --> 01:18:07.987
>> [INAUDIBLE]
>> [LAUGH] See,
01:18:07.987 --> 01:18:11.575
you're not that far behind 2003.
01:18:11.575 --> 01:18:13.660
Well, thanks for
continuing on our journey.
01:18:13.660 --> 01:18:15.850
I don't think this is
directly from Jeff Teper but
01:18:15.850 --> 01:18:20.427
this is from his era so
kind of a fun one to give away.
01:18:20.427 --> 01:18:26.880
[APPLAUSE]
>> So the one thing I'll say just to
01:18:26.880 --> 01:18:30.700
close out primarily because we all
have places to go, and this blinking
01:18:30.700 --> 01:18:33.290
light, and people in the back
want to get out of here as well.
01:18:33.290 --> 01:18:37.390
As the conversation continues
beyond Ignite there will be
01:18:37.390 --> 01:18:39.070
other big events.
01:18:39.070 --> 01:18:41.870
Whether we drive them or
they are third party
01:18:41.870 --> 01:18:45.220
very SharePoint oriented ones or
very broad like here at Ignite.
01:18:45.220 --> 01:18:49.420
But I also encourage you to get
involved in the Office 365 network.
01:18:49.420 --> 01:18:51.500
Not just because it's cool and
it's on Yammer and
01:18:51.500 --> 01:18:55.170
all that but, the engineering
is super clued into that.
01:18:55.170 --> 01:18:56.900
If you have something that's
more of a feature request
01:18:56.900 --> 01:18:59.420
I'd encourage you to look for
the right user voice.
01:18:59.420 --> 01:19:02.280
They're absolutely gold on looking
at that and making sure that we're
01:19:02.280 --> 01:19:06.880
removing more and more blockers or
perceptive and value things.
01:19:06.880 --> 01:19:11.950
But, if I can speak specifically
we created a new next gen portals
01:19:11.950 --> 01:19:14.140
group within the Office 365 network.
01:19:14.140 --> 01:19:15.250
Because that's the team I work with.
01:19:15.250 --> 01:19:18.300
And we just sort of put
all our team in there.
01:19:18.300 --> 01:19:21.100
And obviously just starting to
announce some of the things and
01:19:21.100 --> 01:19:22.450
we'll get active there.
01:19:22.450 --> 01:19:25.790
But the one we had open for Office
365 video has been very active.
01:19:25.790 --> 01:19:28.510
The one that they have for
OneDrive is super active.
01:19:28.510 --> 01:19:32.360
So our intent is keep
pushing us them.
01:19:32.360 --> 01:19:36.600
We'll push back sometimes and
clarify and what not, but for
01:19:36.600 --> 01:19:39.750
us Ignite continues, and
hopefully that resonates.
01:19:39.750 --> 01:19:42.880
But there are real places to
land that get real attention.
01:19:42.880 --> 01:19:45.520
And definitely use them
if you haven't already.
01:19:45.520 --> 01:19:47.460
But with that, thank you,
certainly, for a great week.
01:19:47.460 --> 01:19:48.775
And stay until the end.
01:19:48.775 --> 01:19:51.280
[APPLAUSE]