WEBVTT 00:00:00.000 --> 00:00:02.560 Microsoft just deployed Copilot for Microsoft 00:00:02.560 --> 00:00:07.280 365 to over 330 ,000 employees and contractors. 00:00:08.179 --> 00:00:11.279 Probably the largest deployment of Copilot for 00:00:11.279 --> 00:00:15.820 M365 in the world. Now customers always ask me 00:00:15.820 --> 00:00:18.019 for references and they want to talk to other 00:00:18.019 --> 00:00:21.559 customers and how they've deployed Copilot. What 00:00:21.559 --> 00:00:24.699 better customer than Microsoft itself to talk 00:00:24.699 --> 00:00:27.570 about this? and recently Microsoft published 00:00:27.570 --> 00:00:30.530 white papers and PowerPoint slides that you can 00:00:30.530 --> 00:00:34.049 access that describe how they went on this journey. 00:00:34.789 --> 00:00:37.530 I've taken a look at those documents in addition 00:00:37.530 --> 00:00:39.789 to other documents that talk about deployment 00:00:39.789 --> 00:00:43.729 of Copilot and in this video, in a very simplified 00:00:43.729 --> 00:00:46.189 manner, we're going to look at the four different 00:00:46.189 --> 00:00:50.850 stages. Number one is governance, followed by 00:00:50.850 --> 00:00:54.289 planning and deployment, followed by adoption, 00:00:55.149 --> 00:00:59.009 And finally, support. If you ever want to go 00:00:59.009 --> 00:01:01.649 deeper into any of these topics, I'll provide 00:01:01.649 --> 00:01:04.890 documentation and links from Microsoft that go 00:01:04.890 --> 00:01:08.030 into much more detail. Now let's get started. 00:01:08.269 --> 00:01:11.090 First, a brief overview. There are many different 00:01:11.090 --> 00:01:13.689 flavors of Copilot, and today we're talking about 00:01:13.689 --> 00:01:17.689 Copilot for Microsoft 365. Microsoft deployed 00:01:17.689 --> 00:01:22.650 Copilot for M365 to 330 ,000 employees and contractors. 00:01:24.109 --> 00:01:27.909 Now Microsoft sent out surveys and of the people 00:01:27.909 --> 00:01:32.129 that responded 74 % said that co -pilot for M365 00:01:32.129 --> 00:01:36.209 made them more productive and on average it saved 00:01:36.209 --> 00:01:39.069 them about 20 minutes a day. The following challenges 00:01:39.069 --> 00:01:42.329 were observed during deployment. Number one, 00:01:42.430 --> 00:01:46.730 learning to delegate to AI. Most people haven't 00:01:46.730 --> 00:01:49.549 had their own personal assistant so they're not 00:01:49.549 --> 00:01:53.629 sure when and how to delegate to AI. Because 00:01:53.629 --> 00:01:56.409 Copilot is essentially your own personal assistant. 00:01:56.670 --> 00:02:01.810 Number two, learning to prompt AI. Prompt engineering 00:02:01.810 --> 00:02:05.870 is real. The way you write your prompts and the 00:02:05.870 --> 00:02:08.909 way you interact with Copilot takes some time 00:02:08.909 --> 00:02:11.949 and practice to be able to get the best response 00:02:11.949 --> 00:02:16.569 back. And number three, your usage of Copilot 00:02:16.569 --> 00:02:19.969 is specific to your role, your job function, 00:02:20.539 --> 00:02:23.759 the language and country so microsoft learned 00:02:23.759 --> 00:02:26.580 this and had to do some unique things to make 00:02:26.580 --> 00:02:30.240 sure that copilot was getting used in the most 00:02:30.240 --> 00:02:33.479 efficient way based on those factors now let's 00:02:33.479 --> 00:02:36.800 talk about that first section of governance and 00:02:36.800 --> 00:02:39.840 more specifically we'll talk about tenant hygiene 00:02:39.840 --> 00:02:44.120 see the reason why copilot can provide such amazing 00:02:44.120 --> 00:02:49.099 responses is because it has access to data But 00:02:49.099 --> 00:02:53.520 unlike public AI services like OpenAI that scour 00:02:53.520 --> 00:02:56.479 the internet and provide you information that's 00:02:56.479 --> 00:03:00.520 all public, inside your corporation, there are 00:03:00.520 --> 00:03:03.800 probably lots of files and folders and chat messages 00:03:03.800 --> 00:03:07.199 and SharePoint sites that you should not have 00:03:07.199 --> 00:03:10.659 access to. Think of HR or engineering projects 00:03:10.659 --> 00:03:14.319 that should be just focused on the teams that 00:03:14.319 --> 00:03:17.460 are working on it. So basically you want to limit 00:03:17.460 --> 00:03:20.759 oversharing. Oversharing content that's yours 00:03:20.759 --> 00:03:23.000 with people that shouldn't have access to it 00:03:23.000 --> 00:03:26.740 or people that have shared things with you that 00:03:26.740 --> 00:03:29.560 maybe shouldn't have. So the way you do that 00:03:29.560 --> 00:03:34.439 is by using sensitivity labels. Sensitivity labels 00:03:34.439 --> 00:03:38.099 are labels that you can use to mark your emails, 00:03:38.340 --> 00:03:43.780 your SharePoint sites, your files. And based 00:03:43.780 --> 00:03:46.939 on the classification of those labels, the access 00:03:46.939 --> 00:03:50.620 gets restricted. Another best practice is having 00:03:50.620 --> 00:03:54.659 one SharePoint site per project. And that way 00:03:54.659 --> 00:03:57.919 you can define who should be a member of that 00:03:57.919 --> 00:04:01.520 SharePoint site versus using one SharePoint site 00:04:01.520 --> 00:04:04.400 for all your projects. Another way is Microsoft 00:04:04.400 --> 00:04:08.419 Purview. Now this application has so many different 00:04:08.419 --> 00:04:11.099 functions and features, but one of them is DLP. 00:04:11.759 --> 00:04:15.860 data loss prevention. So if you enable DLP, if 00:04:15.860 --> 00:04:18.860 something happens that shouldn't, then Microsoft 00:04:18.860 --> 00:04:22.019 Purview can kick in and provide some remediation. 00:04:22.319 --> 00:04:26.259 And finally, there's also restricted SharePoint 00:04:26.259 --> 00:04:30.339 search. This basically allows you to restrict 00:04:30.339 --> 00:04:34.519 Copilot to up to 100 SharePoint sites that it 00:04:34.519 --> 00:04:38.319 can then scour and have access to the data. So 00:04:38.319 --> 00:04:41.579 if you haven't done the sensitivity labels and 00:04:41.579 --> 00:04:44.759 other functions to make sure everything is in 00:04:44.759 --> 00:04:47.819 order from a tenant hygiene perspective, then 00:04:47.819 --> 00:04:50.060 you can leverage tools like restricted SharePoint 00:04:50.060 --> 00:04:53.800 search to limit Copilot's access. Let's move 00:04:53.800 --> 00:04:57.439 on to planning. In order to make sure that Copilot 00:04:57.439 --> 00:05:00.100 was being used most effectively by employees 00:05:00.100 --> 00:05:03.259 all around the world, Microsoft collaborated 00:05:03.259 --> 00:05:07.319 with 12 country -specific work councils that 00:05:07.319 --> 00:05:12.040 provided input on cultural nuances, language 00:05:12.040 --> 00:05:15.959 access, and also ethical boundaries. Because 00:05:15.959 --> 00:05:19.639 there are certainly differences between how privacy 00:05:19.639 --> 00:05:22.779 and data is handled in Europe compared to the 00:05:22.779 --> 00:05:26.379 United States. So again, this was important to 00:05:26.379 --> 00:05:29.360 make sure that usage of Copilot was specific 00:05:29.360 --> 00:05:32.699 to the role, language, and country. Moving on 00:05:32.699 --> 00:05:35.959 to deployment. Initially, Microsoft did a very 00:05:35.959 --> 00:05:39.100 targeted rollout. And to decide who would get 00:05:39.100 --> 00:05:43.360 Copilot for Microsoft 365, business impact was 00:05:43.360 --> 00:05:46.600 looked at. KPIs, key performance indicators. 00:05:47.120 --> 00:05:51.319 So who would make the most business impact if 00:05:51.319 --> 00:05:54.819 they got the initial rollout of Copilot? One 00:05:54.819 --> 00:05:57.439 important thing was product feedback. Whoever 00:05:57.439 --> 00:06:00.620 got Copilot had to provide product feedback so 00:06:00.620 --> 00:06:03.360 that... the product engineering teams could keep 00:06:03.360 --> 00:06:06.279 building and improving the product before it 00:06:06.279 --> 00:06:09.079 became generally available now one of the groups 00:06:09.079 --> 00:06:12.540 as a whole that got co -pilot for microsoft 365 00:06:12.540 --> 00:06:16.500 in the beginning was it and this served multiple 00:06:16.500 --> 00:06:21.040 purposes one microsoft knew that it was eventually 00:06:21.040 --> 00:06:24.740 going to support its user population so it would 00:06:24.740 --> 00:06:27.360 be important for them to have access to the tools 00:06:27.360 --> 00:06:30.040 so they can become familiar with it and two it 00:06:30.040 --> 00:06:32.379 was also useful for them so that they could become 00:06:32.379 --> 00:06:35.620 productive and provide feedback so that group 00:06:35.620 --> 00:06:40.199 got co -pilot first then department leads got 00:06:40.199 --> 00:06:44.000 to select groups of users that they thought would 00:06:44.000 --> 00:06:46.279 make the most business impact so it was left 00:06:46.279 --> 00:06:49.399 up to them to select these individuals but also 00:06:49.399 --> 00:06:52.720 notice that rollouts were made to entire teams 00:06:52.720 --> 00:06:56.279 because microsoft understood that If you just 00:06:56.279 --> 00:06:59.720 pick one or two people from certain groups, you 00:06:59.720 --> 00:07:02.439 wouldn't get as much collaboration across that 00:07:02.439 --> 00:07:05.740 team. And so it would make sense to give co -pilot 00:07:05.740 --> 00:07:09.860 to the entire team, all 10 or 20 people, so that 00:07:09.860 --> 00:07:11.920 they can collaborate, they can learn, they can 00:07:11.920 --> 00:07:15.560 help each other out. And once this was all done, 00:07:15.800 --> 00:07:18.740 then the next wave of rollout actually went to 00:07:18.740 --> 00:07:21.860 sales and support because that was the group 00:07:21.860 --> 00:07:24.540 that they deemed made the most business impact. 00:07:25.180 --> 00:07:28.240 As the deployment continued and more and more 00:07:28.240 --> 00:07:31.759 users got Copilot, the team moved into the optimization 00:07:31.759 --> 00:07:36.579 phase, adding value with extensibility. And so 00:07:36.579 --> 00:07:39.680 the team ended up building connectors for line 00:07:39.680 --> 00:07:43.980 of business tools like ServiceNow, SAP, and Workday. 00:07:44.160 --> 00:07:48.079 This allowed Copilot not to just work with Microsoft 00:07:48.079 --> 00:07:51.000 Office applications and data sources inside the 00:07:51.000 --> 00:07:54.209 tenant, but also third -party applications and 00:07:54.209 --> 00:07:58.029 data sources, adding a ton of value for the end 00:07:58.029 --> 00:08:00.970 users at Microsoft. Additionally, the teams use 00:08:00.970 --> 00:08:04.810 Copilot Studio to embed Copilot into Ask HR, 00:08:05.149 --> 00:08:09.389 Microsoft's HR support tool, so that when employees 00:08:09.389 --> 00:08:11.850 opened up cases and were chatting with the bot, 00:08:12.069 --> 00:08:15.350 they got much better responses due to Copilot 00:08:15.350 --> 00:08:17.870 being embedded in there. Critical to the success 00:08:17.870 --> 00:08:21.569 of Copilot was adoption. Getting users to actually 00:08:21.569 --> 00:08:24.350 engage with Copilot, become familiar with it, 00:08:24.430 --> 00:08:28.110 use it, love it in their everyday work. So what 00:08:28.110 --> 00:08:31.430 Microsoft did initially was, one, generate a 00:08:31.430 --> 00:08:34.690 ton of excitement so that end users wanted to 00:08:34.690 --> 00:08:38.549 get Copilot, use Copilot. And number two, create 00:08:38.549 --> 00:08:42.169 an onboarding site, a place where users can go 00:08:42.169 --> 00:08:45.450 to initially get some training. Now, the training 00:08:45.450 --> 00:08:48.450 was happening in different modalities. There 00:08:48.450 --> 00:08:51.470 were videos, there were blog posts, learning 00:08:51.470 --> 00:08:54.090 sites, and later on, there were even in -person 00:08:54.090 --> 00:08:57.070 trainings that happened locally. And it was also 00:08:57.070 --> 00:09:00.090 happening at different difficulty levels, beginner, 00:09:00.230 --> 00:09:02.309 intermediate, advanced. So there was something 00:09:02.309 --> 00:09:06.070 for everyone. And Microsoft also opened a ton 00:09:06.070 --> 00:09:09.129 of different feedback channels so that end users 00:09:09.129 --> 00:09:12.769 could ask questions from the product teams, but 00:09:12.769 --> 00:09:15.870 also learn amongst each other through these different 00:09:15.870 --> 00:09:19.549 channels. And finally, executive usage was key 00:09:19.549 --> 00:09:23.610 because for team members to see that their executives 00:09:23.610 --> 00:09:26.730 are also using Copilot, how they're using it 00:09:26.730 --> 00:09:29.809 and how it simplifies their workflow was motivating 00:09:29.809 --> 00:09:32.929 and encouraging them to use it in their work 00:09:32.929 --> 00:09:35.730 every day as well. On the training side, there 00:09:35.730 --> 00:09:38.190 were initially foundational trainings developed 00:09:38.190 --> 00:09:41.950 to teach users, where can you access Copilot? 00:09:42.090 --> 00:09:45.129 How do you use Copilot inside Word, Outlook, 00:09:45.190 --> 00:09:48.279 PowerPoint? real basic one -on -one level courses. 00:09:48.679 --> 00:09:51.460 Then there were Viva Learning courses as well 00:09:51.460 --> 00:09:54.399 because Microsoft uses Viva Learning a ton and 00:09:54.399 --> 00:09:56.620 so this was a familiar environment for end users 00:09:56.620 --> 00:09:59.919 to go and take these types of courses. There 00:09:59.919 --> 00:10:03.200 were also videos and demos and frequently asked 00:10:03.200 --> 00:10:05.259 question documents that were developed by the 00:10:05.259 --> 00:10:08.500 product teams. And then later on there were instructor 00:10:08.500 --> 00:10:12.240 -led classes because end users asked for in -person 00:10:12.240 --> 00:10:14.220 types of events so that they can collaborate 00:10:14.220 --> 00:10:16.639 and learn from each other. Those worked out really 00:10:16.639 --> 00:10:19.799 well. And also teams of co -pilot champions within 00:10:19.799 --> 00:10:23.000 departments or organizational units started developing. 00:10:23.440 --> 00:10:26.379 People that were very excited and more interested 00:10:26.379 --> 00:10:29.340 about co -pilot going in deeper. And so as they 00:10:29.340 --> 00:10:31.299 got this additional training and understanding 00:10:31.299 --> 00:10:33.360 from their colleagues, they'd go back to their 00:10:33.360 --> 00:10:36.500 teams and provide localized training. And finally, 00:10:36.500 --> 00:10:39.620 on the support side, which ties back into training. 00:10:40.299 --> 00:10:43.820 Microsoft leveraged Viva Engage as well as teams 00:10:43.820 --> 00:10:46.200 and channels where end users could post their 00:10:46.200 --> 00:10:48.559 questions and get responses from their colleagues 00:10:48.559 --> 00:10:51.340 or people in the product team. And then also 00:10:51.340 --> 00:10:54.200 departmental sites from finance and marketing 00:10:54.200 --> 00:10:57.320 and HR started popping up where specific use 00:10:57.320 --> 00:11:00.779 cases and support flows that those types of users 00:11:00.779 --> 00:11:04.590 were encountering. got posted so that colleagues 00:11:04.590 --> 00:11:07.529 could receive help now as we wrap i do want to 00:11:07.529 --> 00:11:10.070 bring your attention to one link in the last 00:11:10.070 --> 00:11:13.990 slide of applying ai at scale and that is deploying 00:11:13.990 --> 00:11:18.210 copilot for microsoft 365 in four chapters i 00:11:18.210 --> 00:11:20.149 looked at this document and i read through it 00:11:20.149 --> 00:11:22.610 and i thought that it was a great article it 00:11:22.610 --> 00:11:24.750 essentially talks about what we talked about 00:11:24.750 --> 00:11:27.629 but in much more detail so make sure you check 00:11:27.629 --> 00:11:30.440 that out Also check out the other links in that 00:11:30.440 --> 00:11:33.779 last slide as well. Tons of great content. Now 00:11:33.779 --> 00:11:37.080 I hope you found this summary of deploying Copilot 00:11:37.080 --> 00:11:40.299 according to Microsoft for all those users helpful. 00:11:41.000 --> 00:11:43.340 If you have any comments, let me know. If you 00:11:43.340 --> 00:11:45.379 like this video, make sure you give it a thumbs 00:11:45.379 --> 00:11:49.580 up. And if you have also deployed Copilot and 00:11:49.580 --> 00:11:52.360 have some unique experiences, I would love to 00:11:52.360 --> 00:11:55.080 hear your feedback. Thank you very much for watching 00:11:55.080 --> 00:11:57.340 and I'll catch you on the next one.