WEBVTT
Kind: captions
Language: en
00:00:00.320 --> 00:00:02.629
Hello everyone. Welcome to this week's
00:00:02.639 --> 00:00:06.309
episode of the 365 message center show.
00:00:06.319 --> 00:00:07.590
Even though Microsoft's trying to get
00:00:07.600 --> 00:00:10.549
rid of the 365 part everywhere,
00:00:10.559 --> 00:00:12.230
on this show we have quite a few
00:00:12.240 --> 00:00:16.230
messages. One is about how you can pay
00:00:16.240 --> 00:00:18.230
more for one drive. Everybody wants to
00:00:18.240 --> 00:00:19.670
do that, right?
00:00:19.680 --> 00:00:22.310
>> Yeah. Yeah. Um uh the other headline is
00:00:22.320 --> 00:00:25.349
of course the bringing of this new super
00:00:25.359 --> 00:00:30.310
app which is all about co-pilot co-work
00:00:30.320 --> 00:00:33.270
auto something it's all together. Yeah.
00:00:33.280 --> 00:00:35.590
Um we'll talk about that
00:00:35.600 --> 00:00:39.510
>> and we're going to cover HTML because
00:00:39.520 --> 00:00:41.670
who doesn't love a little bit of HTML?
00:00:41.680 --> 00:00:44.150
Well, SharePoint does or we're going to
00:00:44.160 --> 00:00:47.910
see t-shirts with SharePoint heart HTML.
00:00:47.920 --> 00:00:50.310
That and more. Stick around. Roll the
00:00:50.320 --> 00:01:03.430
intro.
00:01:03.440 --> 00:01:05.830
>> Why not? That would be great. Um, it's
00:01:05.840 --> 00:01:07.910
We love Linux, we love this, we love
00:01:07.920 --> 00:01:10.870
that. We love old school HTML.
00:01:10.880 --> 00:01:13.109
>> Yeah. So, we're going to cover that.
00:01:13.119 --> 00:01:16.070
Stick around because it's going to be
00:01:16.080 --> 00:01:18.390
toward the end of our show. uh we're
00:01:18.400 --> 00:01:20.950
going to talk about that. But as we talk
00:01:20.960 --> 00:01:24.230
about these messages, please jump into
00:01:24.240 --> 00:01:26.070
the comments if you're on YouTube and
00:01:26.080 --> 00:01:28.070
just leave your comment. We love we love
00:01:28.080 --> 00:01:30.390
reading those, interacting. If you're
00:01:30.400 --> 00:01:32.469
listening on the audio, you're out
00:01:32.479 --> 00:01:35.190
running, uh you're on the train
00:01:35.200 --> 00:01:37.830
listening, whatever. Hit us up on all
00:01:37.840 --> 00:01:40.630
the socials that matter, 365MCS,
00:01:40.640 --> 00:01:43.749
and and you know, type along. Say, "Oh,
00:01:43.759 --> 00:01:45.590
I liked what you said about that, Darl."
00:01:45.600 --> 00:01:48.710
Or Daniel, you are an idiot. Uh, sure,
00:01:48.720 --> 00:01:49.910
go ahead. Fine. Whatever.
00:01:49.920 --> 00:01:51.350
>> Do you do that though, Daniel? Like, do
00:01:51.360 --> 00:01:53.749
you listen to like a video podcast on
00:01:53.759 --> 00:01:55.749
YouTube or something and pause and go,
00:01:55.759 --> 00:01:57.190
I'm I'm going to jump in the comments
00:01:57.200 --> 00:01:59.749
right here. Time code. Here's what I've
00:01:59.759 --> 00:02:01.590
got to say. Do you do that
00:02:01.600 --> 00:02:02.950
>> every once in a while? If it's something
00:02:02.960 --> 00:02:05.510
that's like really
00:02:05.520 --> 00:02:07.350
>> uh if I want to be helpful.
00:02:07.360 --> 00:02:07.910
>> Yeah.
00:02:07.920 --> 00:02:09.190
>> You know, because if I'm making a
00:02:09.200 --> 00:02:10.710
comment about something that said,
00:02:10.720 --> 00:02:12.070
wouldn't it be great if there was a time
00:02:12.080 --> 00:02:13.990
code in there? I mean, but you can type
00:02:14.000 --> 00:02:15.030
it the time code, right?
00:02:15.040 --> 00:02:17.350
>> Oh, of course. Of course. Yeah. Just I I
00:02:17.360 --> 00:02:19.350
find it's funny when I do that sometimes
00:02:19.360 --> 00:02:21.750
and and I'm having a reaction or a
00:02:21.760 --> 00:02:23.990
thought or an idea and I share that and
00:02:24.000 --> 00:02:25.830
then I continue listening to the video
00:02:25.840 --> 00:02:27.510
or the podcast. Oh, they actually talk
00:02:27.520 --> 00:02:29.110
about this later. So,
00:02:29.120 --> 00:02:30.150
>> I look like a fool. But that's all
00:02:30.160 --> 00:02:32.309
right. I'll just leave it there cuz I
00:02:32.319 --> 00:02:32.949
am. So,
00:02:32.959 --> 00:02:34.710
>> yes, that's fine. Let's jump into it and
00:02:34.720 --> 00:02:37.589
let's get to these messages and tell all
00:02:37.599 --> 00:02:39.670
the peeps how Microsoft's just changing
00:02:39.680 --> 00:02:41.030
their world.
00:02:41.040 --> 00:02:43.110
>> Why not?
00:02:43.120 --> 00:02:44.470
First up,
00:02:44.480 --> 00:02:48.550
>> first up is one I alluded to straight
00:02:48.560 --> 00:02:51.830
off the top of the show. Microsoft One
00:02:51.840 --> 00:02:55.509
Drive new pay as you go storage billing
00:02:55.519 --> 00:03:01.270
option. This is MC1477185.
00:03:01.280 --> 00:03:03.830
So, this was the hey, you want to spend
00:03:03.840 --> 00:03:05.750
more money on one drive? Well, now
00:03:05.760 --> 00:03:10.070
you're going to get two. Uh, so this is,
00:03:10.080 --> 00:03:13.589
I think, one, you know, issue that
00:03:13.599 --> 00:03:15.270
organizations run into every once in a
00:03:15.280 --> 00:03:17.589
while, which is someone has a one drive
00:03:17.599 --> 00:03:22.470
and it's full. You can't add anymore and
00:03:22.480 --> 00:03:25.270
they what do what do you do with that?
00:03:25.280 --> 00:03:27.990
Well, one way is you could just spin up
00:03:28.000 --> 00:03:30.789
a SharePoint site and say, "Here's your
00:03:30.799 --> 00:03:33.509
new more storage over here in
00:03:33.519 --> 00:03:35.670
SharePoint.
00:03:35.680 --> 00:03:38.070
um could give you another one drive
00:03:38.080 --> 00:03:40.869
account I guess uh storage put it in
00:03:40.879 --> 00:03:43.030
teams whatever
00:03:43.040 --> 00:03:45.830
well that creates other entry points
00:03:45.840 --> 00:03:48.470
right and it's not all together so you
00:03:48.480 --> 00:03:52.309
might want to use uh this new pay as you
00:03:52.319 --> 00:03:55.509
go option for adding the additional
00:03:55.519 --> 00:03:58.070
storage to one drive now you might say
00:03:58.080 --> 00:03:59.910
Daniel you should be telling people they
00:03:59.920 --> 00:04:02.630
need to callull their information quit
00:04:02.640 --> 00:04:04.710
keeping all that old data uh
00:04:04.720 --> 00:04:06.710
>> blah blah blah. That is true. I agree
00:04:06.720 --> 00:04:09.830
with you. However, there are some times,
00:04:09.840 --> 00:04:13.110
especially temporarily, where
00:04:13.120 --> 00:04:15.030
there is,
00:04:15.040 --> 00:04:17.189
especially with levers,
00:04:17.199 --> 00:04:19.670
there's a bunch of data in someone's one
00:04:19.680 --> 00:04:23.189
drive. It needs to go somewhere. Okay,
00:04:23.199 --> 00:04:25.510
we're going to delete that one drive.
00:04:25.520 --> 00:04:29.590
So, manager or co-orker, you need to
00:04:29.600 --> 00:04:31.830
take on that data. It's like, well, I
00:04:31.840 --> 00:04:34.469
don't have time right now to do this
00:04:34.479 --> 00:04:35.990
immediately.
00:04:36.000 --> 00:04:38.710
So, give me that data, put it in my one
00:04:38.720 --> 00:04:40.469
drive, and then I'll go through it and
00:04:40.479 --> 00:04:42.150
delete stuff and blah blah blah blah.
00:04:42.160 --> 00:04:45.430
Well, you may exceed your storage then
00:04:45.440 --> 00:04:49.030
when as part of that process. Um, that's
00:04:49.040 --> 00:04:50.710
now is there other ways to handle that?
00:04:50.720 --> 00:04:52.870
Absolutely. But some people that's the
00:04:52.880 --> 00:04:54.629
way they do it, right? You take
00:04:54.639 --> 00:04:57.110
ownership of that content. Maybe that's
00:04:57.120 --> 00:04:59.030
the way you do it. Maybe maybe you do it
00:04:59.040 --> 00:05:03.110
a different way. But um this is that
00:05:03.120 --> 00:05:05.189
time I Yes, you should probably do this
00:05:05.199 --> 00:05:07.029
temporarily.
00:05:07.039 --> 00:05:08.790
If you've got too much data in your one
00:05:08.800 --> 00:05:10.469
drive,
00:05:10.479 --> 00:05:12.710
you probably need to to to callull it
00:05:12.720 --> 00:05:15.029
and get rid of the old stuff or move the
00:05:15.039 --> 00:05:16.150
stuff that's supposed to be in
00:05:16.160 --> 00:05:18.950
sharepoint and and being worked on with
00:05:18.960 --> 00:05:20.790
other people. Quit working out of your
00:05:20.800 --> 00:05:23.350
one drive like that. But you're going to
00:05:23.360 --> 00:05:29.670
be able to uh do this um and add that uh
00:05:29.680 --> 00:05:31.990
additional quota. So pay as you go,
00:05:32.000 --> 00:05:33.350
which means yes, you're going to have to
00:05:33.360 --> 00:05:35.350
pay for it.
00:05:35.360 --> 00:05:37.590
Uh there is an article where it talks
00:05:37.600 --> 00:05:40.790
about how you add more one drive and
00:05:40.800 --> 00:05:44.150
shareepoint storage, but um you can read
00:05:44.160 --> 00:05:45.670
that
00:05:45.680 --> 00:05:47.990
at your leisure.
00:05:48.000 --> 00:05:50.629
The rollout schedule public preview
00:05:50.639 --> 00:05:53.830
worldwide. The public preview is now
00:05:53.840 --> 00:05:55.990
available and then the general
00:05:56.000 --> 00:06:00.230
availability will be early November 2026
00:06:00.240 --> 00:06:02.390
and could be will be completed in early
00:06:02.400 --> 00:06:05.110
December. And this is for GCC, GCC high
00:06:05.120 --> 00:06:09.590
and DoD and everybody else. So, um,
00:06:09.600 --> 00:06:11.350
again, I hope you're using this
00:06:11.360 --> 00:06:15.749
temporarily and not in a way that is,
00:06:15.759 --> 00:06:19.350
uh, permanent for users, um, for the
00:06:19.360 --> 00:06:21.590
most part. So,
00:06:21.600 --> 00:06:23.510
Darl,
00:06:23.520 --> 00:06:26.870
uh, when you are, you know, going about
00:06:26.880 --> 00:06:28.710
and
00:06:28.720 --> 00:06:31.270
looking into how to add storage space to
00:06:31.280 --> 00:06:32.950
someone's one drive, you may do some
00:06:32.960 --> 00:06:36.230
research and put together a paper.
00:06:36.240 --> 00:06:39.909
Uh so tell us how that might that kind
00:06:39.919 --> 00:06:43.350
of p that process may be uh changing.
00:06:43.360 --> 00:06:45.749
Wait a minute. Sorry.
00:06:45.759 --> 00:06:46.790
>> Yeah.
00:06:46.800 --> 00:06:48.070
>> You know what we didn't do? You know how
00:06:48.080 --> 00:06:50.710
we like reorder the messages and I I
00:06:50.720 --> 00:06:52.309
kind of left it so that you're doing
00:06:52.319 --> 00:06:53.590
three in a row and I thought
00:06:53.600 --> 00:06:54.790
>> that was awesome.
00:06:54.800 --> 00:06:56.790
>> I better change that.
00:06:56.800 --> 00:06:58.309
>> Darl,
00:06:58.319 --> 00:07:01.589
>> uh tell us about this uh new update with
00:07:01.599 --> 00:07:03.670
co-pilot. how everything's coming
00:07:03.680 --> 00:07:06.230
together right now.
00:07:06.240 --> 00:07:07.990
>> Right. Right there. Yeah. Coming
00:07:08.000 --> 00:07:10.469
together like our show right now on the
00:07:10.479 --> 00:07:13.510
fly. Yeah. Um
00:07:13.520 --> 00:07:15.029
let's find the right message for that.
00:07:15.039 --> 00:07:19.909
It's uh I guess a recent drop um related
00:07:19.919 --> 00:07:23.430
to C-Pilot and we talked about it uh as
00:07:23.440 --> 00:07:25.350
a headline at the top of the show.
00:07:25.360 --> 00:07:28.469
Microsoft Copilot. The new ways to work
00:07:28.479 --> 00:07:31.510
across Microsoft Copilot and Microsoft
00:07:31.520 --> 00:07:33.830
365. How many times can you say
00:07:33.840 --> 00:07:38.950
Microsoft Copilot? This is MC147927.
00:07:38.960 --> 00:07:41.589
And yeah, look, you've heard Daniel and
00:07:41.599 --> 00:07:44.950
I joke about this on and off. Uh we know
00:07:44.960 --> 00:07:48.070
that the name was coming together, the
00:07:48.080 --> 00:07:50.550
apps are coming together, branding's
00:07:50.560 --> 00:07:52.870
coming together. Well, the app is coming
00:07:52.880 --> 00:07:54.869
together. And we had it you know rumored
00:07:54.879 --> 00:07:58.550
for a few months that Microsoft was
00:07:58.560 --> 00:08:01.110
working on this super app was another
00:08:01.120 --> 00:08:03.670
way of referring to it. What is it? It
00:08:03.680 --> 00:08:09.430
is uh we have had chat um with co-pilot
00:08:09.440 --> 00:08:12.309
and co-work as an experience. You can
00:08:12.319 --> 00:08:15.909
switch between the two. uh one is
00:08:15.919 --> 00:08:18.230
predominantly free and included and you
00:08:18.240 --> 00:08:21.110
can use various different models to work
00:08:21.120 --> 00:08:23.909
on a task. Ask it some questions, get it
00:08:23.919 --> 00:08:27.909
to do something for you, involve agents.
00:08:27.919 --> 00:08:29.430
And then there's co-work which is
00:08:29.440 --> 00:08:32.070
multitask doing many things, longer
00:08:32.080 --> 00:08:35.670
tasks, um thinks a bit longer and as
00:08:35.680 --> 00:08:38.389
we've been experiencing um there is some
00:08:38.399 --> 00:08:41.350
costs involved. what has been added to
00:08:41.360 --> 00:08:45.509
this uh unified app um which is I guess
00:08:45.519 --> 00:08:48.150
it's just called Microsoft Copilot now
00:08:48.160 --> 00:08:50.389
uh you'll go to
00:08:50.399 --> 00:08:52.870
office.com if that's your way of getting
00:08:52.880 --> 00:08:55.030
there uh it used to be known as
00:08:55.040 --> 00:08:57.269
m365.cloud.microsoft
00:08:57.279 --> 00:08:59.030
now it's copilot.cloud.microsoft
00:08:59.040 --> 00:09:00.710
cloud.microsoft
00:09:00.720 --> 00:09:03.910
and you'll also see uh the code
00:09:03.920 --> 00:09:05.590
experience
00:09:05.600 --> 00:09:09.190
and the autopilot experience.
00:09:09.200 --> 00:09:12.630
Um so the the home in co-pilot app uh
00:09:12.640 --> 00:09:15.030
will give you that co-pilot and co-work
00:09:15.040 --> 00:09:17.990
switching experience but the code part
00:09:18.000 --> 00:09:21.829
of it uh will allow you to I guess use
00:09:21.839 --> 00:09:24.070
uh an experience which is a bit more
00:09:24.080 --> 00:09:28.150
open in terms of defining what you want.
00:09:28.160 --> 00:09:31.430
uh so you know one level up from co-work
00:09:31.440 --> 00:09:33.829
uh people who have been using the
00:09:33.839 --> 00:09:35.750
anthropic experience will be quite
00:09:35.760 --> 00:09:37.430
familiar with this and this really is
00:09:37.440 --> 00:09:40.389
mirroring that uh it's just doing it in
00:09:40.399 --> 00:09:43.990
a Microsoft kind of way uh that you can
00:09:44.000 --> 00:09:47.509
code up apps you can u describe a bit
00:09:47.519 --> 00:09:49.190
more of what you want and it will
00:09:49.200 --> 00:09:50.710
programmatically
00:09:50.720 --> 00:09:53.750
uh achieve and and and do that task for
00:09:53.760 --> 00:09:57.509
you what we um Daniel and I you know
00:09:57.519 --> 00:09:59.509
reasonably new to this cuz it is a
00:09:59.519 --> 00:10:02.070
recently new announcement at the time of
00:10:02.080 --> 00:10:04.150
recording. So we haven't looked
00:10:04.160 --> 00:10:05.750
massively deeply into it. So we don't
00:10:05.760 --> 00:10:08.230
know the mechanisms for how this will
00:10:08.240 --> 00:10:11.030
work whether uh I think Daniel you were
00:10:11.040 --> 00:10:13.590
suggesting it might have to leverage uh
00:10:13.600 --> 00:10:17.030
GitHub uh in a space because it the code
00:10:17.040 --> 00:10:20.389
needs to have a place and an environment
00:10:20.399 --> 00:10:24.069
to create the the app itself and host it
00:10:24.079 --> 00:10:25.509
somewhere.
00:10:25.519 --> 00:10:27.670
>> Yeah. I
00:10:27.680 --> 00:10:29.750
That that is a question you know because
00:10:29.760 --> 00:10:32.069
when we talk about code we you know are
00:10:32.079 --> 00:10:35.509
we talking about actual code um so is
00:10:35.519 --> 00:10:39.509
this a GitHub kind of connection or is
00:10:39.519 --> 00:10:43.269
this more around coding of apps within
00:10:43.279 --> 00:10:47.590
the you know the power platform and M365
00:10:47.600 --> 00:10:51.430
experience right so don't know a whole
00:10:51.440 --> 00:10:55.590
lot yet uh about that so uh we'll see
00:10:55.600 --> 00:10:57.509
you know there wasn't any kind of up
00:10:57.519 --> 00:11:00.150
announcements around you know any
00:11:00.160 --> 00:11:03.350
connections into GitHub and you know the
00:11:03.360 --> 00:11:05.910
requirements for using GitHub enterprise
00:11:05.920 --> 00:11:08.389
or any we don't know and and that might
00:11:08.399 --> 00:11:11.269
not even be within the realm of this uh
00:11:11.279 --> 00:11:14.389
code functionality um but so it's still
00:11:14.399 --> 00:11:16.310
a question in my mind
00:11:16.320 --> 00:11:19.990
>> yeah uh the other uh addition is
00:11:20.000 --> 00:11:23.430
autopilot and this was known earlier as
00:11:23.440 --> 00:11:26.949
scout and its role uh is is a bit like
00:11:26.959 --> 00:11:30.389
the environment that that some early
00:11:30.399 --> 00:11:32.389
frontier people jumped on. You could
00:11:32.399 --> 00:11:34.630
download this automated experience but
00:11:34.640 --> 00:11:37.590
be running on your machine and uh much
00:11:37.600 --> 00:11:40.550
like code you can do a lot with it.
00:11:40.560 --> 00:11:43.269
There's you know a lot of possibilities.
00:11:43.279 --> 00:11:48.150
Um but Microsoft will run this in a a VM
00:11:48.160 --> 00:11:50.389
style way of working like it'll be a
00:11:50.399 --> 00:11:52.630
machine but it's kind of hosted. Uh, I
00:11:52.640 --> 00:11:54.310
think Daniel, you mentioned that one of
00:11:54.320 --> 00:11:58.310
the the limitations or the um friction
00:11:58.320 --> 00:12:00.150
points for adopting this was you did
00:12:00.160 --> 00:12:01.829
need to have a reasonably good machine
00:12:01.839 --> 00:12:06.069
to run uh Scout uh locally.
00:12:06.079 --> 00:12:08.710
>> Yeah. And I mean there was several setup
00:12:08.720 --> 00:12:10.629
steps that had to be done in an
00:12:10.639 --> 00:12:13.590
organization and on the laptop to enable
00:12:13.600 --> 00:12:17.509
it. Um, and so there was just friction
00:12:17.519 --> 00:12:21.350
uh to getting it. And so I would assume,
00:12:21.360 --> 00:12:22.870
just guessing, I don't know any
00:12:22.880 --> 00:12:24.069
information about this, but I would
00:12:24.079 --> 00:12:26.389
assume adoption was kind of low for it
00:12:26.399 --> 00:12:28.629
uh because of that.
00:12:28.639 --> 00:12:31.670
And you know, I will say this is
00:12:31.680 --> 00:12:33.509
another,
00:12:33.519 --> 00:12:36.870
you know, who thought of the the
00:12:36.880 --> 00:12:40.470
autopilot as the name for this? Yeah,
00:12:40.480 --> 00:12:43.030
>> because there's already a Microsoft
00:12:43.040 --> 00:12:44.470
autopilot.
00:12:44.480 --> 00:12:46.629
>> There's such a thing and it has nothing
00:12:46.639 --> 00:12:48.150
to do with AI.
00:12:48.160 --> 00:12:51.670
>> I mean, it it's it's basically a, you
00:12:51.680 --> 00:12:54.230
know, configuring Windows devices,
00:12:54.240 --> 00:12:56.550
>> you know, automatically. And so, and
00:12:56.560 --> 00:12:58.790
it's been around forever. So, they've
00:12:58.800 --> 00:13:01.269
now co-opted this and it's going to mean
00:13:01.279 --> 00:13:04.230
something totally different now. Um, so
00:13:04.240 --> 00:13:08.069
I I don't know. I whoever named this is
00:13:08.079 --> 00:13:12.310
um come on you know like you could
00:13:12.320 --> 00:13:13.829
anyway I I was about to say you could
00:13:13.839 --> 00:13:16.550
have stuck with scout
00:13:16.560 --> 00:13:20.150
anything else but reusing the same name.
00:13:20.160 --> 00:13:22.629
>> Yeah. Yeah. That that just um doesn't
00:13:22.639 --> 00:13:24.710
help with the the confusion. There is a
00:13:24.720 --> 00:13:27.750
a good blog post that steps through a
00:13:27.760 --> 00:13:31.350
lot of uh the detail. Um, but there is a
00:13:31.360 --> 00:13:33.030
lot of
00:13:33.040 --> 00:13:35.750
vision setting and marketing speak that
00:13:35.760 --> 00:13:37.910
you'll have to get around. Uh, maybe try
00:13:37.920 --> 00:13:41.750
what Daniel did um, himself uh, and get
00:13:41.760 --> 00:13:43.910
co-pilot to look at this page, but then
00:13:43.920 --> 00:13:46.069
explain it like a 12 year old to as if
00:13:46.079 --> 00:13:48.550
he was a 12-year-old and remove the
00:13:48.560 --> 00:13:50.389
marketing speak and you'll get down to
00:13:50.399 --> 00:13:52.310
just the bullet points of what has
00:13:52.320 --> 00:13:54.710
actually changed, what has actually um,
00:13:54.720 --> 00:13:58.470
been uh, pulled together here. Um here's
00:13:58.480 --> 00:14:00.949
like there's a screenshot here. I know
00:14:00.959 --> 00:14:04.150
audio listeners won't um see this but
00:14:04.160 --> 00:14:06.150
that the the vision for what that will
00:14:06.160 --> 00:14:09.910
look like. Um today we have chat and
00:14:09.920 --> 00:14:11.829
co-work as a switch over on the lefth
00:14:11.839 --> 00:14:14.710
hand panel. Now home is going to be that
00:14:14.720 --> 00:14:17.189
unified experience. You'll see the the
00:14:17.199 --> 00:14:19.110
choice between chat and co-work will be
00:14:19.120 --> 00:14:21.910
in the chat box as you start your
00:14:21.920 --> 00:14:24.230
conversation. uh whereas you can switch
00:14:24.240 --> 00:14:27.030
between code and autopilot in that panel
00:14:27.040 --> 00:14:30.389
and you know one concern I had when I
00:14:30.399 --> 00:14:32.790
heard about this coming was okay chat
00:14:32.800 --> 00:14:36.790
and co-work um you do when you choose to
00:14:36.800 --> 00:14:38.230
work in the co-work space if it's
00:14:38.240 --> 00:14:41.509
available to you uh you go back to this
00:14:41.519 --> 00:14:44.550
uh again after a day or so and ask it
00:14:44.560 --> 00:14:46.069
another question it'll still be in
00:14:46.079 --> 00:14:49.189
co-work so keep in mind what you are
00:14:49.199 --> 00:14:50.949
actually using and whether it's the
00:14:50.959 --> 00:14:53.990
right tool cuz it could cost you. Um,
00:14:54.000 --> 00:14:54.870
>> yeah, absolutely.
00:14:54.880 --> 00:14:57.269
>> Yeah. Yeah. So, there's a lot more to to
00:14:57.279 --> 00:14:59.430
look at. Um,
00:14:59.440 --> 00:15:01.350
and I'm sure there are people that are
00:15:01.360 --> 00:15:03.509
covering this in in greater depth. A
00:15:03.519 --> 00:15:05.030
friend or two I can see have already
00:15:05.040 --> 00:15:06.710
published videos stepping through and
00:15:06.720 --> 00:15:08.949
giving their reaction. So, uh, maybe
00:15:08.959 --> 00:15:12.150
we'll leave some links to that in the
00:15:12.160 --> 00:15:15.990
description of this video. Um, but when
00:15:16.000 --> 00:15:19.509
will this arrive? Uh, let's, uh, jump on
00:15:19.519 --> 00:15:22.629
in.
00:15:22.639 --> 00:15:25.269
Wow. Okay. Where is it?
00:15:25.279 --> 00:15:28.389
Somewhere here in this message.
00:15:28.399 --> 00:15:31.350
Is it just a a marketing message filled
00:15:31.360 --> 00:15:35.110
with stuff and no dates?
00:15:35.120 --> 00:15:36.230
>> Am I right, Daniel?
00:15:36.240 --> 00:15:37.990
>> Coming soon.
00:15:38.000 --> 00:15:40.389
>> Coming soon. Okay.
00:15:40.399 --> 00:15:43.910
>> Well, it's coming to um Frontier, right?
00:15:43.920 --> 00:15:48.629
first uh for the autopilot and
00:15:48.639 --> 00:15:53.430
>> um so but I don't know when it's if they
00:15:53.440 --> 00:15:55.350
put a date it's like next month
00:15:55.360 --> 00:15:57.269
>> it's in the summary right at the top
00:15:57.279 --> 00:15:58.949
rollouts roll out
00:15:58.959 --> 00:15:59.910
>> October yeah
00:15:59.920 --> 00:16:03.350
>> begin in October so there are individual
00:16:03.360 --> 00:16:05.670
roll outs for I guess the the various
00:16:05.680 --> 00:16:08.949
different functions and capabilities
00:16:08.959 --> 00:16:10.710
>> sorry about that um but
00:16:10.720 --> 00:16:12.710
>> well it's it's rolling out you know
00:16:12.720 --> 00:16:18.790
Frontier here um for the so co-work
00:16:18.800 --> 00:16:21.189
change is is rolling out in in October
00:16:21.199 --> 00:16:25.030
for everybody you know that has that the
00:16:25.040 --> 00:16:29.990
um frontier in October for um some of
00:16:30.000 --> 00:16:31.749
that you can read right
00:16:31.759 --> 00:16:33.590
>> oh yeah yeah it's under each of the
00:16:33.600 --> 00:16:35.670
sections here in the messages code it
00:16:35.680 --> 00:16:39.030
says Frontier later this month
00:16:39.040 --> 00:16:42.150
>> um autopilot we'll update this message
00:16:42.160 --> 00:16:44.389
when we've got some roll out timings,
00:16:44.399 --> 00:16:45.030
>> right?
00:16:45.040 --> 00:16:47.829
>> Oh, fantastic. Yeah. So, yeah, there's a
00:16:47.839 --> 00:16:49.509
lot to lot to get to grips with.
00:16:49.519 --> 00:16:52.870
Apparently, it's a big deal. Yeah. Um,
00:16:52.880 --> 00:16:54.470
you know, something else that we think
00:16:54.480 --> 00:16:56.790
is a a big deal. I think it's actually
00:16:56.800 --> 00:17:00.069
part of the the backstory for this, but
00:17:00.079 --> 00:17:02.230
um, there's some changes happening to
00:17:02.240 --> 00:17:04.150
researcher and how that's being
00:17:04.160 --> 00:17:06.069
positioned.
00:17:06.079 --> 00:17:09.350
>> Indeed. So, this is Microsoft 365
00:17:09.360 --> 00:17:11.590
copilot. Although isn't that changed now
00:17:11.600 --> 00:17:14.549
to just Microsoft Copilot? Microsoft 365
00:17:14.559 --> 00:17:16.949
copot updates to the researcher
00:17:16.959 --> 00:17:22.069
experience MC1476269.
00:17:22.079 --> 00:17:25.270
The research is
00:17:25.280 --> 00:17:29.430
uh a really cool experience I think for
00:17:29.440 --> 00:17:32.070
doing research, but also it has
00:17:32.080 --> 00:17:33.669
capabilities and we covered on the show
00:17:33.679 --> 00:17:37.110
a while back about using the different
00:17:37.120 --> 00:17:41.909
types of LLMs to your advantage and
00:17:41.919 --> 00:17:45.830
having that experience of um doing that
00:17:45.840 --> 00:17:48.950
comparison uh and and helping each other
00:17:48.960 --> 00:17:51.110
out and it it's just a really cool
00:17:51.120 --> 00:17:53.990
experience. in research, but it also has
00:17:54.000 --> 00:17:56.150
in researcher you're able to save
00:17:56.160 --> 00:17:57.669
prompts
00:17:57.679 --> 00:18:00.789
uh that you have put in it so that you
00:18:00.799 --> 00:18:03.190
can just come back and rerun those uh
00:18:03.200 --> 00:18:05.029
doing research over and over again, you
00:18:05.039 --> 00:18:09.430
know, based upon new stuff. Um a history
00:18:09.440 --> 00:18:12.470
tab, you know, um and then there's this
00:18:12.480 --> 00:18:13.990
really cool functionality where you say,
00:18:14.000 --> 00:18:15.430
"Hey, I want to do this research." And
00:18:15.440 --> 00:18:16.789
it says, "Okay, I'm gathering some
00:18:16.799 --> 00:18:19.110
stuff, but how long do you want this to
00:18:19.120 --> 00:18:22.390
be? Do you want this report to be one to
00:18:22.400 --> 00:18:25.270
three pages? You know, giving you a how
00:18:25.280 --> 00:18:27.270
big of a report are you actually looking
00:18:27.280 --> 00:18:30.310
for? Well, Microsoft's changing and this
00:18:30.320 --> 00:18:34.310
is part of the um really I I think part
00:18:34.320 --> 00:18:37.350
of all of these moves. One is that
00:18:37.360 --> 00:18:40.150
they're really wanting to bring the
00:18:40.160 --> 00:18:42.630
researcher experience
00:18:42.640 --> 00:18:46.070
um navigation out. Like so now you have
00:18:46.080 --> 00:18:48.710
to click on and click researcher and it
00:18:48.720 --> 00:18:50.230
brings in this new experience. Well,
00:18:50.240 --> 00:18:52.310
they're going to bring researcher
00:18:52.320 --> 00:18:54.710
functionality just to co-pilot, right?
00:18:54.720 --> 00:18:58.310
So you don't go out to researcher is
00:18:58.320 --> 00:19:00.789
just going to do it. Now how you call
00:19:00.799 --> 00:19:02.310
it, I don't know.
00:19:02.320 --> 00:19:04.150
>> You know, are you just going to do the
00:19:04.160 --> 00:19:06.549
drop down and say researcher as a
00:19:06.559 --> 00:19:08.549
knowledge? I I don't know
00:19:08.559 --> 00:19:09.669
>> because they don't tell us in the
00:19:09.679 --> 00:19:11.190
message and they don't give us a blog
00:19:11.200 --> 00:19:12.310
post and they don't give us a
00:19:12.320 --> 00:19:17.110
screenshot. So, we have no idea. Um, but
00:19:17.120 --> 00:19:19.110
basically they're going to remove all of
00:19:19.120 --> 00:19:22.630
that functionality that makes it the UI
00:19:22.640 --> 00:19:24.710
kind of unique to researcher because
00:19:24.720 --> 00:19:27.190
it's not going to be its own UI anymore.
00:19:27.200 --> 00:19:28.870
>> So, they're going to they are going to
00:19:28.880 --> 00:19:30.390
remove that functionality. I talked
00:19:30.400 --> 00:19:32.710
about the report length. It's just going
00:19:32.720 --> 00:19:35.029
to kind of guess what you should have
00:19:35.039 --> 00:19:39.110
based upon what you've inputed. Um,
00:19:39.120 --> 00:19:40.789
>> you're not going to have the support uh
00:19:40.799 --> 00:19:44.070
the the uh saved prompts tab. You're not
00:19:44.080 --> 00:19:45.430
going to have the history tab. Not going
00:19:45.440 --> 00:19:47.270
to have the reports tab, the explore
00:19:47.280 --> 00:19:49.830
tab, or the recommended prompts. All of
00:19:49.840 --> 00:19:51.909
that's going to be retired.
00:19:51.919 --> 00:19:56.070
So, you know, I hope we can still keep
00:19:56.080 --> 00:19:57.909
the comparison
00:19:57.919 --> 00:20:00.710
uh may hopefully between, you know, the
00:20:00.720 --> 00:20:03.990
anthropic and the GPT models and and
00:20:04.000 --> 00:20:06.950
giving you so they can help each other.
00:20:06.960 --> 00:20:11.110
I don't know. But um it's all being
00:20:11.120 --> 00:20:13.510
consolidated into the co-pilot
00:20:13.520 --> 00:20:14.870
experience.
00:20:14.880 --> 00:20:17.590
>> Yeah, Daniel, I think um maybe we'll
00:20:17.600 --> 00:20:19.510
have to describe these things that we
00:20:19.520 --> 00:20:22.789
want within the prompt. Um, and I I
00:20:22.799 --> 00:20:24.310
suggest I don't know what this
00:20:24.320 --> 00:20:26.230
experience will be like, but I suggest
00:20:26.240 --> 00:20:32.390
that um you you do ask researcher when
00:20:32.400 --> 00:20:33.990
actually let me back up a bit that we do
00:20:34.000 --> 00:20:35.990
have a small clue as to what this looks
00:20:36.000 --> 00:20:38.950
like. In the chat box, you can add
00:20:38.960 --> 00:20:41.430
content the plus button. And I think
00:20:41.440 --> 00:20:43.590
it's like adding a skill like when you
00:20:43.600 --> 00:20:45.430
can say, "Hey, I want to add the Excel
00:20:45.440 --> 00:20:47.430
skill." Uh, you'll add the researcher
00:20:47.440 --> 00:20:51.110
skill. Um, and maybe uh you can say,
00:20:51.120 --> 00:20:52.950
"Look, ask me some questions, some
00:20:52.960 --> 00:20:55.350
clarifying questions before we get into
00:20:55.360 --> 00:20:58.070
doing the actual research." But it feels
00:20:58.080 --> 00:21:00.070
like the weight of that isn't the way
00:21:00.080 --> 00:21:02.149
that you prompt again.
00:21:02.159 --> 00:21:06.470
>> Yep. So the And you could do that now in
00:21:06.480 --> 00:21:09.029
chat. You can go and say plus you could
00:21:09.039 --> 00:21:11.909
say add capabilities and click on
00:21:11.919 --> 00:21:14.230
research a topic. And so that you could
00:21:14.240 --> 00:21:16.950
do that now. And I'm assuming again, we
00:21:16.960 --> 00:21:18.149
don't have any screenshots, we don't
00:21:18.159 --> 00:21:20.070
have any blog posts, we don't have I'm
00:21:20.080 --> 00:21:22.310
assuming that they just mean that's the
00:21:22.320 --> 00:21:24.310
way you're going to call researcher
00:21:24.320 --> 00:21:25.510
>> and that's going to be the only thing.
00:21:25.520 --> 00:21:27.110
You're not going to be able to, you
00:21:27.120 --> 00:21:29.669
know, pop out and and under agents click
00:21:29.679 --> 00:21:33.350
on researcher. Um,
00:21:33.360 --> 00:21:35.590
which is fine, but if you use that
00:21:35.600 --> 00:21:38.470
history tab or the save tab of your the
00:21:38.480 --> 00:21:40.630
prompts that you've done,
00:21:40.640 --> 00:21:43.029
>> uh, you know, that's not that's not fun.
00:21:43.039 --> 00:21:46.470
uh you're losing that. Um the explore
00:21:46.480 --> 00:21:49.350
which gave you kind of the the explore
00:21:49.360 --> 00:21:53.270
tab which was uh is still a way for you
00:21:53.280 --> 00:21:56.549
to get ideas as to how you know what you
00:21:56.559 --> 00:21:58.390
can research and how you could use that.
00:21:58.400 --> 00:22:01.270
Now I also could see and I don't know
00:22:01.280 --> 00:22:04.390
anything about this and no NDAs or
00:22:04.400 --> 00:22:06.710
anything. I haven't been told anything,
00:22:06.720 --> 00:22:10.149
but um if you think about it,
00:22:10.159 --> 00:22:11.669
researcher,
00:22:11.679 --> 00:22:13.909
it's going and doing more complex stuff
00:22:13.919 --> 00:22:16.789
than a regular co-pilot chat.
00:22:16.799 --> 00:22:19.590
And it actually is kind of close,
00:22:19.600 --> 00:22:21.510
depending on how you look at it, to what
00:22:21.520 --> 00:22:23.750
co-work can do. M
00:22:23.760 --> 00:22:25.590
>> and so
00:22:25.600 --> 00:22:28.710
I wouldn't you know it wouldn't shock me
00:22:28.720 --> 00:22:32.549
if later down the road researcher is
00:22:32.559 --> 00:22:34.390
something they say that's more of a
00:22:34.400 --> 00:22:36.630
co-work thing or it's more of a you need
00:22:36.640 --> 00:22:39.190
to pay extra to use it. Um
00:22:39.200 --> 00:22:41.909
>> I I don't know they could still keep it
00:22:41.919 --> 00:22:44.230
there. I'm just saying I that's kind of
00:22:44.240 --> 00:22:46.710
a feeling when they start making changes
00:22:46.720 --> 00:22:50.549
like this and making it not as special,
00:22:50.559 --> 00:22:52.710
you know, removing the navigation. I
00:22:52.720 --> 00:22:54.470
don't know. It just kind of
00:22:54.480 --> 00:22:56.710
>> seems
00:22:56.720 --> 00:22:58.789
>> seems interesting. So, that's just the
00:22:58.799 --> 00:23:01.669
way I'll put it. So, roll out schedule.
00:23:01.679 --> 00:23:03.430
Well, it's not really rollout. It's
00:23:03.440 --> 00:23:06.950
retirement. Uh worldwide GCC and GCC
00:23:06.960 --> 00:23:10.149
high beginning October 21st
00:23:10.159 --> 00:23:12.070
and then expected to be completed by
00:23:12.080 --> 00:23:16.149
December 30th of this year. And it does
00:23:16.159 --> 00:23:18.950
say it's gradually rolling out and users
00:23:18.960 --> 00:23:21.750
in the same environment in your
00:23:21.760 --> 00:23:24.470
organization may see it different. You
00:23:24.480 --> 00:23:27.270
may have different, you know, one person
00:23:27.280 --> 00:23:29.830
sees it in the navigation, one person
00:23:29.840 --> 00:23:33.190
doesn't, you know. Um, so that's going
00:23:33.200 --> 00:23:37.110
to be fun, you know, for
00:23:37.120 --> 00:23:38.070
>> Yeah.
00:23:38.080 --> 00:23:41.350
>> Anyway, let's talk about more fun, Darl.
00:23:41.360 --> 00:23:45.590
And fun. You know what is fun is when
00:23:45.600 --> 00:23:47.590
I'm writing emails and all the
00:23:47.600 --> 00:23:50.870
squigglies are showing up in my emails.
00:23:50.880 --> 00:23:52.070
>> Squiggies.
00:23:52.080 --> 00:23:53.669
>> Yeah. You know, squiggly saying, "Hey,
00:23:53.679 --> 00:23:55.510
you misspelled this." Or, "Oh, yeah.
00:23:55.520 --> 00:23:57.750
>> Are you sure that's the proper grammar?"
00:23:57.760 --> 00:23:59.909
That's what I call the blue squiggly.
00:23:59.919 --> 00:24:03.190
>> Uh, tell us how we might be able to, you
00:24:03.200 --> 00:24:06.070
know, not not use that anymore if maybe
00:24:06.080 --> 00:24:08.149
a new capability or
00:24:08.159 --> 00:24:09.990
>> maybe it's not new. Maybe it's something
00:24:10.000 --> 00:24:10.789
we've had before.
00:24:10.799 --> 00:24:12.870
>> Doesn't feel new. just feels like it's
00:24:12.880 --> 00:24:14.390
rephrased.
00:24:14.400 --> 00:24:17.190
Spell check before sending emails in new
00:24:17.200 --> 00:24:20.310
Outlook. Or maybe it was an old Outlook.
00:24:20.320 --> 00:24:21.669
That's not part of the title, by the
00:24:21.679 --> 00:24:24.630
way. MC1479509.
00:24:24.640 --> 00:24:26.390
Daniel's right. I feel like this was
00:24:26.400 --> 00:24:28.710
something that was available in Outlook
00:24:28.720 --> 00:24:31.510
98. And it was a tick box that said,
00:24:31.520 --> 00:24:33.669
"Check my spelling and grammar before I
00:24:33.679 --> 00:24:36.310
send this message." Uh, and it would
00:24:36.320 --> 00:24:37.830
take you through that and show you what
00:24:37.840 --> 00:24:39.590
it found. Now, we've become so
00:24:39.600 --> 00:24:42.310
accustomed to seeing the squigglies, the
00:24:42.320 --> 00:24:44.789
red underline and the blue underline
00:24:44.799 --> 00:24:47.830
that interrupt us. I'm getting into an
00:24:47.840 --> 00:24:51.110
impassion topic here. Interrupt our flow
00:24:51.120 --> 00:24:53.269
because we Oh, got to get rid of the
00:24:53.279 --> 00:24:55.350
lines. Right click, choose the correct
00:24:55.360 --> 00:24:57.029
word. Right click, choose the correct
00:24:57.039 --> 00:25:01.350
grammar. Uh, I think this feature, the
00:25:01.360 --> 00:25:04.710
return of this feature, uh, will help
00:25:04.720 --> 00:25:08.230
some of us maybe, um, get back into the
00:25:08.240 --> 00:25:11.510
flow of writing that email and then
00:25:11.520 --> 00:25:13.590
going through and checking for spelling,
00:25:13.600 --> 00:25:16.549
grammar before we go through the the
00:25:16.559 --> 00:25:19.190
actual sending of the message. So, this
00:25:19.200 --> 00:25:21.830
um, uh, let's see, it's uh, how does
00:25:21.840 --> 00:25:24.149
this actually work? Um, what will
00:25:24.159 --> 00:25:26.710
happen? Users will configure this to to
00:25:26.720 --> 00:25:28.630
check spelling and grammar before the
00:25:28.640 --> 00:25:32.310
email is sent. Um, it will
00:25:32.320 --> 00:25:33.669
well, yeah, it's going to reduce the
00:25:33.679 --> 00:25:35.909
spelling mistakes. If if you aren't
00:25:35.919 --> 00:25:38.070
already ignoring the red lines and blue
00:25:38.080 --> 00:25:40.149
lines, some people do. They're like, I'm
00:25:40.159 --> 00:25:42.149
so important. I don't have time to go
00:25:42.159 --> 00:25:43.909
back and correct this stuff. They'll
00:25:43.919 --> 00:25:47.110
figure it out. Um, but yeah, what I like
00:25:47.120 --> 00:25:50.070
about it, Daniel, is uh that as you're
00:25:50.080 --> 00:25:52.070
sending it, going through and checking
00:25:52.080 --> 00:25:56.630
these things as a last uh hurrah before
00:25:56.640 --> 00:25:59.590
the message goes off, um you'll still
00:25:59.600 --> 00:26:01.350
look professional because you've you've
00:26:01.360 --> 00:26:03.269
managed to to fix these things.
00:26:03.279 --> 00:26:04.549
>> Mhm. Indeed.
00:26:04.559 --> 00:26:05.590
>> Yeah.
00:26:05.600 --> 00:26:09.750
>> Um when is this arriving?
00:26:09.760 --> 00:26:13.510
It is uh oo there's a breakdown of five
00:26:13.520 --> 00:26:15.029
delivery times generally available
00:26:15.039 --> 00:26:17.990
worldwide begin mid November and
00:26:18.000 --> 00:26:20.789
complete by early December targeted
00:26:20.799 --> 00:26:22.070
release worldwide. Why are they doing
00:26:22.080 --> 00:26:24.870
that in that order
00:26:24.880 --> 00:26:27.190
come out in October
00:26:27.200 --> 00:26:29.669
just so you know before generally
00:26:29.679 --> 00:26:32.230
available as it usually would be um and
00:26:32.240 --> 00:26:34.470
complete by late October. So yeah,
00:26:34.480 --> 00:26:37.669
generally available for GCC November,
00:26:37.679 --> 00:26:41.909
December, GCC high November. This is
00:26:41.919 --> 00:26:44.070
weird guys. Come on, man. You would
00:26:44.080 --> 00:26:47.830
normally say GCC GCC high and DoD roll
00:26:47.840 --> 00:26:50.470
out mid November through to mid
00:26:50.480 --> 00:26:53.590
December. Anyway, I've corrected that.
00:26:53.600 --> 00:26:55.750
Maybe you should have used another kind
00:26:55.760 --> 00:26:57.029
of
00:26:57.039 --> 00:26:59.909
>> message format and sense check before
00:26:59.919 --> 00:27:02.549
you save this message and publish it. M
00:27:02.559 --> 00:27:04.230
>> that would be a great feature to build
00:27:04.240 --> 00:27:07.269
into your checking. Um but let's move
00:27:07.279 --> 00:27:09.830
into something else that feels like old
00:27:09.840 --> 00:27:12.549
school but um is actually mixed with new
00:27:12.559 --> 00:27:15.590
school HTML. Tell us Daniel what's
00:27:15.600 --> 00:27:16.710
happening.
00:27:16.720 --> 00:27:19.830
>> SharePoint HTML pages.
00:27:19.840 --> 00:27:21.190
>> Oh fantastic.
00:27:21.200 --> 00:27:27.110
>> I like short titles. MC1479517.
00:27:27.120 --> 00:27:30.470
So we talked a little bit about uh
00:27:30.480 --> 00:27:35.269
co-pilot in SharePoint which is now GA
00:27:35.279 --> 00:27:39.669
by the way. So the AI in SharePoint, you
00:27:39.679 --> 00:27:41.190
know, having Copilot in SharePoint,
00:27:41.200 --> 00:27:44.070
having uh the capabilities, it's
00:27:44.080 --> 00:27:46.310
fantastic. And one of those capabilities
00:27:46.320 --> 00:27:50.149
is you could generate an HTML page with
00:27:50.159 --> 00:27:54.630
Copilot that is uh based upon data that
00:27:54.640 --> 00:27:56.070
you have in your, you know, in a
00:27:56.080 --> 00:27:58.389
SharePoint list and it'll render a
00:27:58.399 --> 00:28:02.310
report and look pretty snazzy. Well, now
00:28:02.320 --> 00:28:04.549
we can also
00:28:04.559 --> 00:28:08.710
uh create a regular HTML page and going
00:28:08.720 --> 00:28:11.909
to the new button and click new and give
00:28:11.919 --> 00:28:17.510
me an HTML. We can also upload HTML page
00:28:17.520 --> 00:28:20.710
into our SharePoint site. And when we do
00:28:20.720 --> 00:28:23.269
that, we can edit it. We can edit the
00:28:23.279 --> 00:28:27.029
HTML page. We can we can share it out
00:28:27.039 --> 00:28:30.470
like we can other types of content in
00:28:30.480 --> 00:28:32.549
SharePoint.
00:28:32.559 --> 00:28:37.110
There I will state there is one link in
00:28:37.120 --> 00:28:40.710
this update and it's toward the bottom.
00:28:40.720 --> 00:28:45.190
says review and it's uh a page on the
00:28:45.200 --> 00:28:48.630
support site called uh create edit
00:28:48.640 --> 00:28:52.870
publish HTML pages or create upload edit
00:28:52.880 --> 00:28:54.870
publish anyway
00:28:54.880 --> 00:28:57.510
uh so you know it kind of walks you
00:28:57.520 --> 00:28:59.590
through how you could do that. The
00:28:59.600 --> 00:29:01.269
really important part that I kind of
00:29:01.279 --> 00:29:04.470
wanted to focus on is toward the bottom
00:29:04.480 --> 00:29:06.789
um there is a frequently asked questions
00:29:06.799 --> 00:29:08.789
and the first question is what can I do
00:29:08.799 --> 00:29:11.990
with an HTML page in SharePoint and then
00:29:12.000 --> 00:29:14.470
it lists in a table format all the
00:29:14.480 --> 00:29:16.789
little things you know the things you
00:29:16.799 --> 00:29:19.430
might think an HTML page would do and
00:29:19.440 --> 00:29:22.149
does it support it. So things like
00:29:22.159 --> 00:29:26.310
outbound API calls, no
00:29:26.320 --> 00:29:31.430
CDN scripts, no. Uh you know, SharePoint
00:29:31.440 --> 00:29:36.470
app and teams on a mobile, no promote to
00:29:36.480 --> 00:29:40.230
news post, no you know. Anyway, so look
00:29:40.240 --> 00:29:43.750
at this. You can think of uh you know,
00:29:43.760 --> 00:29:46.149
hey, can if I'm going to upload this
00:29:46.159 --> 00:29:47.990
HTML, can it do this? Can it do that?
00:29:48.000 --> 00:29:51.029
Well, here is a table that tells you a
00:29:51.039 --> 00:29:55.269
lot. And if you um if it doesn't answer
00:29:55.279 --> 00:29:57.510
it, then you can give feedback here and
00:29:57.520 --> 00:29:59.669
maybe they'll keep editing, you know,
00:29:59.679 --> 00:30:03.669
this uh this table with items from
00:30:03.679 --> 00:30:07.830
people saying, "Hey, can I do live data
00:30:07.840 --> 00:30:10.230
sharing with this HTML page?"
00:30:10.240 --> 00:30:10.549
>> No.
00:30:12.799 --> 00:30:13.110
>> So,
00:30:13.120 --> 00:30:15.029
>> can I host my own website inside of
00:30:15.039 --> 00:30:16.549
SharePoint?
00:30:16.559 --> 00:30:21.110
>> No. No. Uh so anyway, take a look at
00:30:21.120 --> 00:30:23.110
this. Don't I mean get excited. I think
00:30:23.120 --> 00:30:25.750
this is really cool. Uh it gives you
00:30:25.760 --> 00:30:27.750
some capabilities of breaking out of
00:30:27.760 --> 00:30:31.029
that, you know, web part structure of
00:30:31.039 --> 00:30:33.269
what SharePoint is and and you can do
00:30:33.279 --> 00:30:36.070
some cool stuff. So I think it is
00:30:36.080 --> 00:30:39.830
exciting. It of course has some
00:30:39.840 --> 00:30:41.750
framework around it so that you're not
00:30:41.760 --> 00:30:45.190
going to be doing some hacking and doing
00:30:45.200 --> 00:30:49.190
some you know uh suspicious behaviors
00:30:49.200 --> 00:30:51.590
some behaviors that might be uh
00:30:51.600 --> 00:30:53.830
detrimental to not just your site but
00:30:53.840 --> 00:30:57.750
also to the hosting platform of uh
00:30:57.760 --> 00:30:59.830
SharePoint itself. So Daniel, I think I
00:30:59.840 --> 00:31:01.430
think there's a direct connection here
00:31:01.440 --> 00:31:04.630
too with um what you're able to create
00:31:04.640 --> 00:31:06.549
and code and
00:31:06.559 --> 00:31:09.430
>> make within uh the co-pilot experience
00:31:09.440 --> 00:31:12.549
that these HTML artifacts as they're
00:31:12.559 --> 00:31:15.430
called in the anthropic space uh the
00:31:15.440 --> 00:31:17.350
example in that support article is
00:31:17.360 --> 00:31:19.510
here's an interactive page
00:31:19.520 --> 00:31:21.510
>> uh another way of presenting this
00:31:21.520 --> 00:31:23.990
content click through this report. I
00:31:24.000 --> 00:31:26.470
think, you know, it makes sense to be
00:31:26.480 --> 00:31:28.230
able to host it in SharePoint, uh,
00:31:28.240 --> 00:31:29.510
rather than it just being a
00:31:29.520 --> 00:31:30.070
>> absolutely
00:31:30.080 --> 00:31:31.510
>> a standalone thing.
00:31:31.520 --> 00:31:33.669
>> Yeah, absolutely. I mean, I I I think
00:31:33.679 --> 00:31:36.470
there's going to be some I' I'm really
00:31:36.480 --> 00:31:38.149
looking forward to seeing how people do
00:31:38.159 --> 00:31:40.789
this, how people use this functionality
00:31:40.799 --> 00:31:43.430
because you're right, there's, hey, I
00:31:43.440 --> 00:31:45.509
want to do this, but where would it
00:31:45.519 --> 00:31:48.389
live? And the answer might have been on
00:31:48.399 --> 00:31:50.630
a web server back in the day, but you
00:31:50.640 --> 00:31:52.710
know, we're not running web servers on
00:31:52.720 --> 00:31:55.350
prim anymore. I mean, some people do
00:31:55.360 --> 00:31:57.269
>> or download it and you have to run it
00:31:57.279 --> 00:31:59.029
locally from your own machine,
00:31:59.039 --> 00:32:00.389
>> right? No, no, no.
00:32:00.399 --> 00:32:03.269
>> Let's put it into SharePoint and let's
00:32:03.279 --> 00:32:05.750
put some framework around it. But I'm
00:32:05.760 --> 00:32:07.110
really looking forward to seeing how
00:32:07.120 --> 00:32:09.269
people do this uh and and make use of
00:32:09.279 --> 00:32:11.350
this. Uh I think it's going to be pretty
00:32:11.360 --> 00:32:13.029
cool.
00:32:13.039 --> 00:32:16.470
So, um, the roll out, you might be
00:32:16.480 --> 00:32:18.470
asking, public preview rollout will
00:32:18.480 --> 00:32:22.230
begin early October, so very soonish,
00:32:22.240 --> 00:32:24.470
>> and expect to be completed by, well,
00:32:24.480 --> 00:32:25.990
early October. So, it's one of those
00:32:26.000 --> 00:32:27.430
instant ones.
00:32:27.440 --> 00:32:30.070
>> General availability worldwide will be
00:32:30.080 --> 00:32:33.669
mid November through late December. So,
00:32:33.679 --> 00:32:36.630
nice holiday present. Um, so I think
00:32:36.640 --> 00:32:38.310
that'll be cool. Like I said, looking
00:32:38.320 --> 00:32:40.549
forward to seeing how people uh use this
00:32:40.559 --> 00:32:42.549
functionality.
00:32:42.559 --> 00:32:44.630
Darl,
00:32:44.640 --> 00:32:47.190
I'm I'm excited about this because I get
00:32:47.200 --> 00:32:48.710
questions all the time about where
00:32:48.720 --> 00:32:51.350
what's going to happen to this planner
00:32:51.360 --> 00:32:54.310
that uh gets created every time we have
00:32:54.320 --> 00:32:55.990
these meetings.
00:32:56.000 --> 00:32:58.710
>> Tell us how's this going to that going
00:32:58.720 --> 00:33:01.750
to be uh cleaned up. Sir,
00:33:01.760 --> 00:33:05.190
>> Microsoft Planner meeting created plans
00:33:05.200 --> 00:33:07.669
will expire after 180 days of
00:33:07.679 --> 00:33:12.230
inactivity. that is MC1479508.
00:33:12.240 --> 00:33:14.230
Now, this is referring to when you
00:33:14.240 --> 00:33:15.990
create meeting notes as part of your
00:33:16.000 --> 00:33:19.190
team's meeting. You can add an agenda.
00:33:19.200 --> 00:33:21.830
Um, below that you got an area for notes
00:33:21.840 --> 00:33:24.310
that you might take. And then there's a
00:33:24.320 --> 00:33:28.070
task table and uh if you add it before
00:33:28.080 --> 00:33:29.990
the meeting, cool. If you add it during
00:33:30.000 --> 00:33:31.750
the meeting, there it is in the side
00:33:31.760 --> 00:33:34.789
panel. But this is referring to the task
00:33:34.799 --> 00:33:36.549
list at the bottom. It's a simple
00:33:36.559 --> 00:33:39.029
looking table, but what it's doing in
00:33:39.039 --> 00:33:42.070
the background is creating a planner
00:33:42.080 --> 00:33:45.110
plan and synchronizing the simple
00:33:45.120 --> 00:33:47.669
details from that table into a planner
00:33:47.679 --> 00:33:51.669
plan. Um, it's disconnected from uh
00:33:51.679 --> 00:33:53.669
other plans that you might have that
00:33:53.679 --> 00:33:56.710
exist. Although sometime this month in
00:33:56.720 --> 00:33:59.590
the next few days apparently um we'll be
00:33:59.600 --> 00:34:03.190
able to connect this meeting created
00:34:03.200 --> 00:34:06.710
plan to an existing plan. This message
00:34:06.720 --> 00:34:09.669
is really dealing with uh the plans that
00:34:09.679 --> 00:34:11.589
are disconnected that aren't really been
00:34:11.599 --> 00:34:13.190
used anymore. They're just sitting out
00:34:13.200 --> 00:34:15.909
there uh cluttering up your planner
00:34:15.919 --> 00:34:17.990
experience. If they're not used within
00:34:18.000 --> 00:34:22.629
180 days then they will be expired. Uh I
00:34:22.639 --> 00:34:25.270
this is great. I do too. One thing I
00:34:25.280 --> 00:34:26.950
want to ask though under the what and
00:34:26.960 --> 00:34:29.829
why. Yes. The last sentence tasks in
00:34:29.839 --> 00:34:34.230
loop and meeting notes remain intact and
00:34:34.240 --> 00:34:35.430
accessible.
00:34:35.440 --> 00:34:37.510
>> I understand the meeting notes part.
00:34:37.520 --> 00:34:41.829
>> I do. Uh but the tasks in loop
00:34:41.839 --> 00:34:43.750
are going to be remain accessible even
00:34:43.760 --> 00:34:47.270
after this plan is deleted.
00:34:47.280 --> 00:34:48.550
>> Yeah.
00:34:48.560 --> 00:34:50.470
So I think how this will work Daniel
00:34:50.480 --> 00:34:52.550
because it's a table and that's what
00:34:52.560 --> 00:34:54.629
they say to say the referring to the
00:34:54.639 --> 00:34:56.550
list of tasks
00:34:56.560 --> 00:34:59.030
you know the task name who it's assigned
00:34:59.040 --> 00:35:01.750
to the the due date. I think all they're
00:35:01.760 --> 00:35:04.630
going to do is cut off that connection
00:35:04.640 --> 00:35:06.390
to this
00:35:06.400 --> 00:35:08.870
standalone plan
00:35:08.880 --> 00:35:10.870
expire the plan but you'll still have
00:35:10.880 --> 00:35:13.510
the table there and you can happily use
00:35:13.520 --> 00:35:15.270
that if you want to. But um it it's
00:35:15.280 --> 00:35:18.069
after 180 days of inactivity and I'd say
00:35:18.079 --> 00:35:21.750
there'd be quite a fair number of those
00:35:21.760 --> 00:35:24.069
types of plans that are inactive.
00:35:24.079 --> 00:35:24.870
>> Yep. Indeed.
00:35:24.880 --> 00:35:27.589
>> Yeah. So, this is really a short
00:35:27.599 --> 00:35:30.950
message, a tidy up uh function, but um
00:35:30.960 --> 00:35:32.310
I'm looking forward to the other one
00:35:32.320 --> 00:35:34.390
that we talked about a few shows ago,
00:35:34.400 --> 00:35:36.310
which allows us to put these tasks where
00:35:36.320 --> 00:35:38.710
they should be in an existing plan, you
00:35:38.720 --> 00:35:41.270
know, rather than this standalone thing.
00:35:41.280 --> 00:35:43.750
This particular feature roll out will
00:35:43.760 --> 00:35:47.030
begin early October and complete by mid
00:35:47.040 --> 00:35:49.030
October and it's for everybody generally
00:35:49.040 --> 00:35:50.550
available.
00:35:50.560 --> 00:35:53.190
That's it. Um that's the show too. I
00:35:53.200 --> 00:35:55.270
know we went a little over. We're just
00:35:55.280 --> 00:35:57.910
adding extra value all the time. But um
00:35:57.920 --> 00:35:59.670
we're glad to do that and thanks for
00:35:59.680 --> 00:36:00.710
joining us.
00:36:00.720 --> 00:36:03.190
>> Thank you so much everyone. We greatly
00:36:03.200 --> 00:36:05.670
appreciate it. We'll catch you next
00:36:05.680 --> 00:36:06.470
time.
00:36:06.480 --> 00:36:07.750
>> All right. Bye for now.
00:36:07.760 --> 00:36:10.760
>> Byebye.
Kind: captions
Language: en
00:00:00.320 --> 00:00:02.629
Hello everyone. Welcome to this week's
00:00:02.639 --> 00:00:06.309
episode of the 365 message center show.
00:00:06.319 --> 00:00:07.590
Even though Microsoft's trying to get
00:00:07.600 --> 00:00:10.549
rid of the 365 part everywhere,
00:00:10.559 --> 00:00:12.230
on this show we have quite a few
00:00:12.240 --> 00:00:16.230
messages. One is about how you can pay
00:00:16.240 --> 00:00:18.230
more for one drive. Everybody wants to
00:00:18.240 --> 00:00:19.670
do that, right?
00:00:19.680 --> 00:00:22.310
>> Yeah. Yeah. Um uh the other headline is
00:00:22.320 --> 00:00:25.349
of course the bringing of this new super
00:00:25.359 --> 00:00:30.310
app which is all about co-pilot co-work
00:00:30.320 --> 00:00:33.270
auto something it's all together. Yeah.
00:00:33.280 --> 00:00:35.590
Um we'll talk about that
00:00:35.600 --> 00:00:39.510
>> and we're going to cover HTML because
00:00:39.520 --> 00:00:41.670
who doesn't love a little bit of HTML?
00:00:41.680 --> 00:00:44.150
Well, SharePoint does or we're going to
00:00:44.160 --> 00:00:47.910
see t-shirts with SharePoint heart HTML.
00:00:47.920 --> 00:00:50.310
That and more. Stick around. Roll the
00:00:50.320 --> 00:01:03.430
intro.
00:01:03.440 --> 00:01:05.830
>> Why not? That would be great. Um, it's
00:01:05.840 --> 00:01:07.910
We love Linux, we love this, we love
00:01:07.920 --> 00:01:10.870
that. We love old school HTML.
00:01:10.880 --> 00:01:13.109
>> Yeah. So, we're going to cover that.
00:01:13.119 --> 00:01:16.070
Stick around because it's going to be
00:01:16.080 --> 00:01:18.390
toward the end of our show. uh we're
00:01:18.400 --> 00:01:20.950
going to talk about that. But as we talk
00:01:20.960 --> 00:01:24.230
about these messages, please jump into
00:01:24.240 --> 00:01:26.070
the comments if you're on YouTube and
00:01:26.080 --> 00:01:28.070
just leave your comment. We love we love
00:01:28.080 --> 00:01:30.390
reading those, interacting. If you're
00:01:30.400 --> 00:01:32.469
listening on the audio, you're out
00:01:32.479 --> 00:01:35.190
running, uh you're on the train
00:01:35.200 --> 00:01:37.830
listening, whatever. Hit us up on all
00:01:37.840 --> 00:01:40.630
the socials that matter, 365MCS,
00:01:40.640 --> 00:01:43.749
and and you know, type along. Say, "Oh,
00:01:43.759 --> 00:01:45.590
I liked what you said about that, Darl."
00:01:45.600 --> 00:01:48.710
Or Daniel, you are an idiot. Uh, sure,
00:01:48.720 --> 00:01:49.910
go ahead. Fine. Whatever.
00:01:49.920 --> 00:01:51.350
>> Do you do that though, Daniel? Like, do
00:01:51.360 --> 00:01:53.749
you listen to like a video podcast on
00:01:53.759 --> 00:01:55.749
YouTube or something and pause and go,
00:01:55.759 --> 00:01:57.190
I'm I'm going to jump in the comments
00:01:57.200 --> 00:01:59.749
right here. Time code. Here's what I've
00:01:59.759 --> 00:02:01.590
got to say. Do you do that
00:02:01.600 --> 00:02:02.950
>> every once in a while? If it's something
00:02:02.960 --> 00:02:05.510
that's like really
00:02:05.520 --> 00:02:07.350
>> uh if I want to be helpful.
00:02:07.360 --> 00:02:07.910
>> Yeah.
00:02:07.920 --> 00:02:09.190
>> You know, because if I'm making a
00:02:09.200 --> 00:02:10.710
comment about something that said,
00:02:10.720 --> 00:02:12.070
wouldn't it be great if there was a time
00:02:12.080 --> 00:02:13.990
code in there? I mean, but you can type
00:02:14.000 --> 00:02:15.030
it the time code, right?
00:02:15.040 --> 00:02:17.350
>> Oh, of course. Of course. Yeah. Just I I
00:02:17.360 --> 00:02:19.350
find it's funny when I do that sometimes
00:02:19.360 --> 00:02:21.750
and and I'm having a reaction or a
00:02:21.760 --> 00:02:23.990
thought or an idea and I share that and
00:02:24.000 --> 00:02:25.830
then I continue listening to the video
00:02:25.840 --> 00:02:27.510
or the podcast. Oh, they actually talk
00:02:27.520 --> 00:02:29.110
about this later. So,
00:02:29.120 --> 00:02:30.150
>> I look like a fool. But that's all
00:02:30.160 --> 00:02:32.309
right. I'll just leave it there cuz I
00:02:32.319 --> 00:02:32.949
am. So,
00:02:32.959 --> 00:02:34.710
>> yes, that's fine. Let's jump into it and
00:02:34.720 --> 00:02:37.589
let's get to these messages and tell all
00:02:37.599 --> 00:02:39.670
the peeps how Microsoft's just changing
00:02:39.680 --> 00:02:41.030
their world.
00:02:41.040 --> 00:02:43.110
>> Why not?
00:02:43.120 --> 00:02:44.470
First up,
00:02:44.480 --> 00:02:48.550
>> first up is one I alluded to straight
00:02:48.560 --> 00:02:51.830
off the top of the show. Microsoft One
00:02:51.840 --> 00:02:55.509
Drive new pay as you go storage billing
00:02:55.519 --> 00:03:01.270
option. This is MC1477185.
00:03:01.280 --> 00:03:03.830
So, this was the hey, you want to spend
00:03:03.840 --> 00:03:05.750
more money on one drive? Well, now
00:03:05.760 --> 00:03:10.070
you're going to get two. Uh, so this is,
00:03:10.080 --> 00:03:13.589
I think, one, you know, issue that
00:03:13.599 --> 00:03:15.270
organizations run into every once in a
00:03:15.280 --> 00:03:17.589
while, which is someone has a one drive
00:03:17.599 --> 00:03:22.470
and it's full. You can't add anymore and
00:03:22.480 --> 00:03:25.270
they what do what do you do with that?
00:03:25.280 --> 00:03:27.990
Well, one way is you could just spin up
00:03:28.000 --> 00:03:30.789
a SharePoint site and say, "Here's your
00:03:30.799 --> 00:03:33.509
new more storage over here in
00:03:33.519 --> 00:03:35.670
SharePoint.
00:03:35.680 --> 00:03:38.070
um could give you another one drive
00:03:38.080 --> 00:03:40.869
account I guess uh storage put it in
00:03:40.879 --> 00:03:43.030
teams whatever
00:03:43.040 --> 00:03:45.830
well that creates other entry points
00:03:45.840 --> 00:03:48.470
right and it's not all together so you
00:03:48.480 --> 00:03:52.309
might want to use uh this new pay as you
00:03:52.319 --> 00:03:55.509
go option for adding the additional
00:03:55.519 --> 00:03:58.070
storage to one drive now you might say
00:03:58.080 --> 00:03:59.910
Daniel you should be telling people they
00:03:59.920 --> 00:04:02.630
need to callull their information quit
00:04:02.640 --> 00:04:04.710
keeping all that old data uh
00:04:04.720 --> 00:04:06.710
>> blah blah blah. That is true. I agree
00:04:06.720 --> 00:04:09.830
with you. However, there are some times,
00:04:09.840 --> 00:04:13.110
especially temporarily, where
00:04:13.120 --> 00:04:15.030
there is,
00:04:15.040 --> 00:04:17.189
especially with levers,
00:04:17.199 --> 00:04:19.670
there's a bunch of data in someone's one
00:04:19.680 --> 00:04:23.189
drive. It needs to go somewhere. Okay,
00:04:23.199 --> 00:04:25.510
we're going to delete that one drive.
00:04:25.520 --> 00:04:29.590
So, manager or co-orker, you need to
00:04:29.600 --> 00:04:31.830
take on that data. It's like, well, I
00:04:31.840 --> 00:04:34.469
don't have time right now to do this
00:04:34.479 --> 00:04:35.990
immediately.
00:04:36.000 --> 00:04:38.710
So, give me that data, put it in my one
00:04:38.720 --> 00:04:40.469
drive, and then I'll go through it and
00:04:40.479 --> 00:04:42.150
delete stuff and blah blah blah blah.
00:04:42.160 --> 00:04:45.430
Well, you may exceed your storage then
00:04:45.440 --> 00:04:49.030
when as part of that process. Um, that's
00:04:49.040 --> 00:04:50.710
now is there other ways to handle that?
00:04:50.720 --> 00:04:52.870
Absolutely. But some people that's the
00:04:52.880 --> 00:04:54.629
way they do it, right? You take
00:04:54.639 --> 00:04:57.110
ownership of that content. Maybe that's
00:04:57.120 --> 00:04:59.030
the way you do it. Maybe maybe you do it
00:04:59.040 --> 00:05:03.110
a different way. But um this is that
00:05:03.120 --> 00:05:05.189
time I Yes, you should probably do this
00:05:05.199 --> 00:05:07.029
temporarily.
00:05:07.039 --> 00:05:08.790
If you've got too much data in your one
00:05:08.800 --> 00:05:10.469
drive,
00:05:10.479 --> 00:05:12.710
you probably need to to to callull it
00:05:12.720 --> 00:05:15.029
and get rid of the old stuff or move the
00:05:15.039 --> 00:05:16.150
stuff that's supposed to be in
00:05:16.160 --> 00:05:18.950
sharepoint and and being worked on with
00:05:18.960 --> 00:05:20.790
other people. Quit working out of your
00:05:20.800 --> 00:05:23.350
one drive like that. But you're going to
00:05:23.360 --> 00:05:29.670
be able to uh do this um and add that uh
00:05:29.680 --> 00:05:31.990
additional quota. So pay as you go,
00:05:32.000 --> 00:05:33.350
which means yes, you're going to have to
00:05:33.360 --> 00:05:35.350
pay for it.
00:05:35.360 --> 00:05:37.590
Uh there is an article where it talks
00:05:37.600 --> 00:05:40.790
about how you add more one drive and
00:05:40.800 --> 00:05:44.150
shareepoint storage, but um you can read
00:05:44.160 --> 00:05:45.670
that
00:05:45.680 --> 00:05:47.990
at your leisure.
00:05:48.000 --> 00:05:50.629
The rollout schedule public preview
00:05:50.639 --> 00:05:53.830
worldwide. The public preview is now
00:05:53.840 --> 00:05:55.990
available and then the general
00:05:56.000 --> 00:06:00.230
availability will be early November 2026
00:06:00.240 --> 00:06:02.390
and could be will be completed in early
00:06:02.400 --> 00:06:05.110
December. And this is for GCC, GCC high
00:06:05.120 --> 00:06:09.590
and DoD and everybody else. So, um,
00:06:09.600 --> 00:06:11.350
again, I hope you're using this
00:06:11.360 --> 00:06:15.749
temporarily and not in a way that is,
00:06:15.759 --> 00:06:19.350
uh, permanent for users, um, for the
00:06:19.360 --> 00:06:21.590
most part. So,
00:06:21.600 --> 00:06:23.510
Darl,
00:06:23.520 --> 00:06:26.870
uh, when you are, you know, going about
00:06:26.880 --> 00:06:28.710
and
00:06:28.720 --> 00:06:31.270
looking into how to add storage space to
00:06:31.280 --> 00:06:32.950
someone's one drive, you may do some
00:06:32.960 --> 00:06:36.230
research and put together a paper.
00:06:36.240 --> 00:06:39.909
Uh so tell us how that might that kind
00:06:39.919 --> 00:06:43.350
of p that process may be uh changing.
00:06:43.360 --> 00:06:45.749
Wait a minute. Sorry.
00:06:45.759 --> 00:06:46.790
>> Yeah.
00:06:46.800 --> 00:06:48.070
>> You know what we didn't do? You know how
00:06:48.080 --> 00:06:50.710
we like reorder the messages and I I
00:06:50.720 --> 00:06:52.309
kind of left it so that you're doing
00:06:52.319 --> 00:06:53.590
three in a row and I thought
00:06:53.600 --> 00:06:54.790
>> that was awesome.
00:06:54.800 --> 00:06:56.790
>> I better change that.
00:06:56.800 --> 00:06:58.309
>> Darl,
00:06:58.319 --> 00:07:01.589
>> uh tell us about this uh new update with
00:07:01.599 --> 00:07:03.670
co-pilot. how everything's coming
00:07:03.680 --> 00:07:06.230
together right now.
00:07:06.240 --> 00:07:07.990
>> Right. Right there. Yeah. Coming
00:07:08.000 --> 00:07:10.469
together like our show right now on the
00:07:10.479 --> 00:07:13.510
fly. Yeah. Um
00:07:13.520 --> 00:07:15.029
let's find the right message for that.
00:07:15.039 --> 00:07:19.909
It's uh I guess a recent drop um related
00:07:19.919 --> 00:07:23.430
to C-Pilot and we talked about it uh as
00:07:23.440 --> 00:07:25.350
a headline at the top of the show.
00:07:25.360 --> 00:07:28.469
Microsoft Copilot. The new ways to work
00:07:28.479 --> 00:07:31.510
across Microsoft Copilot and Microsoft
00:07:31.520 --> 00:07:33.830
365. How many times can you say
00:07:33.840 --> 00:07:38.950
Microsoft Copilot? This is MC147927.
00:07:38.960 --> 00:07:41.589
And yeah, look, you've heard Daniel and
00:07:41.599 --> 00:07:44.950
I joke about this on and off. Uh we know
00:07:44.960 --> 00:07:48.070
that the name was coming together, the
00:07:48.080 --> 00:07:50.550
apps are coming together, branding's
00:07:50.560 --> 00:07:52.870
coming together. Well, the app is coming
00:07:52.880 --> 00:07:54.869
together. And we had it you know rumored
00:07:54.879 --> 00:07:58.550
for a few months that Microsoft was
00:07:58.560 --> 00:08:01.110
working on this super app was another
00:08:01.120 --> 00:08:03.670
way of referring to it. What is it? It
00:08:03.680 --> 00:08:09.430
is uh we have had chat um with co-pilot
00:08:09.440 --> 00:08:12.309
and co-work as an experience. You can
00:08:12.319 --> 00:08:15.909
switch between the two. uh one is
00:08:15.919 --> 00:08:18.230
predominantly free and included and you
00:08:18.240 --> 00:08:21.110
can use various different models to work
00:08:21.120 --> 00:08:23.909
on a task. Ask it some questions, get it
00:08:23.919 --> 00:08:27.909
to do something for you, involve agents.
00:08:27.919 --> 00:08:29.430
And then there's co-work which is
00:08:29.440 --> 00:08:32.070
multitask doing many things, longer
00:08:32.080 --> 00:08:35.670
tasks, um thinks a bit longer and as
00:08:35.680 --> 00:08:38.389
we've been experiencing um there is some
00:08:38.399 --> 00:08:41.350
costs involved. what has been added to
00:08:41.360 --> 00:08:45.509
this uh unified app um which is I guess
00:08:45.519 --> 00:08:48.150
it's just called Microsoft Copilot now
00:08:48.160 --> 00:08:50.389
uh you'll go to
00:08:50.399 --> 00:08:52.870
office.com if that's your way of getting
00:08:52.880 --> 00:08:55.030
there uh it used to be known as
00:08:55.040 --> 00:08:57.269
m365.cloud.microsoft
00:08:57.279 --> 00:08:59.030
now it's copilot.cloud.microsoft
00:08:59.040 --> 00:09:00.710
cloud.microsoft
00:09:00.720 --> 00:09:03.910
and you'll also see uh the code
00:09:03.920 --> 00:09:05.590
experience
00:09:05.600 --> 00:09:09.190
and the autopilot experience.
00:09:09.200 --> 00:09:12.630
Um so the the home in co-pilot app uh
00:09:12.640 --> 00:09:15.030
will give you that co-pilot and co-work
00:09:15.040 --> 00:09:17.990
switching experience but the code part
00:09:18.000 --> 00:09:21.829
of it uh will allow you to I guess use
00:09:21.839 --> 00:09:24.070
uh an experience which is a bit more
00:09:24.080 --> 00:09:28.150
open in terms of defining what you want.
00:09:28.160 --> 00:09:31.430
uh so you know one level up from co-work
00:09:31.440 --> 00:09:33.829
uh people who have been using the
00:09:33.839 --> 00:09:35.750
anthropic experience will be quite
00:09:35.760 --> 00:09:37.430
familiar with this and this really is
00:09:37.440 --> 00:09:40.389
mirroring that uh it's just doing it in
00:09:40.399 --> 00:09:43.990
a Microsoft kind of way uh that you can
00:09:44.000 --> 00:09:47.509
code up apps you can u describe a bit
00:09:47.519 --> 00:09:49.190
more of what you want and it will
00:09:49.200 --> 00:09:50.710
programmatically
00:09:50.720 --> 00:09:53.750
uh achieve and and and do that task for
00:09:53.760 --> 00:09:57.509
you what we um Daniel and I you know
00:09:57.519 --> 00:09:59.509
reasonably new to this cuz it is a
00:09:59.519 --> 00:10:02.070
recently new announcement at the time of
00:10:02.080 --> 00:10:04.150
recording. So we haven't looked
00:10:04.160 --> 00:10:05.750
massively deeply into it. So we don't
00:10:05.760 --> 00:10:08.230
know the mechanisms for how this will
00:10:08.240 --> 00:10:11.030
work whether uh I think Daniel you were
00:10:11.040 --> 00:10:13.590
suggesting it might have to leverage uh
00:10:13.600 --> 00:10:17.030
GitHub uh in a space because it the code
00:10:17.040 --> 00:10:20.389
needs to have a place and an environment
00:10:20.399 --> 00:10:24.069
to create the the app itself and host it
00:10:24.079 --> 00:10:25.509
somewhere.
00:10:25.519 --> 00:10:27.670
>> Yeah. I
00:10:27.680 --> 00:10:29.750
That that is a question you know because
00:10:29.760 --> 00:10:32.069
when we talk about code we you know are
00:10:32.079 --> 00:10:35.509
we talking about actual code um so is
00:10:35.519 --> 00:10:39.509
this a GitHub kind of connection or is
00:10:39.519 --> 00:10:43.269
this more around coding of apps within
00:10:43.279 --> 00:10:47.590
the you know the power platform and M365
00:10:47.600 --> 00:10:51.430
experience right so don't know a whole
00:10:51.440 --> 00:10:55.590
lot yet uh about that so uh we'll see
00:10:55.600 --> 00:10:57.509
you know there wasn't any kind of up
00:10:57.519 --> 00:11:00.150
announcements around you know any
00:11:00.160 --> 00:11:03.350
connections into GitHub and you know the
00:11:03.360 --> 00:11:05.910
requirements for using GitHub enterprise
00:11:05.920 --> 00:11:08.389
or any we don't know and and that might
00:11:08.399 --> 00:11:11.269
not even be within the realm of this uh
00:11:11.279 --> 00:11:14.389
code functionality um but so it's still
00:11:14.399 --> 00:11:16.310
a question in my mind
00:11:16.320 --> 00:11:19.990
>> yeah uh the other uh addition is
00:11:20.000 --> 00:11:23.430
autopilot and this was known earlier as
00:11:23.440 --> 00:11:26.949
scout and its role uh is is a bit like
00:11:26.959 --> 00:11:30.389
the environment that that some early
00:11:30.399 --> 00:11:32.389
frontier people jumped on. You could
00:11:32.399 --> 00:11:34.630
download this automated experience but
00:11:34.640 --> 00:11:37.590
be running on your machine and uh much
00:11:37.600 --> 00:11:40.550
like code you can do a lot with it.
00:11:40.560 --> 00:11:43.269
There's you know a lot of possibilities.
00:11:43.279 --> 00:11:48.150
Um but Microsoft will run this in a a VM
00:11:48.160 --> 00:11:50.389
style way of working like it'll be a
00:11:50.399 --> 00:11:52.630
machine but it's kind of hosted. Uh, I
00:11:52.640 --> 00:11:54.310
think Daniel, you mentioned that one of
00:11:54.320 --> 00:11:58.310
the the limitations or the um friction
00:11:58.320 --> 00:12:00.150
points for adopting this was you did
00:12:00.160 --> 00:12:01.829
need to have a reasonably good machine
00:12:01.839 --> 00:12:06.069
to run uh Scout uh locally.
00:12:06.079 --> 00:12:08.710
>> Yeah. And I mean there was several setup
00:12:08.720 --> 00:12:10.629
steps that had to be done in an
00:12:10.639 --> 00:12:13.590
organization and on the laptop to enable
00:12:13.600 --> 00:12:17.509
it. Um, and so there was just friction
00:12:17.519 --> 00:12:21.350
uh to getting it. And so I would assume,
00:12:21.360 --> 00:12:22.870
just guessing, I don't know any
00:12:22.880 --> 00:12:24.069
information about this, but I would
00:12:24.079 --> 00:12:26.389
assume adoption was kind of low for it
00:12:26.399 --> 00:12:28.629
uh because of that.
00:12:28.639 --> 00:12:31.670
And you know, I will say this is
00:12:31.680 --> 00:12:33.509
another,
00:12:33.519 --> 00:12:36.870
you know, who thought of the the
00:12:36.880 --> 00:12:40.470
autopilot as the name for this? Yeah,
00:12:40.480 --> 00:12:43.030
>> because there's already a Microsoft
00:12:43.040 --> 00:12:44.470
autopilot.
00:12:44.480 --> 00:12:46.629
>> There's such a thing and it has nothing
00:12:46.639 --> 00:12:48.150
to do with AI.
00:12:48.160 --> 00:12:51.670
>> I mean, it it's it's basically a, you
00:12:51.680 --> 00:12:54.230
know, configuring Windows devices,
00:12:54.240 --> 00:12:56.550
>> you know, automatically. And so, and
00:12:56.560 --> 00:12:58.790
it's been around forever. So, they've
00:12:58.800 --> 00:13:01.269
now co-opted this and it's going to mean
00:13:01.279 --> 00:13:04.230
something totally different now. Um, so
00:13:04.240 --> 00:13:08.069
I I don't know. I whoever named this is
00:13:08.079 --> 00:13:12.310
um come on you know like you could
00:13:12.320 --> 00:13:13.829
anyway I I was about to say you could
00:13:13.839 --> 00:13:16.550
have stuck with scout
00:13:16.560 --> 00:13:20.150
anything else but reusing the same name.
00:13:20.160 --> 00:13:22.629
>> Yeah. Yeah. That that just um doesn't
00:13:22.639 --> 00:13:24.710
help with the the confusion. There is a
00:13:24.720 --> 00:13:27.750
a good blog post that steps through a
00:13:27.760 --> 00:13:31.350
lot of uh the detail. Um, but there is a
00:13:31.360 --> 00:13:33.030
lot of
00:13:33.040 --> 00:13:35.750
vision setting and marketing speak that
00:13:35.760 --> 00:13:37.910
you'll have to get around. Uh, maybe try
00:13:37.920 --> 00:13:41.750
what Daniel did um, himself uh, and get
00:13:41.760 --> 00:13:43.910
co-pilot to look at this page, but then
00:13:43.920 --> 00:13:46.069
explain it like a 12 year old to as if
00:13:46.079 --> 00:13:48.550
he was a 12-year-old and remove the
00:13:48.560 --> 00:13:50.389
marketing speak and you'll get down to
00:13:50.399 --> 00:13:52.310
just the bullet points of what has
00:13:52.320 --> 00:13:54.710
actually changed, what has actually um,
00:13:54.720 --> 00:13:58.470
been uh, pulled together here. Um here's
00:13:58.480 --> 00:14:00.949
like there's a screenshot here. I know
00:14:00.959 --> 00:14:04.150
audio listeners won't um see this but
00:14:04.160 --> 00:14:06.150
that the the vision for what that will
00:14:06.160 --> 00:14:09.910
look like. Um today we have chat and
00:14:09.920 --> 00:14:11.829
co-work as a switch over on the lefth
00:14:11.839 --> 00:14:14.710
hand panel. Now home is going to be that
00:14:14.720 --> 00:14:17.189
unified experience. You'll see the the
00:14:17.199 --> 00:14:19.110
choice between chat and co-work will be
00:14:19.120 --> 00:14:21.910
in the chat box as you start your
00:14:21.920 --> 00:14:24.230
conversation. uh whereas you can switch
00:14:24.240 --> 00:14:27.030
between code and autopilot in that panel
00:14:27.040 --> 00:14:30.389
and you know one concern I had when I
00:14:30.399 --> 00:14:32.790
heard about this coming was okay chat
00:14:32.800 --> 00:14:36.790
and co-work um you do when you choose to
00:14:36.800 --> 00:14:38.230
work in the co-work space if it's
00:14:38.240 --> 00:14:41.509
available to you uh you go back to this
00:14:41.519 --> 00:14:44.550
uh again after a day or so and ask it
00:14:44.560 --> 00:14:46.069
another question it'll still be in
00:14:46.079 --> 00:14:49.189
co-work so keep in mind what you are
00:14:49.199 --> 00:14:50.949
actually using and whether it's the
00:14:50.959 --> 00:14:53.990
right tool cuz it could cost you. Um,
00:14:54.000 --> 00:14:54.870
>> yeah, absolutely.
00:14:54.880 --> 00:14:57.269
>> Yeah. Yeah. So, there's a lot more to to
00:14:57.279 --> 00:14:59.430
look at. Um,
00:14:59.440 --> 00:15:01.350
and I'm sure there are people that are
00:15:01.360 --> 00:15:03.509
covering this in in greater depth. A
00:15:03.519 --> 00:15:05.030
friend or two I can see have already
00:15:05.040 --> 00:15:06.710
published videos stepping through and
00:15:06.720 --> 00:15:08.949
giving their reaction. So, uh, maybe
00:15:08.959 --> 00:15:12.150
we'll leave some links to that in the
00:15:12.160 --> 00:15:15.990
description of this video. Um, but when
00:15:16.000 --> 00:15:19.509
will this arrive? Uh, let's, uh, jump on
00:15:19.519 --> 00:15:22.629
in.
00:15:22.639 --> 00:15:25.269
Wow. Okay. Where is it?
00:15:25.279 --> 00:15:28.389
Somewhere here in this message.
00:15:28.399 --> 00:15:31.350
Is it just a a marketing message filled
00:15:31.360 --> 00:15:35.110
with stuff and no dates?
00:15:35.120 --> 00:15:36.230
>> Am I right, Daniel?
00:15:36.240 --> 00:15:37.990
>> Coming soon.
00:15:38.000 --> 00:15:40.389
>> Coming soon. Okay.
00:15:40.399 --> 00:15:43.910
>> Well, it's coming to um Frontier, right?
00:15:43.920 --> 00:15:48.629
first uh for the autopilot and
00:15:48.639 --> 00:15:53.430
>> um so but I don't know when it's if they
00:15:53.440 --> 00:15:55.350
put a date it's like next month
00:15:55.360 --> 00:15:57.269
>> it's in the summary right at the top
00:15:57.279 --> 00:15:58.949
rollouts roll out
00:15:58.959 --> 00:15:59.910
>> October yeah
00:15:59.920 --> 00:16:03.350
>> begin in October so there are individual
00:16:03.360 --> 00:16:05.670
roll outs for I guess the the various
00:16:05.680 --> 00:16:08.949
different functions and capabilities
00:16:08.959 --> 00:16:10.710
>> sorry about that um but
00:16:10.720 --> 00:16:12.710
>> well it's it's rolling out you know
00:16:12.720 --> 00:16:18.790
Frontier here um for the so co-work
00:16:18.800 --> 00:16:21.189
change is is rolling out in in October
00:16:21.199 --> 00:16:25.030
for everybody you know that has that the
00:16:25.040 --> 00:16:29.990
um frontier in October for um some of
00:16:30.000 --> 00:16:31.749
that you can read right
00:16:31.759 --> 00:16:33.590
>> oh yeah yeah it's under each of the
00:16:33.600 --> 00:16:35.670
sections here in the messages code it
00:16:35.680 --> 00:16:39.030
says Frontier later this month
00:16:39.040 --> 00:16:42.150
>> um autopilot we'll update this message
00:16:42.160 --> 00:16:44.389
when we've got some roll out timings,
00:16:44.399 --> 00:16:45.030
>> right?
00:16:45.040 --> 00:16:47.829
>> Oh, fantastic. Yeah. So, yeah, there's a
00:16:47.839 --> 00:16:49.509
lot to lot to get to grips with.
00:16:49.519 --> 00:16:52.870
Apparently, it's a big deal. Yeah. Um,
00:16:52.880 --> 00:16:54.470
you know, something else that we think
00:16:54.480 --> 00:16:56.790
is a a big deal. I think it's actually
00:16:56.800 --> 00:17:00.069
part of the the backstory for this, but
00:17:00.079 --> 00:17:02.230
um, there's some changes happening to
00:17:02.240 --> 00:17:04.150
researcher and how that's being
00:17:04.160 --> 00:17:06.069
positioned.
00:17:06.079 --> 00:17:09.350
>> Indeed. So, this is Microsoft 365
00:17:09.360 --> 00:17:11.590
copilot. Although isn't that changed now
00:17:11.600 --> 00:17:14.549
to just Microsoft Copilot? Microsoft 365
00:17:14.559 --> 00:17:16.949
copot updates to the researcher
00:17:16.959 --> 00:17:22.069
experience MC1476269.
00:17:22.079 --> 00:17:25.270
The research is
00:17:25.280 --> 00:17:29.430
uh a really cool experience I think for
00:17:29.440 --> 00:17:32.070
doing research, but also it has
00:17:32.080 --> 00:17:33.669
capabilities and we covered on the show
00:17:33.679 --> 00:17:37.110
a while back about using the different
00:17:37.120 --> 00:17:41.909
types of LLMs to your advantage and
00:17:41.919 --> 00:17:45.830
having that experience of um doing that
00:17:45.840 --> 00:17:48.950
comparison uh and and helping each other
00:17:48.960 --> 00:17:51.110
out and it it's just a really cool
00:17:51.120 --> 00:17:53.990
experience. in research, but it also has
00:17:54.000 --> 00:17:56.150
in researcher you're able to save
00:17:56.160 --> 00:17:57.669
prompts
00:17:57.679 --> 00:18:00.789
uh that you have put in it so that you
00:18:00.799 --> 00:18:03.190
can just come back and rerun those uh
00:18:03.200 --> 00:18:05.029
doing research over and over again, you
00:18:05.039 --> 00:18:09.430
know, based upon new stuff. Um a history
00:18:09.440 --> 00:18:12.470
tab, you know, um and then there's this
00:18:12.480 --> 00:18:13.990
really cool functionality where you say,
00:18:14.000 --> 00:18:15.430
"Hey, I want to do this research." And
00:18:15.440 --> 00:18:16.789
it says, "Okay, I'm gathering some
00:18:16.799 --> 00:18:19.110
stuff, but how long do you want this to
00:18:19.120 --> 00:18:22.390
be? Do you want this report to be one to
00:18:22.400 --> 00:18:25.270
three pages? You know, giving you a how
00:18:25.280 --> 00:18:27.270
big of a report are you actually looking
00:18:27.280 --> 00:18:30.310
for? Well, Microsoft's changing and this
00:18:30.320 --> 00:18:34.310
is part of the um really I I think part
00:18:34.320 --> 00:18:37.350
of all of these moves. One is that
00:18:37.360 --> 00:18:40.150
they're really wanting to bring the
00:18:40.160 --> 00:18:42.630
researcher experience
00:18:42.640 --> 00:18:46.070
um navigation out. Like so now you have
00:18:46.080 --> 00:18:48.710
to click on and click researcher and it
00:18:48.720 --> 00:18:50.230
brings in this new experience. Well,
00:18:50.240 --> 00:18:52.310
they're going to bring researcher
00:18:52.320 --> 00:18:54.710
functionality just to co-pilot, right?
00:18:54.720 --> 00:18:58.310
So you don't go out to researcher is
00:18:58.320 --> 00:19:00.789
just going to do it. Now how you call
00:19:00.799 --> 00:19:02.310
it, I don't know.
00:19:02.320 --> 00:19:04.150
>> You know, are you just going to do the
00:19:04.160 --> 00:19:06.549
drop down and say researcher as a
00:19:06.559 --> 00:19:08.549
knowledge? I I don't know
00:19:08.559 --> 00:19:09.669
>> because they don't tell us in the
00:19:09.679 --> 00:19:11.190
message and they don't give us a blog
00:19:11.200 --> 00:19:12.310
post and they don't give us a
00:19:12.320 --> 00:19:17.110
screenshot. So, we have no idea. Um, but
00:19:17.120 --> 00:19:19.110
basically they're going to remove all of
00:19:19.120 --> 00:19:22.630
that functionality that makes it the UI
00:19:22.640 --> 00:19:24.710
kind of unique to researcher because
00:19:24.720 --> 00:19:27.190
it's not going to be its own UI anymore.
00:19:27.200 --> 00:19:28.870
>> So, they're going to they are going to
00:19:28.880 --> 00:19:30.390
remove that functionality. I talked
00:19:30.400 --> 00:19:32.710
about the report length. It's just going
00:19:32.720 --> 00:19:35.029
to kind of guess what you should have
00:19:35.039 --> 00:19:39.110
based upon what you've inputed. Um,
00:19:39.120 --> 00:19:40.789
>> you're not going to have the support uh
00:19:40.799 --> 00:19:44.070
the the uh saved prompts tab. You're not
00:19:44.080 --> 00:19:45.430
going to have the history tab. Not going
00:19:45.440 --> 00:19:47.270
to have the reports tab, the explore
00:19:47.280 --> 00:19:49.830
tab, or the recommended prompts. All of
00:19:49.840 --> 00:19:51.909
that's going to be retired.
00:19:51.919 --> 00:19:56.070
So, you know, I hope we can still keep
00:19:56.080 --> 00:19:57.909
the comparison
00:19:57.919 --> 00:20:00.710
uh may hopefully between, you know, the
00:20:00.720 --> 00:20:03.990
anthropic and the GPT models and and
00:20:04.000 --> 00:20:06.950
giving you so they can help each other.
00:20:06.960 --> 00:20:11.110
I don't know. But um it's all being
00:20:11.120 --> 00:20:13.510
consolidated into the co-pilot
00:20:13.520 --> 00:20:14.870
experience.
00:20:14.880 --> 00:20:17.590
>> Yeah, Daniel, I think um maybe we'll
00:20:17.600 --> 00:20:19.510
have to describe these things that we
00:20:19.520 --> 00:20:22.789
want within the prompt. Um, and I I
00:20:22.799 --> 00:20:24.310
suggest I don't know what this
00:20:24.320 --> 00:20:26.230
experience will be like, but I suggest
00:20:26.240 --> 00:20:32.390
that um you you do ask researcher when
00:20:32.400 --> 00:20:33.990
actually let me back up a bit that we do
00:20:34.000 --> 00:20:35.990
have a small clue as to what this looks
00:20:36.000 --> 00:20:38.950
like. In the chat box, you can add
00:20:38.960 --> 00:20:41.430
content the plus button. And I think
00:20:41.440 --> 00:20:43.590
it's like adding a skill like when you
00:20:43.600 --> 00:20:45.430
can say, "Hey, I want to add the Excel
00:20:45.440 --> 00:20:47.430
skill." Uh, you'll add the researcher
00:20:47.440 --> 00:20:51.110
skill. Um, and maybe uh you can say,
00:20:51.120 --> 00:20:52.950
"Look, ask me some questions, some
00:20:52.960 --> 00:20:55.350
clarifying questions before we get into
00:20:55.360 --> 00:20:58.070
doing the actual research." But it feels
00:20:58.080 --> 00:21:00.070
like the weight of that isn't the way
00:21:00.080 --> 00:21:02.149
that you prompt again.
00:21:02.159 --> 00:21:06.470
>> Yep. So the And you could do that now in
00:21:06.480 --> 00:21:09.029
chat. You can go and say plus you could
00:21:09.039 --> 00:21:11.909
say add capabilities and click on
00:21:11.919 --> 00:21:14.230
research a topic. And so that you could
00:21:14.240 --> 00:21:16.950
do that now. And I'm assuming again, we
00:21:16.960 --> 00:21:18.149
don't have any screenshots, we don't
00:21:18.159 --> 00:21:20.070
have any blog posts, we don't have I'm
00:21:20.080 --> 00:21:22.310
assuming that they just mean that's the
00:21:22.320 --> 00:21:24.310
way you're going to call researcher
00:21:24.320 --> 00:21:25.510
>> and that's going to be the only thing.
00:21:25.520 --> 00:21:27.110
You're not going to be able to, you
00:21:27.120 --> 00:21:29.669
know, pop out and and under agents click
00:21:29.679 --> 00:21:33.350
on researcher. Um,
00:21:33.360 --> 00:21:35.590
which is fine, but if you use that
00:21:35.600 --> 00:21:38.470
history tab or the save tab of your the
00:21:38.480 --> 00:21:40.630
prompts that you've done,
00:21:40.640 --> 00:21:43.029
>> uh, you know, that's not that's not fun.
00:21:43.039 --> 00:21:46.470
uh you're losing that. Um the explore
00:21:46.480 --> 00:21:49.350
which gave you kind of the the explore
00:21:49.360 --> 00:21:53.270
tab which was uh is still a way for you
00:21:53.280 --> 00:21:56.549
to get ideas as to how you know what you
00:21:56.559 --> 00:21:58.390
can research and how you could use that.
00:21:58.400 --> 00:22:01.270
Now I also could see and I don't know
00:22:01.280 --> 00:22:04.390
anything about this and no NDAs or
00:22:04.400 --> 00:22:06.710
anything. I haven't been told anything,
00:22:06.720 --> 00:22:10.149
but um if you think about it,
00:22:10.159 --> 00:22:11.669
researcher,
00:22:11.679 --> 00:22:13.909
it's going and doing more complex stuff
00:22:13.919 --> 00:22:16.789
than a regular co-pilot chat.
00:22:16.799 --> 00:22:19.590
And it actually is kind of close,
00:22:19.600 --> 00:22:21.510
depending on how you look at it, to what
00:22:21.520 --> 00:22:23.750
co-work can do. M
00:22:23.760 --> 00:22:25.590
>> and so
00:22:25.600 --> 00:22:28.710
I wouldn't you know it wouldn't shock me
00:22:28.720 --> 00:22:32.549
if later down the road researcher is
00:22:32.559 --> 00:22:34.390
something they say that's more of a
00:22:34.400 --> 00:22:36.630
co-work thing or it's more of a you need
00:22:36.640 --> 00:22:39.190
to pay extra to use it. Um
00:22:39.200 --> 00:22:41.909
>> I I don't know they could still keep it
00:22:41.919 --> 00:22:44.230
there. I'm just saying I that's kind of
00:22:44.240 --> 00:22:46.710
a feeling when they start making changes
00:22:46.720 --> 00:22:50.549
like this and making it not as special,
00:22:50.559 --> 00:22:52.710
you know, removing the navigation. I
00:22:52.720 --> 00:22:54.470
don't know. It just kind of
00:22:54.480 --> 00:22:56.710
>> seems
00:22:56.720 --> 00:22:58.789
>> seems interesting. So, that's just the
00:22:58.799 --> 00:23:01.669
way I'll put it. So, roll out schedule.
00:23:01.679 --> 00:23:03.430
Well, it's not really rollout. It's
00:23:03.440 --> 00:23:06.950
retirement. Uh worldwide GCC and GCC
00:23:06.960 --> 00:23:10.149
high beginning October 21st
00:23:10.159 --> 00:23:12.070
and then expected to be completed by
00:23:12.080 --> 00:23:16.149
December 30th of this year. And it does
00:23:16.159 --> 00:23:18.950
say it's gradually rolling out and users
00:23:18.960 --> 00:23:21.750
in the same environment in your
00:23:21.760 --> 00:23:24.470
organization may see it different. You
00:23:24.480 --> 00:23:27.270
may have different, you know, one person
00:23:27.280 --> 00:23:29.830
sees it in the navigation, one person
00:23:29.840 --> 00:23:33.190
doesn't, you know. Um, so that's going
00:23:33.200 --> 00:23:37.110
to be fun, you know, for
00:23:37.120 --> 00:23:38.070
>> Yeah.
00:23:38.080 --> 00:23:41.350
>> Anyway, let's talk about more fun, Darl.
00:23:41.360 --> 00:23:45.590
And fun. You know what is fun is when
00:23:45.600 --> 00:23:47.590
I'm writing emails and all the
00:23:47.600 --> 00:23:50.870
squigglies are showing up in my emails.
00:23:50.880 --> 00:23:52.070
>> Squiggies.
00:23:52.080 --> 00:23:53.669
>> Yeah. You know, squiggly saying, "Hey,
00:23:53.679 --> 00:23:55.510
you misspelled this." Or, "Oh, yeah.
00:23:55.520 --> 00:23:57.750
>> Are you sure that's the proper grammar?"
00:23:57.760 --> 00:23:59.909
That's what I call the blue squiggly.
00:23:59.919 --> 00:24:03.190
>> Uh, tell us how we might be able to, you
00:24:03.200 --> 00:24:06.070
know, not not use that anymore if maybe
00:24:06.080 --> 00:24:08.149
a new capability or
00:24:08.159 --> 00:24:09.990
>> maybe it's not new. Maybe it's something
00:24:10.000 --> 00:24:10.789
we've had before.
00:24:10.799 --> 00:24:12.870
>> Doesn't feel new. just feels like it's
00:24:12.880 --> 00:24:14.390
rephrased.
00:24:14.400 --> 00:24:17.190
Spell check before sending emails in new
00:24:17.200 --> 00:24:20.310
Outlook. Or maybe it was an old Outlook.
00:24:20.320 --> 00:24:21.669
That's not part of the title, by the
00:24:21.679 --> 00:24:24.630
way. MC1479509.
00:24:24.640 --> 00:24:26.390
Daniel's right. I feel like this was
00:24:26.400 --> 00:24:28.710
something that was available in Outlook
00:24:28.720 --> 00:24:31.510
98. And it was a tick box that said,
00:24:31.520 --> 00:24:33.669
"Check my spelling and grammar before I
00:24:33.679 --> 00:24:36.310
send this message." Uh, and it would
00:24:36.320 --> 00:24:37.830
take you through that and show you what
00:24:37.840 --> 00:24:39.590
it found. Now, we've become so
00:24:39.600 --> 00:24:42.310
accustomed to seeing the squigglies, the
00:24:42.320 --> 00:24:44.789
red underline and the blue underline
00:24:44.799 --> 00:24:47.830
that interrupt us. I'm getting into an
00:24:47.840 --> 00:24:51.110
impassion topic here. Interrupt our flow
00:24:51.120 --> 00:24:53.269
because we Oh, got to get rid of the
00:24:53.279 --> 00:24:55.350
lines. Right click, choose the correct
00:24:55.360 --> 00:24:57.029
word. Right click, choose the correct
00:24:57.039 --> 00:25:01.350
grammar. Uh, I think this feature, the
00:25:01.360 --> 00:25:04.710
return of this feature, uh, will help
00:25:04.720 --> 00:25:08.230
some of us maybe, um, get back into the
00:25:08.240 --> 00:25:11.510
flow of writing that email and then
00:25:11.520 --> 00:25:13.590
going through and checking for spelling,
00:25:13.600 --> 00:25:16.549
grammar before we go through the the
00:25:16.559 --> 00:25:19.190
actual sending of the message. So, this
00:25:19.200 --> 00:25:21.830
um, uh, let's see, it's uh, how does
00:25:21.840 --> 00:25:24.149
this actually work? Um, what will
00:25:24.159 --> 00:25:26.710
happen? Users will configure this to to
00:25:26.720 --> 00:25:28.630
check spelling and grammar before the
00:25:28.640 --> 00:25:32.310
email is sent. Um, it will
00:25:32.320 --> 00:25:33.669
well, yeah, it's going to reduce the
00:25:33.679 --> 00:25:35.909
spelling mistakes. If if you aren't
00:25:35.919 --> 00:25:38.070
already ignoring the red lines and blue
00:25:38.080 --> 00:25:40.149
lines, some people do. They're like, I'm
00:25:40.159 --> 00:25:42.149
so important. I don't have time to go
00:25:42.159 --> 00:25:43.909
back and correct this stuff. They'll
00:25:43.919 --> 00:25:47.110
figure it out. Um, but yeah, what I like
00:25:47.120 --> 00:25:50.070
about it, Daniel, is uh that as you're
00:25:50.080 --> 00:25:52.070
sending it, going through and checking
00:25:52.080 --> 00:25:56.630
these things as a last uh hurrah before
00:25:56.640 --> 00:25:59.590
the message goes off, um you'll still
00:25:59.600 --> 00:26:01.350
look professional because you've you've
00:26:01.360 --> 00:26:03.269
managed to to fix these things.
00:26:03.279 --> 00:26:04.549
>> Mhm. Indeed.
00:26:04.559 --> 00:26:05.590
>> Yeah.
00:26:05.600 --> 00:26:09.750
>> Um when is this arriving?
00:26:09.760 --> 00:26:13.510
It is uh oo there's a breakdown of five
00:26:13.520 --> 00:26:15.029
delivery times generally available
00:26:15.039 --> 00:26:17.990
worldwide begin mid November and
00:26:18.000 --> 00:26:20.789
complete by early December targeted
00:26:20.799 --> 00:26:22.070
release worldwide. Why are they doing
00:26:22.080 --> 00:26:24.870
that in that order
00:26:24.880 --> 00:26:27.190
come out in October
00:26:27.200 --> 00:26:29.669
just so you know before generally
00:26:29.679 --> 00:26:32.230
available as it usually would be um and
00:26:32.240 --> 00:26:34.470
complete by late October. So yeah,
00:26:34.480 --> 00:26:37.669
generally available for GCC November,
00:26:37.679 --> 00:26:41.909
December, GCC high November. This is
00:26:41.919 --> 00:26:44.070
weird guys. Come on, man. You would
00:26:44.080 --> 00:26:47.830
normally say GCC GCC high and DoD roll
00:26:47.840 --> 00:26:50.470
out mid November through to mid
00:26:50.480 --> 00:26:53.590
December. Anyway, I've corrected that.
00:26:53.600 --> 00:26:55.750
Maybe you should have used another kind
00:26:55.760 --> 00:26:57.029
of
00:26:57.039 --> 00:26:59.909
>> message format and sense check before
00:26:59.919 --> 00:27:02.549
you save this message and publish it. M
00:27:02.559 --> 00:27:04.230
>> that would be a great feature to build
00:27:04.240 --> 00:27:07.269
into your checking. Um but let's move
00:27:07.279 --> 00:27:09.830
into something else that feels like old
00:27:09.840 --> 00:27:12.549
school but um is actually mixed with new
00:27:12.559 --> 00:27:15.590
school HTML. Tell us Daniel what's
00:27:15.600 --> 00:27:16.710
happening.
00:27:16.720 --> 00:27:19.830
>> SharePoint HTML pages.
00:27:19.840 --> 00:27:21.190
>> Oh fantastic.
00:27:21.200 --> 00:27:27.110
>> I like short titles. MC1479517.
00:27:27.120 --> 00:27:30.470
So we talked a little bit about uh
00:27:30.480 --> 00:27:35.269
co-pilot in SharePoint which is now GA
00:27:35.279 --> 00:27:39.669
by the way. So the AI in SharePoint, you
00:27:39.679 --> 00:27:41.190
know, having Copilot in SharePoint,
00:27:41.200 --> 00:27:44.070
having uh the capabilities, it's
00:27:44.080 --> 00:27:46.310
fantastic. And one of those capabilities
00:27:46.320 --> 00:27:50.149
is you could generate an HTML page with
00:27:50.159 --> 00:27:54.630
Copilot that is uh based upon data that
00:27:54.640 --> 00:27:56.070
you have in your, you know, in a
00:27:56.080 --> 00:27:58.389
SharePoint list and it'll render a
00:27:58.399 --> 00:28:02.310
report and look pretty snazzy. Well, now
00:28:02.320 --> 00:28:04.549
we can also
00:28:04.559 --> 00:28:08.710
uh create a regular HTML page and going
00:28:08.720 --> 00:28:11.909
to the new button and click new and give
00:28:11.919 --> 00:28:17.510
me an HTML. We can also upload HTML page
00:28:17.520 --> 00:28:20.710
into our SharePoint site. And when we do
00:28:20.720 --> 00:28:23.269
that, we can edit it. We can edit the
00:28:23.279 --> 00:28:27.029
HTML page. We can we can share it out
00:28:27.039 --> 00:28:30.470
like we can other types of content in
00:28:30.480 --> 00:28:32.549
SharePoint.
00:28:32.559 --> 00:28:37.110
There I will state there is one link in
00:28:37.120 --> 00:28:40.710
this update and it's toward the bottom.
00:28:40.720 --> 00:28:45.190
says review and it's uh a page on the
00:28:45.200 --> 00:28:48.630
support site called uh create edit
00:28:48.640 --> 00:28:52.870
publish HTML pages or create upload edit
00:28:52.880 --> 00:28:54.870
publish anyway
00:28:54.880 --> 00:28:57.510
uh so you know it kind of walks you
00:28:57.520 --> 00:28:59.590
through how you could do that. The
00:28:59.600 --> 00:29:01.269
really important part that I kind of
00:29:01.279 --> 00:29:04.470
wanted to focus on is toward the bottom
00:29:04.480 --> 00:29:06.789
um there is a frequently asked questions
00:29:06.799 --> 00:29:08.789
and the first question is what can I do
00:29:08.799 --> 00:29:11.990
with an HTML page in SharePoint and then
00:29:12.000 --> 00:29:14.470
it lists in a table format all the
00:29:14.480 --> 00:29:16.789
little things you know the things you
00:29:16.799 --> 00:29:19.430
might think an HTML page would do and
00:29:19.440 --> 00:29:22.149
does it support it. So things like
00:29:22.159 --> 00:29:26.310
outbound API calls, no
00:29:26.320 --> 00:29:31.430
CDN scripts, no. Uh you know, SharePoint
00:29:31.440 --> 00:29:36.470
app and teams on a mobile, no promote to
00:29:36.480 --> 00:29:40.230
news post, no you know. Anyway, so look
00:29:40.240 --> 00:29:43.750
at this. You can think of uh you know,
00:29:43.760 --> 00:29:46.149
hey, can if I'm going to upload this
00:29:46.159 --> 00:29:47.990
HTML, can it do this? Can it do that?
00:29:48.000 --> 00:29:51.029
Well, here is a table that tells you a
00:29:51.039 --> 00:29:55.269
lot. And if you um if it doesn't answer
00:29:55.279 --> 00:29:57.510
it, then you can give feedback here and
00:29:57.520 --> 00:29:59.669
maybe they'll keep editing, you know,
00:29:59.679 --> 00:30:03.669
this uh this table with items from
00:30:03.679 --> 00:30:07.830
people saying, "Hey, can I do live data
00:30:07.840 --> 00:30:10.230
sharing with this HTML page?"
00:30:10.240 --> 00:30:10.549
>> No.
00:30:12.799 --> 00:30:13.110
>> So,
00:30:13.120 --> 00:30:15.029
>> can I host my own website inside of
00:30:15.039 --> 00:30:16.549
SharePoint?
00:30:16.559 --> 00:30:21.110
>> No. No. Uh so anyway, take a look at
00:30:21.120 --> 00:30:23.110
this. Don't I mean get excited. I think
00:30:23.120 --> 00:30:25.750
this is really cool. Uh it gives you
00:30:25.760 --> 00:30:27.750
some capabilities of breaking out of
00:30:27.760 --> 00:30:31.029
that, you know, web part structure of
00:30:31.039 --> 00:30:33.269
what SharePoint is and and you can do
00:30:33.279 --> 00:30:36.070
some cool stuff. So I think it is
00:30:36.080 --> 00:30:39.830
exciting. It of course has some
00:30:39.840 --> 00:30:41.750
framework around it so that you're not
00:30:41.760 --> 00:30:45.190
going to be doing some hacking and doing
00:30:45.200 --> 00:30:49.190
some you know uh suspicious behaviors
00:30:49.200 --> 00:30:51.590
some behaviors that might be uh
00:30:51.600 --> 00:30:53.830
detrimental to not just your site but
00:30:53.840 --> 00:30:57.750
also to the hosting platform of uh
00:30:57.760 --> 00:30:59.830
SharePoint itself. So Daniel, I think I
00:30:59.840 --> 00:31:01.430
think there's a direct connection here
00:31:01.440 --> 00:31:04.630
too with um what you're able to create
00:31:04.640 --> 00:31:06.549
and code and
00:31:06.559 --> 00:31:09.430
>> make within uh the co-pilot experience
00:31:09.440 --> 00:31:12.549
that these HTML artifacts as they're
00:31:12.559 --> 00:31:15.430
called in the anthropic space uh the
00:31:15.440 --> 00:31:17.350
example in that support article is
00:31:17.360 --> 00:31:19.510
here's an interactive page
00:31:19.520 --> 00:31:21.510
>> uh another way of presenting this
00:31:21.520 --> 00:31:23.990
content click through this report. I
00:31:24.000 --> 00:31:26.470
think, you know, it makes sense to be
00:31:26.480 --> 00:31:28.230
able to host it in SharePoint, uh,
00:31:28.240 --> 00:31:29.510
rather than it just being a
00:31:29.520 --> 00:31:30.070
>> absolutely
00:31:30.080 --> 00:31:31.510
>> a standalone thing.
00:31:31.520 --> 00:31:33.669
>> Yeah, absolutely. I mean, I I I think
00:31:33.679 --> 00:31:36.470
there's going to be some I' I'm really
00:31:36.480 --> 00:31:38.149
looking forward to seeing how people do
00:31:38.159 --> 00:31:40.789
this, how people use this functionality
00:31:40.799 --> 00:31:43.430
because you're right, there's, hey, I
00:31:43.440 --> 00:31:45.509
want to do this, but where would it
00:31:45.519 --> 00:31:48.389
live? And the answer might have been on
00:31:48.399 --> 00:31:50.630
a web server back in the day, but you
00:31:50.640 --> 00:31:52.710
know, we're not running web servers on
00:31:52.720 --> 00:31:55.350
prim anymore. I mean, some people do
00:31:55.360 --> 00:31:57.269
>> or download it and you have to run it
00:31:57.279 --> 00:31:59.029
locally from your own machine,
00:31:59.039 --> 00:32:00.389
>> right? No, no, no.
00:32:00.399 --> 00:32:03.269
>> Let's put it into SharePoint and let's
00:32:03.279 --> 00:32:05.750
put some framework around it. But I'm
00:32:05.760 --> 00:32:07.110
really looking forward to seeing how
00:32:07.120 --> 00:32:09.269
people do this uh and and make use of
00:32:09.279 --> 00:32:11.350
this. Uh I think it's going to be pretty
00:32:11.360 --> 00:32:13.029
cool.
00:32:13.039 --> 00:32:16.470
So, um, the roll out, you might be
00:32:16.480 --> 00:32:18.470
asking, public preview rollout will
00:32:18.480 --> 00:32:22.230
begin early October, so very soonish,
00:32:22.240 --> 00:32:24.470
>> and expect to be completed by, well,
00:32:24.480 --> 00:32:25.990
early October. So, it's one of those
00:32:26.000 --> 00:32:27.430
instant ones.
00:32:27.440 --> 00:32:30.070
>> General availability worldwide will be
00:32:30.080 --> 00:32:33.669
mid November through late December. So,
00:32:33.679 --> 00:32:36.630
nice holiday present. Um, so I think
00:32:36.640 --> 00:32:38.310
that'll be cool. Like I said, looking
00:32:38.320 --> 00:32:40.549
forward to seeing how people uh use this
00:32:40.559 --> 00:32:42.549
functionality.
00:32:42.559 --> 00:32:44.630
Darl,
00:32:44.640 --> 00:32:47.190
I'm I'm excited about this because I get
00:32:47.200 --> 00:32:48.710
questions all the time about where
00:32:48.720 --> 00:32:51.350
what's going to happen to this planner
00:32:51.360 --> 00:32:54.310
that uh gets created every time we have
00:32:54.320 --> 00:32:55.990
these meetings.
00:32:56.000 --> 00:32:58.710
>> Tell us how's this going to that going
00:32:58.720 --> 00:33:01.750
to be uh cleaned up. Sir,
00:33:01.760 --> 00:33:05.190
>> Microsoft Planner meeting created plans
00:33:05.200 --> 00:33:07.669
will expire after 180 days of
00:33:07.679 --> 00:33:12.230
inactivity. that is MC1479508.
00:33:12.240 --> 00:33:14.230
Now, this is referring to when you
00:33:14.240 --> 00:33:15.990
create meeting notes as part of your
00:33:16.000 --> 00:33:19.190
team's meeting. You can add an agenda.
00:33:19.200 --> 00:33:21.830
Um, below that you got an area for notes
00:33:21.840 --> 00:33:24.310
that you might take. And then there's a
00:33:24.320 --> 00:33:28.070
task table and uh if you add it before
00:33:28.080 --> 00:33:29.990
the meeting, cool. If you add it during
00:33:30.000 --> 00:33:31.750
the meeting, there it is in the side
00:33:31.760 --> 00:33:34.789
panel. But this is referring to the task
00:33:34.799 --> 00:33:36.549
list at the bottom. It's a simple
00:33:36.559 --> 00:33:39.029
looking table, but what it's doing in
00:33:39.039 --> 00:33:42.070
the background is creating a planner
00:33:42.080 --> 00:33:45.110
plan and synchronizing the simple
00:33:45.120 --> 00:33:47.669
details from that table into a planner
00:33:47.679 --> 00:33:51.669
plan. Um, it's disconnected from uh
00:33:51.679 --> 00:33:53.669
other plans that you might have that
00:33:53.679 --> 00:33:56.710
exist. Although sometime this month in
00:33:56.720 --> 00:33:59.590
the next few days apparently um we'll be
00:33:59.600 --> 00:34:03.190
able to connect this meeting created
00:34:03.200 --> 00:34:06.710
plan to an existing plan. This message
00:34:06.720 --> 00:34:09.669
is really dealing with uh the plans that
00:34:09.679 --> 00:34:11.589
are disconnected that aren't really been
00:34:11.599 --> 00:34:13.190
used anymore. They're just sitting out
00:34:13.200 --> 00:34:15.909
there uh cluttering up your planner
00:34:15.919 --> 00:34:17.990
experience. If they're not used within
00:34:18.000 --> 00:34:22.629
180 days then they will be expired. Uh I
00:34:22.639 --> 00:34:25.270
this is great. I do too. One thing I
00:34:25.280 --> 00:34:26.950
want to ask though under the what and
00:34:26.960 --> 00:34:29.829
why. Yes. The last sentence tasks in
00:34:29.839 --> 00:34:34.230
loop and meeting notes remain intact and
00:34:34.240 --> 00:34:35.430
accessible.
00:34:35.440 --> 00:34:37.510
>> I understand the meeting notes part.
00:34:37.520 --> 00:34:41.829
>> I do. Uh but the tasks in loop
00:34:41.839 --> 00:34:43.750
are going to be remain accessible even
00:34:43.760 --> 00:34:47.270
after this plan is deleted.
00:34:47.280 --> 00:34:48.550
>> Yeah.
00:34:48.560 --> 00:34:50.470
So I think how this will work Daniel
00:34:50.480 --> 00:34:52.550
because it's a table and that's what
00:34:52.560 --> 00:34:54.629
they say to say the referring to the
00:34:54.639 --> 00:34:56.550
list of tasks
00:34:56.560 --> 00:34:59.030
you know the task name who it's assigned
00:34:59.040 --> 00:35:01.750
to the the due date. I think all they're
00:35:01.760 --> 00:35:04.630
going to do is cut off that connection
00:35:04.640 --> 00:35:06.390
to this
00:35:06.400 --> 00:35:08.870
standalone plan
00:35:08.880 --> 00:35:10.870
expire the plan but you'll still have
00:35:10.880 --> 00:35:13.510
the table there and you can happily use
00:35:13.520 --> 00:35:15.270
that if you want to. But um it it's
00:35:15.280 --> 00:35:18.069
after 180 days of inactivity and I'd say
00:35:18.079 --> 00:35:21.750
there'd be quite a fair number of those
00:35:21.760 --> 00:35:24.069
types of plans that are inactive.
00:35:24.079 --> 00:35:24.870
>> Yep. Indeed.
00:35:24.880 --> 00:35:27.589
>> Yeah. So, this is really a short
00:35:27.599 --> 00:35:30.950
message, a tidy up uh function, but um
00:35:30.960 --> 00:35:32.310
I'm looking forward to the other one
00:35:32.320 --> 00:35:34.390
that we talked about a few shows ago,
00:35:34.400 --> 00:35:36.310
which allows us to put these tasks where
00:35:36.320 --> 00:35:38.710
they should be in an existing plan, you
00:35:38.720 --> 00:35:41.270
know, rather than this standalone thing.
00:35:41.280 --> 00:35:43.750
This particular feature roll out will
00:35:43.760 --> 00:35:47.030
begin early October and complete by mid
00:35:47.040 --> 00:35:49.030
October and it's for everybody generally
00:35:49.040 --> 00:35:50.550
available.
00:35:50.560 --> 00:35:53.190
That's it. Um that's the show too. I
00:35:53.200 --> 00:35:55.270
know we went a little over. We're just
00:35:55.280 --> 00:35:57.910
adding extra value all the time. But um
00:35:57.920 --> 00:35:59.670
we're glad to do that and thanks for
00:35:59.680 --> 00:36:00.710
joining us.
00:36:00.720 --> 00:36:03.190
>> Thank you so much everyone. We greatly
00:36:03.200 --> 00:36:05.670
appreciate it. We'll catch you next
00:36:05.680 --> 00:36:06.470
time.
00:36:06.480 --> 00:36:07.750
>> All right. Bye for now.
00:36:07.760 --> 00:36:10.760
>> Byebye.
