Build your own copilot! New Microsoft Copilot extensions
Summary
TLDRこのビデオスクリプトでは、Microsoft 365のCopilot拡張機能を紹介しています。Copilotは、Microsoft Graphを活用し、SharePointやOneDrive、メール、カレンダー、TeamsなどのMicrosoft 365アプリ内のファイルやデータを参照し、インターネット情報と組み合わせてパーソナライズされた体験を提供します。Copilot拡張機能では、外部の情報源にリアルタイムでアクセスし、カスタムタスクに特化したCopilotを作成し、外部システムとの動的な接続や特定のアクションを自動化できます。ビデオでは、サポート技術者として週次報告を作成する例を通じて、Copilot拡張機能がどのように体験をカスタマイズするかを説明しています。
Takeaways
- 🔍 Copilot for Microsoft 365は、外部データと独自スキルを組み合わせて日常業務を効率化することができる拡張機能を提供しています。
- 🌐 CopilotはMicrosoft Graphを利用して、SharePoint、OneDrive、メール、カレンダー、TeamsなどのMicrosoft 365内のファイルやデータを参照し、パーソナライズされたエクスペリエンスを提供します。
- 📄 Wordでプロンプトを送信すると、Copilotは目的を理解し、必要な情報を取得してフォーマットされた応答を返します。
- 📈 Copilot拡張機能は、既に優れた基盤体験をさらに強化し、特定のタスクに特化したCopilotを構築することができます。
- 🔌 Copilot拡張機能を使用すると、Microsoft 365以外のリアルタイムの外部情報源にアクセスし、タスクの確認などを行うことができます。
- 📚 Copilot拡張機能では、特定のファイルやデータセットに特化した独自のCopilotを作成し、生成内容や自動化されたアクションをカスタマイズできます。
- 🛠️ 技術者として週報を作成する例では、Copilot拡張機能を使用して、Microsoft 365以外のサポートサイトの知識ベース記事を含めることができます。
- 📝 Copilot拡張機能を使用して、外部システムに代わってアクションを実行することができるプラグイン(例:Doc Improvement)があります。
- 📘 Copilot Studioを使用して、低コード方法で独自のCopilotを構築することができます。これにより、特定のユーザーやグループに公開して使用することができます。
- 💻 Visual Studio CodeなどのIDEを使用して、プラグインやAPI仕様、機能定義を含むCopilot拡張機能を構築することも可能です。
- 🚀 Copilot拡張機能の構築と展開は今後数週間で行われ、詳細はcopilotstudio.microsoft.comで確認できます。
Q & A
Copilot for Microsoft 365をカスタマイズするために何ができるのか?
-Copilot for Microsoft 365は、外部データとの連携や特定のスキルを追加することで、ユーザーの日常業務を加速させるためにカスタマイズできます。
Copilot extensionsの役割は何ですか?
-Copilot extensionsは、Copilotの基本的な機能をさらに充実させ、特定のタスクや外部データとの連携を可能にします。
Copilot for Microsoft 365が他の無料の生成AIと異なる点は何ですか?
-Copilot for Microsoft 365は、Microsoft Graphの情報を使用して個々のユーザーの体験をパーソナライズし、さらに外部のデータソースと連携してより高度な応答を提供する点で異なります。
技術者の例でCopilot extensionsがどのように役立つのかを説明してください。
-技術者が週次レポートを作成する際、Copilot extensionsを使用して、Microsoft 365内のデータだけでなく、サポートサイトのナレッジベース記事も含めた情報を取得し、レポートを自動生成することができます。
特定のタスクに焦点を当てたCopilotはどのように構築されますか?
-特定のタスクに焦点を当てたCopilotは、必要なファイルやデータを指定し、追加の指示やワークフローを設定して生成されます。その後、他のユーザーも利用できるようにCopilot extensionとして公開されます。
Copilot StudioでCopilotを作成する手順は何ですか?
-Copilot Studioでは、まずCopilotに名前と説明を付け、指示を追加してから、データソースやアクションを設定し、作成後に公開して特定のユーザーやグループに提供します。
Visual Studio Codeを使用してCopilot extensionを作成する際の基本ファイルは何ですか?
-Visual Studio Codeを使用してCopilot extensionを作成する際には、Swagger.json、Supportplugin.json、manifest.jsonの3つの基本JSONファイルが必要です。
Swagger.jsonファイルの役割は何ですか?
-Swagger.jsonファイルは、APIに接続するための操作や応答を定義し、成功または失敗時に返す情報を指定します。
manifest.jsonファイルに含まれる重要な情報は何ですか?
-manifest.jsonファイルには、ID、名前、開発者、説明、ブランディングの詳細、および定義された宣言的なCopilotの情報が含まれます。
Copilot extensionsの展開時期はいつですか?
-Copilot extensionsの機能は、今後数週間以内に展開される予定です。
Outlines
🌟 Copilot拡張機能の紹介と構築方法
Microsoft 365のCopilotを拡張して、独自のニーズに合わせた体験を実現することができる。Copilot拡張機能は、外部データを使用し、日常業務を加速させる特別なスキルを追加することができる。Copilotは、Microsoft Graphの情報と連携して、SharePoint、OneDrive、メール、カレンダー、Teamsなどのファイルやデータを参照し、インターネットの情報も活用して、Microsoft 365アプリ内のCopilot体験をパーソナライズする。Copilot拡張機能は、情報源にリアルタイムでアクセスし、タスクの完了確認などを行うプラグインや、Microsoft Graphがインデックスするサイトやサービスを拡張するコネクタを提供する。また、特定のファイルやデータを必要とする特定のタスクに焦点を当てた独自のCopilotを構築することもできる。これらのCopilotは、他のユーザーが使用できるCopilot拡張機能として提供される。サポート技術者が週報を作成する例として、Copilot拡張機能を使用して、Microsoft 365以外のサポートサイトの情報を含めたり、外部システムに代わってアクションを実行したりする方法が紹介されている。
📚 Copilot拡張機能を使ったサポート技術者の仕事の効率化
Copilot拡張機能を使用することで、サポート技術者の業務が効率化される。Copilotは、メールの分析やKB記事の更新など、同じセッション内で複数のカスタムCopilotを操作することができる。サポートコンテンツの執筆者Copilotは、知識ベース記事を最新の状態に保つための役立ちのツールとして構築されている。Copilot拡張機能を構築するには、Microsoft Copilot Studioの低コードアプローチやVisual Studio CodeなどのIDEを使用することができる。Copilot Studioでは、Copilotの名前や説明、インストラクション、スタータープロンプトを設定して作成することができる。また、外部データやMicrosoft 365内のデータをプラグインやコネクタを使って接続することができる。Visual Studio Codeでは、プラグインの動作を定義するJSONファイルを作成し、APIの操作や応答、機能の定義、マニフェストのメタデータなどを設定することができる。これらの機能を活用して、よりカスタマイズされた体験を実現することができる。
Mindmap
Keywords
💡Copilot for Microsoft 365
💡Copilot extensions
💡Microsoft Graph
💡Knowledge Base (KB) articles
💡Copilot Studio
💡Visual Studio Code
💡JSONファイル
💡プラグイン
💡低コード
💡タスクの自動化
Highlights
Customizing Copilot for Microsoft 365 with tailored experiences and external data integration.
Introduction of Copilot extensions to enhance the baseline experience of Copilot for Microsoft 365.
Utilization of large language models and Microsoft Graph to personalize the Copilot experience.
How Copilot determines user intent and grounds prompts with additional information.
Types of Copilot extensions: external data integration and specialized task-focused extensions.
Real-time interaction with external information sources through available plugins.
Using connectors to extend Microsoft Graph indexing to external sites or services.
Building custom Copilots for specific tasks with a unique set of files or data.
Adding instructions and workflows to scope the generated content by a specialized Copilot.
Example of a support technician using Copilot to write a weekly report with external data.
Demonstration of enriched experience with Copilot extension including external KB articles.
Explanation of how a Microsoft Graph connector is used to find external information.
Using a plugin to perform actions with an external system on behalf of the user.
Creating a task in a knowledge base system through a Copilot extension.
Tailoring the technician's experience with content specific to their needs.
Focusing on a specific task with a specialized Copilot available as an extension.
Building a support content author Copilot to keep knowledge base articles updated.
Using multiple custom Copilots in the same conversation for a cohesive workflow.
Drafting a fully written report with the help of Support Report Writer Copilot.
Building Copilot extensions using a low-code approach with Microsoft Copilot Studio.
Accessing Copilot Studio and creating a new Copilot with specific instructions.
Linking Copilot to external data sources or inside Microsoft 365 with actions.
Using an IDE like Visual Studio Code for building Copilot extensions with detailed configurations.
Overview of the JSON files required for building a Copilot extension in an IDE.
The upcoming rollout of these capabilities and resources for getting started.
Transcripts
You can now customize Copilot for Microsoft 365
for your own unique needs,
with tailored experiences that can work with external data,
while adding unique skills
to accelerate the things you do every day.
This is now possible with Copilot extensions.
And today I'll demonstrate the experience
with Copilot extensions and how to build them.
First, let me unpack how Copilot for Microsoft 365 works
in relation to Copilot extensions.
Copilot for Microsoft 365 comprises large language models,
information in the Microsoft Graph to find
or reference files and data in places like SharePoint,
OneDrive, email, your calendar, and Teams,
along with information found on the internet
to personalize the Copilot experience
inside the Microsoft 365 apps you use.
For example, when you submit a prompt in Word,
Copilot determines what you are trying to do,
finds additional information to ground your prompt,
and then returns a fully formatted,
highly personalized response to you.
This is what sets Copilot for Microsoft 365 apart
from free generative AI experiences.
Copilot extensions enrich and focus
this already great baseline experience further.
There are a few main types.
The first lets you plug into information sources
relevant to you that are sitting outside of Microsoft 365
in near real time, and you can interact with them,
like confirming a task was completed.
This is made possible by available plugins.
You can also use connectors
to extend what the Microsoft Graph indexes
to sites or services also outside of Microsoft 365.
The next lets you build your own Copilot,
focused on a specific task requiring a specific set of files
or data to guide it.
You can also add additional instructions and workflow
to scope what it generates
and even automate specific actions.
This specialized Copilot is then made available
as a Copilot extension for others to use.
Let me make this real
by walking through how Copilot extensions
customize your experience with Copilot for Microsoft 365.
In this example, I'm a support technician.
And one of the things I regularly have to do
is write a weekly report
detailing the support cases that I've worked on.
I'm in Copilot for Microsoft Teams,
and I'll first start with my baseline Copilot experience
without extensions.
I'll write a prompt to find all the emails I sent today
and group them by topic.
And that finds me all of the emails I was looking for
and groups them like I asked.
I now want to go beyond Microsoft 365 data
and include information and knowledge base articles
outside of it that are on our support site.
I'll show you the enriched experience
with my Copilot extension first,
and then explain what's going on under the covers.
I'll use a different session, and paste in,
"Summarize all the emails I sent today,
group them by high level topic.
For each topic, find the support wiki article
that is most related."
And KB articles will come from the connected site.
Once the entire response is generated,
I can see the matching KB articles for each topic.
And if I look at the citations,
these ones are the sources using my Graph connected site.
Here, my Copilot extension is using
a Microsoft Graph connector
to find information from the external sources
that are connected to the Microsoft Graph.
Next, I'll use a different Copilot extension
that can also perform actions
with an external system on my behalf.
My IT team has enabled a plugin called Doc Improvement.
In this prompt from yesterday,
I'll paste create a doc improvement task
to improve that first KB article
based on the related emails I sent.
This doesn't need all of the detail from the previous prompt
because Copilot gets that information from the chat history
in this session.
And this extension actually writes back to another system
and creates a task for a content writer to update
one of our KB support articles.
After I confirm, I see a confirmation that it has created
the doc improvement work item.
So far I've shown how by using Copilot extensions,
my experience as a technician
was tailored with content specific to me,
while enabling dynamic connections to external data
and creating a ticket in my knowledge base system.
Now let's look at how I can go further
by focusing in on a specific task with a specialized Copilot
available as a Copilot extension.
This is our support content author Copilot,
which my team has built
to help us keep our knowledge base articles up to date.
You can see that it has a few suggested prompts
for skills or frequent tasks.
I'll paste in update the Wiki article about remote help
to add a first step of making sure
that the user has logged in.
This will first find the correct KB article,
get its contents, understand where to insert the text,
and then ask me to confirm.
I can also suggest a modification,
but let me type, go ahead,
and let Copilot make the update.
And one more thing I'll show you
is how you can have multiple custom Copilots
work together in the same conversation.
I'll go back to the session I had with Copilot earlier.
This time, I will at mention the support content author
Copilot with a similar prompt.
This performs the same job,
but keeps me in this same session.
Now, I'll at mention another custom Copilot
that my team has written called Support Report Writer.
Because it is being used in the same session,
it has Microsoft Copilot's analysis of my email,
as well as information about the KB article I just updated.
Then after it's finished,
you'll see that I now have a fully written draft report
that I can copy into an email or a document,
and make any additional changes.
So, that's how Copilot extensions work.
To build them, you can choose a low-code approach
with Microsoft Copilot Studio,
or an IDE like Visual Studio.
Let's start with the low-code approach
to build your own Copilot.
You can get to Copilot Studio
by going to copilotstudio.microsoft.com.
From the Copilots tab, I just need to add a Copilot.
And I can either use a prompt
to describe the Copilot I want to build,
or I can skip right to the configuration,
which I'll do in this case.
First, I need to give it a name,
so I'll type in "Support Report Writer."
For description, I've enabled clipboard history here,
so I'll paste in the text to describe my Copilot.
Next, instructions, give your Copilot more context
about its purpose and how to respond.
You can get very specific with these instructions
using natural language.
Here I've pasted in about 600 characters,
but these can be up to 8,000 characters.
Starter prompts like we saw before in our custom Copilot
can also be added for frequent tasks
and to help new users quickly get started.
These are optional,
and I'll skip this step to save a little time.
From there, I just need to hit create.
Once complete, I can make it available
to the right users and groups by publishing it.
Next, you can plug into other data,
which can be external to, or inside of Microsoft 365.
In the Copilot from Microsoft 365 page,
you can see that I already have a few actions,
including a few that point to a specific
SharePoint locations for content.
I'll add an action.
Here, I can choose between a connector
to link to the data I want,
conversation to link to an existing solution,
a prompt to link to a standard reusable prompt,
and a flow containing workflow automation.
I'll choose a conversation in my case.
Now, I'll give it a name, "Support KB Docs Improvement."
I'll leave the default solution,
and you'll see that the schema name
updates itself automatically.
Then I'll hit create.
And if you prefer to use an IDE like Visual Studio Code,
let me show you the experience
with the Microsoft Teams toolkit installed.
I'll start with the plugin this time.
You'll see that I have three basic JSON files
open in my tabs.
Swagger that JSON to connect to my API
using specified operations and responses to send back
when it succeeds or fails.
Supportplugin.JSON describes the actions to take for users
and gives more information for the model to use.
Below that, the functions are defined to perform tasks.
Then in runtimes, it points back to the swagger file
and what functions are defined there.
Finally, the manifest.JSON,
which includes a bit more metadata including the ID,
naming, developer, description, and branding details.
Importantly, you'll see that in the manifest,
I've also defined declarative Copilots.
In my case, the content Copilot I showed you earlier.
So let's jump into that JSON file
to show you how to build a Copilot.
You'll see that this file contains
essentially the same elements that we saw in Copilot Studio.
Things like the name, ID, and description.
The instructions, again,
to provide more context for your custom Copilot.
We've also defined capabilities,
which point to our Graph connector data.
Actions for a plugin that points
to our open API specification,
and there are also conversation starters
as suggested prompts with details
about what those should do.
And with that, you can get started
building Copilot extensions for more tailored experiences,
capable of specialized tasks with the data you specify,
even if it sits outside of Microsoft 365.
These capabilities will be rolling out in the coming weeks.
To learn more and get started, check out
copilotstudio.microsoft.com.
Keep watching Microsoft Mechanics for all the deep dives
and latest updates for Copilot and more.
Subscribe if you haven't yet, and we'll see you soon.
تصفح المزيد من مقاطع الفيديو ذات الصلة
Extend Copilot for Sales with custom data and insights from your own apps
How Microsoft Copilot for Microsoft 365 works
How Microsoft Copilot for Microsoft 365 works
便利技を紹介します|ここまで使える!Copilot初心者講座2024年7月
Copilot for Microsoft365 のAIが業務を簡単に時短できる方法 ウェビナー
【Copilot for Microsoft 365】もっと活用しよう - Copilot(M365 用)編
5.0 / 5 (0 votes)