[{"data":1,"prerenderedAt":2120},["ShallowReactive",2],{"article-\u002Farticles\u002Fcopilot-agent-katsuyou":3,"article-series-m365-copilot":2047},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"category":11,"series":12,"seriesNo":13,"seriesLabel":14,"author":15,"thumbnail":16,"tags":17,"faq":22,"body":38,"_type":2041,"_id":2042,"_source":2043,"_file":2044,"_stem":2045,"_extension":2046},"\u002Farticles\u002Fcopilot-agent-katsuyou","articles",false,"","Microsoft 365 Copilotのエージェントの作り方と活用事例｜Copilot Studio・エージェントビルダー・Notebooksの使い分け（シリーズ完結）","Microsoft 365 Copilotを「使う」段階から、エージェントを「作る」段階へ。エージェントビルダー・Copilot Studio・Copilot Notebooksの使い分け、非IT企業での活用例と作り方、野良エージェントを防ぐ管理を解説します。","2026-11-09","Microsoft 365 活用","m365-copilot",8,"第8回（完結）","K.S.ロジャース株式会社","\u002Fimg\u002Fcontents\u002Fnews\u002Fthumb129.jpg",[18,19,20,21],"Microsoft 365 Copilot","AIエージェント","Copilot Studio","AX",[23,26,29,32,35],{"q":24,"a":25},"Microsoft 365 Copilotのエージェントとは何ですか？","特定の業務やテーマに合わせて、指示・参照する知識・実行できる操作を設定した Copilot の専用版です。たとえば社内規程の問い合わせに答えるエージェントや、新人の受け入れを手伝うエージェントを作り、社内で共有して使えます。",{"q":27,"a":28},"エージェントビルダーとCopilot Studioはどう使い分けますか？","指示と社内ファイルなどの知識だけで動く簡単なエージェントは、Microsoft 365 Copilot アプリや Teams から使えるエージェントビルダーで作ります。外部サービスとの連携やワークフローの自動実行など、アクションが必要なものは Copilot Studio を使います。",{"q":30,"a":31},"Copilot StudioとPower Automateはどう使い分けますか？","決まった手順を決まった順番で流すだけなら Power Automate のクラウドフローで足ります。SharePoint・Outlook・Teams などは標準のコネクタでつながり、要約や分類などAIの判断が要るところだけ、フローの中にプロンプトを差し込めます。人との会話の中で外部サービスの照会や更新まで行わせたい場合に Copilot Studio を使います。",{"q":33,"a":34},"エージェントを使うのに追加料金はかかりますか？","2026年9月時点の Microsoft の説明では、Microsoft 365 Copilot ライセンスを持つユーザーが Copilot Chat・Teams・SharePoint でエージェントを使う場合、追加料金はかかりません。ライセンスを持たない Copilot Chat ユーザーでは、指示や公開Webだけを使うエージェントは無料ですが、SharePoint などの社内データを使うと Copilot クレジットによる従量課金の対象になります。料金体系は変わりやすいため、導入前に公式情報を確認してください。",{"q":36,"a":37},"野良エージェントとは何ですか？どう防げばよいですか？","所有者や目的が分からないまま社内に残り、誰も管理していないエージェントのことです。作成者の退職や参照先の資料の古さが原因で、誤った回答を返し続けるおそれがあります。社内の台帳で所有者と見直し日を管理し、Microsoft 365 管理センターで所有者のいないエージェントを確認・ブロックできるようにしておきます。",{"type":39,"children":40,"toc":2016},"root",[41,60,73,78,91,184,191,211,237,256,262,281,303,315,321,425,449,456,483,495,501,511,546,551,622,634,650,655,670,676,688,694,716,721,727,736,741,778,794,799,804,828,840,846,858,956,969,989,995,1022,1195,1205,1211,1216,1269,1285,1290,1296,1307,1335,1356,1368,1411,1417,1422,1434,1440,1459,1521,1542,1556,1576,1581,1596,1601,1606,1611,1627,1635,1648,1656,1691,1699,1735,1743,1779,1787,1812,1820,1860,1881,1893,1899,1904,1924,1937,1950,1955,2011],{"type":42,"tag":43,"props":44,"children":45},"element","p",{},[46,49,58],{"type":47,"value":48},"text","※ Microsoft 365 Copilot は、2026年8月から「Microsoft Copilot」に名称が変わりました（Copilot Chat は「Microsoft Copilot Chat」）。移行期間中は旧名称も併用されているため、本記事では広く使われている「Microsoft 365 Copilot」の表記で統一しています（出典：",{"type":42,"tag":50,"props":51,"children":55},"a",{"href":52,"rel":53},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fcopilot\u002Fplan\u002Fmicrosoft-365-copilot-privacy",[54],"nofollow",[56],{"type":47,"value":57},"Microsoft Learn「Microsoft Copilot のデータ、プライバシー、セキュリティ」",{"type":47,"value":59},"）。",{"type":42,"tag":43,"props":61,"children":62},{},[63,65,71],{"type":47,"value":64},"本シリーズではここまで、Microsoft 365 Copilot を導入し、社員が日常業務で「使う」ための準備と定着を扱ってきました。データの置き場所を整え、権限とルールを決め、研修とチャンピオン制度で使われる状態を作る——ここまで来た会社が次に向き合うのが、",{"type":42,"tag":66,"props":67,"children":68},"strong",{},[69],{"type":47,"value":70},"自社の業務に合わせたAIを「作る」段階",{"type":47,"value":72},"です。",{"type":42,"tag":43,"props":74,"children":75},{},[76],{"type":47,"value":77},"その中心にあるのがエージェントです。「社内規程の質問に答える」「見積もりの前に確認すべき点を洗い出す」といった特定の仕事に絞った Copilot を、IT部門ではなく現場の社員が作り、社内で共有できるようになっています。一方で、誰でも作れるからこそ、管理されないエージェントが増える問題も出てきます。",{"type":42,"tag":43,"props":79,"children":80},{},[81,83,89],{"type":47,"value":82},"本記事は",{"type":42,"tag":50,"props":84,"children":86},{"href":85},"\u002Farticles\u002Fm365-copilot-donyu-roadmap\u002F",[87],{"type":47,"value":88},"第1回：非IT企業のMicrosoft 365 Copilot導入ロードマップ",{"type":47,"value":90},"で示したフェーズ4の先、「その先のAI活用へ」を扱う第8回で、シリーズの完結編です。エージェントの作り方と使い分け、管理の考え方、料金の注意点を解説し、最後にシリーズ全体を振り返ります。",{"type":42,"tag":92,"props":93,"children":94},"blockquote",{},[95,103],{"type":42,"tag":43,"props":96,"children":97},{},[98],{"type":42,"tag":66,"props":99,"children":100},{},[101],{"type":47,"value":102},"この記事の要点",{"type":42,"tag":104,"props":105,"children":106},"ul",{},[107,140,160,172],{"type":42,"tag":108,"props":109,"children":110},"li",{},[111,113,118,120,125,127,131,133,138],{"type":47,"value":112},"エージェントとは、指示・知識・操作を設定した業務専用の Copilot です。簡単なものは",{"type":42,"tag":66,"props":114,"children":115},{},[116],{"type":47,"value":117},"エージェントビルダー",{"type":47,"value":119},"（ChatGPT の GPTs や Gemini の Gem の Microsoft 365 版）、決まった手順の自動化は",{"type":42,"tag":66,"props":121,"children":122},{},[123],{"type":47,"value":124},"Power Automate",{"type":47,"value":126},"、外部連携まで要るものは",{"type":42,"tag":66,"props":128,"children":129},{},[130],{"type":47,"value":20},{"type":47,"value":132},"、案件ごとの資料の束は",{"type":42,"tag":66,"props":134,"children":135},{},[136],{"type":47,"value":137},"Copilot Notebooks",{"type":47,"value":139},"で作ります",{"type":42,"tag":108,"props":141,"children":142},{},[143,145,151,153,158],{"type":47,"value":144},"エージェントとノートブックは、",{"type":42,"tag":50,"props":146,"children":148},{"href":147},"\u002Farticles\u002Fcopilot-data-okiba-box-sharepoint\u002F",[149],{"type":47,"value":150},"第2回前編",{"type":47,"value":152},"で整理した「学習の3層」の③",{"type":42,"tag":66,"props":154,"children":155},{},[156],{"type":47,"value":157},"整理・蓄積",{"type":47,"value":159},"を形にする道具です。暗黙知を書いて置く習慣があって初めて役に立ちます",{"type":42,"tag":108,"props":161,"children":162},{},[163,165,170],{"type":47,"value":164},"作る人が増えるほど、所有者不在の",{"type":42,"tag":66,"props":166,"children":167},{},[168],{"type":47,"value":169},"野良エージェント",{"type":47,"value":171},"が増えます。台帳・所有者2名・定期見直しのルールを、作り始める前に決めておきます",{"type":42,"tag":108,"props":173,"children":174},{},[175,177,182],{"type":47,"value":176},"当社の支援では、",{"type":42,"tag":66,"props":178,"children":179},{},[180],{"type":47,"value":181},"SharePoint へのアップロード → Power Automate → Copilot → Excel",{"type":47,"value":183}," の型で組むことが多く、精度とAIのクレジットの消費を見て、AIに任せる部分を読み取りなどに絞っています",{"type":42,"tag":185,"props":186,"children":188},"h2",{"id":187},"microsoft-365-copilotのエージェントとは",[189],{"type":47,"value":190},"Microsoft 365 Copilotのエージェントとは",{"type":42,"tag":43,"props":192,"children":193},{},[194,196,201,203,210],{"type":47,"value":195},"Microsoft 365 Copilot のエージェントとは、",{"type":42,"tag":66,"props":197,"children":198},{},[199],{"type":47,"value":200},"特定の業務やテーマに合わせて、指示・知識・操作を設定した専用のAIアシスタント",{"type":47,"value":202},"です。Microsoft は、エージェントを「特定の領域に合わせた特殊なAIアシスタントとして Copilot の機能を拡張するもの」と説明しており、情報の取得や要約に加えて、メールの送信や記録の更新といった操作を行うこともできます（出典：",{"type":42,"tag":50,"props":204,"children":207},{"href":205,"rel":206},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-365\u002Fcopilot\u002Fextensibility\u002Fagents-overview",[54],[208],{"type":47,"value":209},"Microsoft Learn「Microsoft 365 Copilot のエージェント」",{"type":47,"value":59},{"type":42,"tag":43,"props":212,"children":213},{},[214,216,221,223,228,230,235],{"type":47,"value":215},"構成要素は、どんな役割でどう答えるかの",{"type":42,"tag":66,"props":217,"children":218},{},[219],{"type":47,"value":220},"指示",{"type":47,"value":222},"、何を参照するかの",{"type":42,"tag":66,"props":224,"children":225},{},[226],{"type":47,"value":227},"知識",{"type":47,"value":229},"（SharePoint の規程フォルダなど）、答える以外に何を実行するかの",{"type":42,"tag":66,"props":231,"children":232},{},[233],{"type":47,"value":234},"操作",{"type":47,"value":236},"（申請の起票など）の3つです。",{"type":42,"tag":43,"props":238,"children":239},{},[240,242,247,249,254],{"type":47,"value":241},"種類は、Copilot のAIモデルと処理の流れをそのまま使う",{"type":42,"tag":66,"props":243,"children":244},{},[245],{"type":47,"value":246},"宣言型エージェント",{"type":47,"value":248},"と、独自のモデルや処理を組み込む",{"type":42,"tag":66,"props":250,"children":251},{},[252],{"type":47,"value":253},"カスタムエンジンエージェント",{"type":47,"value":255},"の2つで、非IT企業が社内で作るのはほとんどが前者です。",{"type":42,"tag":185,"props":257,"children":259},{"id":258},"使う民主化から作る民主化へ",[260],{"type":47,"value":261},"「使う民主化」から「作る民主化」へ",{"type":42,"tag":43,"props":263,"children":264},{},[265,267,272,274,279],{"type":47,"value":266},"生成AIの社内活用には、全社員がAIを",{"type":42,"tag":66,"props":268,"children":269},{},[270],{"type":47,"value":271},"使える",{"type":47,"value":273},"ようにする段階と、現場の社員が自分の業務に合わせたAIを",{"type":42,"tag":66,"props":275,"children":276},{},[277],{"type":47,"value":278},"作れる",{"type":47,"value":280},"ようにする段階があります。",{"type":42,"tag":43,"props":282,"children":283},{},[284,286,293,295,302],{"type":47,"value":285},"後者に踏み込んでいるのが、日用品メーカーのライオンです。同社は2025年6月、社内生成AIに共通業務のエージェントを実装するとともに、非エンジニアを含むビジネス部門から100名の「AIエージェント開発者」を育成し、2025年度内に各部門固有の30体以上のエージェントを本格運用することを目指すと発表しました。2026年度以降は、そこで得た開発ノウハウを各部門やグループ各社に共有していくとしています（出典：",{"type":42,"tag":50,"props":287,"children":290},{"href":288,"rel":289},"https:\u002F\u002Fwww.lion.co.jp\u002Fja\u002Fnewsroom\u002Fnews\u002F2025\u002F4923",[54],[291],{"type":47,"value":292},"ライオン ニュースリリース（2025年6月24日）",{"type":47,"value":294},"）。同社はこれを「生成AIの民主化」と呼んでいます（参考：",{"type":42,"tag":50,"props":296,"children":299},{"href":297,"rel":298},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=xgBkuYGWFYg",[54],[300],{"type":47,"value":301},"PIVOT「&Questions」",{"type":47,"value":59},{"type":42,"tag":43,"props":304,"children":305},{},[306,308,313],{"type":47,"value":307},"中小企業がこの規模をそのまま真似する必要はありません。ただし、",{"type":42,"tag":66,"props":309,"children":310},{},[311],{"type":47,"value":312},"業務を知っている人が作り、作ったものとノウハウを社内で共有する",{"type":47,"value":314},"という方向性は、規模に関係なく参考になります。Microsoft 365 Copilot では、そのための道具がすでに用意されています。",{"type":42,"tag":185,"props":316,"children":318},{"id":317},"作る道具は3つ-エージェントビルダーcopilot-studiocopilot-notebooks",[319],{"type":47,"value":320},"作る道具は3つ ― エージェントビルダー・Copilot Studio・Copilot Notebooks",{"type":42,"tag":322,"props":323,"children":324},"table",{},[325,354],{"type":42,"tag":326,"props":327,"children":328},"thead",{},[329],{"type":42,"tag":330,"props":331,"children":332},"tr",{},[333,339,344,349],{"type":42,"tag":334,"props":335,"children":336},"th",{},[337],{"type":47,"value":338},"道具",{"type":42,"tag":334,"props":340,"children":341},{},[342],{"type":47,"value":343},"向いているもの",{"type":42,"tag":334,"props":345,"children":346},{},[347],{"type":47,"value":348},"どこで作るか",{"type":42,"tag":334,"props":350,"children":351},{},[352],{"type":47,"value":353},"ポイント",{"type":42,"tag":355,"props":356,"children":357},"tbody",{},[358,381,403],{"type":42,"tag":330,"props":359,"children":360},{},[361,366,371,376],{"type":42,"tag":362,"props":363,"children":364},"td",{},[365],{"type":47,"value":117},{"type":42,"tag":362,"props":367,"children":368},{},[369],{"type":47,"value":370},"指示と社内ファイルなどの知識だけで動く、社内向けの簡単なエージェント",{"type":42,"tag":362,"props":372,"children":373},{},[374],{"type":47,"value":375},"Microsoft 365 Copilot アプリ、Teams",{"type":42,"tag":362,"props":377,"children":378},{},[379],{"type":47,"value":380},"会話しながら作れる。作ったエージェントは Microsoft 365 Copilot ライセンスに含まれる",{"type":42,"tag":330,"props":382,"children":383},{},[384,388,393,398],{"type":42,"tag":362,"props":385,"children":386},{},[387],{"type":47,"value":20},{"type":42,"tag":362,"props":389,"children":390},{},[391],{"type":47,"value":392},"外部サービスとの連携、ワークフローの自動実行など、操作が必要なエージェント",{"type":42,"tag":362,"props":394,"children":395},{},[396],{"type":47,"value":397},"Copilot Studio の画面",{"type":42,"tag":362,"props":399,"children":400},{},[401],{"type":47,"value":402},"できることは多いが、設計と管理の負担も大きい。利用方法によって追加の費用がかかる",{"type":42,"tag":330,"props":404,"children":405},{},[406,410,415,420],{"type":42,"tag":362,"props":407,"children":408},{},[409],{"type":47,"value":137},{"type":42,"tag":362,"props":411,"children":412},{},[413],{"type":47,"value":414},"案件やテーマごとに資料・会議・メールを束ね、繰り返し質問や下書きに使う",{"type":42,"tag":362,"props":416,"children":417},{},[418],{"type":47,"value":419},"Microsoft 365 Copilot アプリの「ノートブック」、OneNote",{"type":42,"tag":362,"props":421,"children":422},{},[423],{"type":47,"value":424},"エージェントのような設定は不要。共有した相手と一緒に使える",{"type":42,"tag":426,"props":427,"children":428},"picture",{},[429,431,439,440],{"type":47,"value":430},"\n  ",{"type":42,"tag":432,"props":433,"children":438},"source",{"media":434,"srcSet":435,"width":436,"height":437},"(max-width: 768px)","\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Ftsukau-dougu-sp.svg",420,736,[],{"type":47,"value":430},{"type":42,"tag":441,"props":442,"children":448},"img",{"src":443,"alt":444,"width":445,"height":446,"loading":447},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Ftsukau-dougu.svg","作る道具の使い分け：案件やテーマの資料を束ねるならCopilot Notebooks、指示と知識だけで動くならエージェントビルダー、外部連携や自動実行が必要ならCopilot Studio",800,380,"lazy",[],{"type":42,"tag":450,"props":451,"children":453},"h3",{"id":452},"エージェントビルダー-まずはここから",[454],{"type":47,"value":455},"エージェントビルダー ― まずはここから",{"type":42,"tag":43,"props":457,"children":458},{},[459,461,466,468,473,475,482],{"type":47,"value":460},"エージェントビルダーは、Microsoft 365 Copilot アプリや Teams から、会話形式で宣言型エージェントを作れる機能です。すでに ChatGPT の GPTs や Gemini の Gem を触ったことがあれば、",{"type":42,"tag":66,"props":462,"children":463},{},[464],{"type":47,"value":465},"その Microsoft 365 版",{"type":47,"value":467},"と考えると分かりやすいです。役割や答え方の指示を書き、参照する知識を指定して、自分用のAIを作って共有する、という組み立ては同じです。違いは、知識として社内の SharePoint のファイルを指定でき、",{"type":42,"tag":66,"props":469,"children":470},{},[471],{"type":47,"value":472},"誰が何を見られるかは Microsoft 365 の権限がそのまま効く",{"type":47,"value":474},"こと、管理者が組織として管理できることです。SharePoint 上のファイルなどを知識として指定し、テストしてから社内の他のユーザーと共有できます。Microsoft は、エージェントビルダーで作るエージェントは Microsoft 365 Copilot ライセンスに含まれるとし、外部サービスと連携する操作などの高度な機能が必要な場合は Copilot Studio を使うよう案内しています（出典：",{"type":42,"tag":50,"props":476,"children":479},{"href":477,"rel":478},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-365\u002Fcopilot\u002Fextensibility\u002Fagent-builder",[54],[480],{"type":47,"value":481},"Microsoft Learn「Microsoft 365 Copilot のエージェント ビルダー」",{"type":47,"value":59},{"type":42,"tag":43,"props":484,"children":485},{},[486,488,493],{"type":47,"value":487},"注意点として、知識に指定した SharePoint のファイルやフォルダは、共有先の全員が閲覧できるように自動で設定されるとは限りません。エージェントを共有したのに「答えが返ってこない」場合は、参照先のファイルの権限を確認します。これはシリーズ第3回で扱う SharePoint の権限設計と同じ考え方で、",{"type":42,"tag":66,"props":489,"children":490},{},[491],{"type":47,"value":492},"エージェントも、使う人が見られる情報しか答えに使えない",{"type":47,"value":494},"ということです。",{"type":42,"tag":450,"props":496,"children":498},{"id":497},"その前に-power-automate-で足りることも多い",[499],{"type":47,"value":500},"その前に ― Power Automate で足りることも多い",{"type":42,"tag":43,"props":502,"children":503},{},[504,506],{"type":47,"value":505},"「業務の自動化まで踏み込みたい」と思ったとき、いきなり Copilot Studio に向かう必要はありません。",{"type":42,"tag":66,"props":507,"children":508},{},[509],{"type":47,"value":510},"決まった手順を決まった順番で流すだけなら、Power Automate のクラウドフローで足ります。",{"type":42,"tag":104,"props":512,"children":513},{},[514,519,533],{"type":42,"tag":108,"props":515,"children":516},{},[517],{"type":47,"value":518},"SharePoint・Outlook・Teams・Excel などは、Power Automate の標準のコネクタでつながります（「ファイルが追加されたら」「メールが届いたら」を起点に、承認を回す、ファイルを移す、通知する）",{"type":42,"tag":108,"props":520,"children":521},{},[522,524,531],{"type":47,"value":523},"フローは自然言語で下書きできます。Microsoft は、Power Automate の Copilot について「自然言語で指定した手順を使用して、目標を達成するソリューションを提案します」と説明しています（出典：",{"type":42,"tag":50,"props":525,"children":528},{"href":526,"rel":527},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fpower-automate\u002Fcopilot-overview",[54],[529],{"type":47,"value":530},"Microsoft Learn「Power Automate の Copilot」",{"type":47,"value":532},"）",{"type":42,"tag":108,"props":534,"children":535},{},[536,538,545],{"type":47,"value":537},"「本文を要約する」「問い合わせを分類する」のようにAIの判断を挟みたいところだけ、フローの途中にプロンプト（生成AIに処理させる部品）を差し込めます。プロンプトは Power Automate の画面から作成でき、フローの中から呼び出せます（出典：",{"type":42,"tag":50,"props":539,"children":542},{"href":540,"rel":541},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-copilot-studio\u002Fcreate-custom-prompt",[54],[543],{"type":47,"value":544},"Microsoft Learn「プロンプトを作成する」",{"type":47,"value":532},{"type":42,"tag":43,"props":547,"children":548},{},[549],{"type":47,"value":550},"使い分けの目安は次のとおりです。",{"type":42,"tag":322,"props":552,"children":553},{},[554,570],{"type":42,"tag":326,"props":555,"children":556},{},[557],{"type":42,"tag":330,"props":558,"children":559},{},[560,565],{"type":42,"tag":334,"props":561,"children":562},{},[563],{"type":47,"value":564},"やりたいこと",{"type":42,"tag":334,"props":566,"children":567},{},[568],{"type":47,"value":569},"向いている道具",{"type":42,"tag":355,"props":571,"children":572},{},[573,585,597,610],{"type":42,"tag":330,"props":574,"children":575},{},[576,581],{"type":42,"tag":362,"props":577,"children":578},{},[579],{"type":47,"value":580},"人が質問し、社内の資料をもとに答えてほしい",{"type":42,"tag":362,"props":582,"children":583},{},[584],{"type":47,"value":117},{"type":42,"tag":330,"props":586,"children":587},{},[588,593],{"type":42,"tag":362,"props":589,"children":590},{},[591],{"type":47,"value":592},"決まった手順を自動で流したい（承認、転記、通知、定期処理）",{"type":42,"tag":362,"props":594,"children":595},{},[596],{"type":47,"value":124},{"type":42,"tag":330,"props":598,"children":599},{},[600,605],{"type":42,"tag":362,"props":601,"children":602},{},[603],{"type":47,"value":604},"手順の一部でAIに要約・分類・下書きをさせたい",{"type":42,"tag":362,"props":606,"children":607},{},[608],{"type":47,"value":609},"Power Automate ＋ プロンプト",{"type":42,"tag":330,"props":611,"children":612},{},[613,618],{"type":42,"tag":362,"props":614,"children":615},{},[616],{"type":47,"value":617},"人との会話の中で、外部サービスの照会や更新まで行わせたい",{"type":42,"tag":362,"props":619,"children":620},{},[621],{"type":47,"value":20},{"type":42,"tag":43,"props":623,"children":624},{},[625,627,632],{"type":47,"value":626},"当社の支援先でも、最初に挙がる「自動化したいこと」の多くは、会話するエージェントではなく",{"type":42,"tag":66,"props":628,"children":629},{},[630],{"type":47,"value":631},"決まった手順の自動化",{"type":47,"value":633},"でした。Power Automate で形にし、判断が要る部分だけAIに任せる組み立てのほうが、作るのも直すのも簡単です。",{"type":42,"tag":92,"props":635,"children":636},{},[637,645],{"type":42,"tag":43,"props":638,"children":639},{},[640],{"type":42,"tag":66,"props":641,"children":642},{},[643],{"type":47,"value":644},"K.S.Rogers の現場から",{"type":42,"tag":43,"props":646,"children":647},{},[648],{"type":47,"value":649},"当社がよく使うのは、SharePoint のフォルダにファイルをアップロードすると Power Automate が動き、Copilot で処理して、結果を Excel に書き出す、という型です。支援先で個別の業務から入っても、型でくくると「帳票の読み取り・転記」「集計・報告書の作成」「紙の記録のデータ化と検索」「予定の共有」の4つ程度にまとまります。入口・処理・出口を同じ形にそろえておくと、1つの部署で作った仕組みを、別の業務や別の部署にも持ち込みやすくなります。",{"type":42,"tag":43,"props":651,"children":652},{},[653],{"type":47,"value":654},"型の中でAIに任せる範囲は、実際に動かして精度を見てから決めます。",{"type":42,"tag":92,"props":656,"children":657},{},[658,665],{"type":42,"tag":43,"props":659,"children":660},{},[661],{"type":42,"tag":66,"props":662,"children":663},{},[664],{"type":47,"value":644},{"type":42,"tag":43,"props":666,"children":667},{},[668],{"type":47,"value":669},"ある支援先では、Copilot に処理を任せたところ、精度が足りませんでした。そこで、手順として決められる部分は Excel の Office Scripts（Excel の操作をスクリプトで自動実行する仕組み）で組み、AIには読み取りだけを任せる形に切り替えました。AIに任せる範囲を絞ると結果がぶれにくくなり、誤りが出たときもどこを直せばよいか分かります。「AIで全部やる」より「手順で組めるところは手順で組む」ほうが、現場で安心して使える仕組みになります。",{"type":42,"tag":450,"props":671,"children":673},{"id":672},"copilot-studio-操作と連携が必要になったら",[674],{"type":47,"value":675},"Copilot Studio ― 操作と連携が必要になったら",{"type":42,"tag":43,"props":677,"children":678},{},[679,681,686],{"type":47,"value":680},"Copilot Studio は、外部サービスとの連携や条件に応じた自動実行を組み込める開発ツールです。ノーコード・ローコードで作れますが、「どのデータに、誰の権限でアクセスし、何を実行するか」の設計と保守が必要です。非IT企業では、",{"type":42,"tag":66,"props":682,"children":683},{},[684],{"type":47,"value":685},"最初からCopilot Studioで作り込まず",{"type":47,"value":687},"、エージェントビルダーや Power Automate で試して「会話の中でこの操作まで自動にしたい」という具体的な要望が出てから移るほうが、使われないエージェントを避けられます。",{"type":42,"tag":450,"props":689,"children":691},{"id":690},"copilot-notebooks-案件ごとの判断材料を束ねる",[692],{"type":47,"value":693},"Copilot Notebooks ― 案件ごとの判断材料を束ねる",{"type":42,"tag":43,"props":695,"children":696},{},[697,699,706,708,715],{"type":47,"value":698},"Copilot Notebooks（Copilot ノートブック）は、ファイル、会議のメモ、メール、Copilot とのチャットなどを1か所に集め、その内容に基づいて質問に答えさせたり、新しい下書きを作らせたりできる作業場所です。ノートブックはチームと共有でき、Microsoft 365 Copilot のライセンスがなくても Copilot Chat のユーザーであれば利用できます（作成には SharePoint または OneDrive のライセンスが必要です）（出典：",{"type":42,"tag":50,"props":700,"children":703},{"href":701,"rel":702},"https:\u002F\u002Fsupport.microsoft.com\u002Fja-jp\u002Fmicrosoft-365-copilot\u002Fget-started-with-microsoft-365-copilot-notebooks",[54],[704],{"type":47,"value":705},"Microsoft サポート「Copilot ノートブックの使用を開始する」",{"type":47,"value":707},"、",{"type":42,"tag":50,"props":709,"children":712},{"href":710,"rel":711},"https:\u002F\u002Fsupport.microsoft.com\u002Fja-jp\u002Fmicrosoft-365-copilot\u002Ffrequently-asked-questions-about-microsoft-365-copilot-notebooks",[54],[713],{"type":47,"value":714},"Microsoft サポート「Microsoft 365 Copilot ノートブックについてよく寄せられる質問」",{"type":47,"value":59},{"type":42,"tag":43,"props":717,"children":718},{},[719],{"type":47,"value":720},"なお、2026年9月時点では、ノートブックに招待したユーザーは全員が編集できる権限を持ち、読み取り専用のメンバーは設定できないとされています。共有する相手は、編集されてもよい関係者に絞ります。",{"type":42,"tag":185,"props":722,"children":724},{"id":723},"学習の3層の整理蓄積を形にする",[725],{"type":47,"value":726},"「学習の3層」の③整理・蓄積を形にする",{"type":42,"tag":43,"props":728,"children":729},{},[730,734],{"type":42,"tag":50,"props":731,"children":732},{"href":147},[733],{"type":47,"value":150},{"type":47,"value":735},"では、「AIに学習させる」という言葉を3つの層に分けました。①モデルの学習（Copilot では行われない）、②参照（質問のたびに社内データを検索して答える、Copilot の本体）、③整理・蓄積（特定のテーマの資料ややりとりを束ね、繰り返し判断材料を引き出せる形にする）です。前編では「③の使い方は第8回で本格的に扱う」と予告しました。",{"type":42,"tag":43,"props":737,"children":738},{},[739],{"type":47,"value":740},"③を形にする道具が、ノートブックとエージェントです。使い分けは次のとおりです。",{"type":42,"tag":104,"props":742,"children":743},{},[744,761],{"type":42,"tag":108,"props":745,"children":746},{},[747,752,754,759],{"type":42,"tag":66,"props":748,"children":749},{},[750],{"type":47,"value":751},"ノートブック",{"type":47,"value":753},"：案件やプロジェクトのように、",{"type":42,"tag":66,"props":755,"children":756},{},[757],{"type":47,"value":758},"期間が決まっていて、関係者が限られる",{"type":47,"value":760},"判断材料の束",{"type":42,"tag":108,"props":762,"children":763},{},[764,769,771,776],{"type":42,"tag":66,"props":765,"children":766},{},[767],{"type":47,"value":768},"エージェント",{"type":47,"value":770},"：社内規程や製品知識のように、",{"type":42,"tag":66,"props":772,"children":773},{},[774],{"type":47,"value":775},"期間を問わず、多くの人から繰り返し聞かれる",{"type":47,"value":777},"問いへの窓口",{"type":42,"tag":426,"props":779,"children":780},{},[781,782,787,788],{"type":47,"value":430},{"type":42,"tag":432,"props":783,"children":786},{"media":434,"srcSet":784,"width":436,"height":785},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Fgakushu-3so-3-sp.svg",558,[],{"type":47,"value":430},{"type":42,"tag":441,"props":789,"children":793},{"src":790,"alt":791,"width":445,"height":792,"loading":447},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Fgakushu-3so-3.svg","学習の3層のうち③整理・蓄積の形：案件ごとの判断材料はCopilot Notebooksで束ね、繰り返し聞かれる問いはエージェントにする。どちらも書かれてM365の中に置かれた情報が材料になる",400,[],{"type":42,"tag":450,"props":795,"children":797},{"id":796},"案件別の意思決定ノートを作る",[798],{"type":47,"value":796},{"type":42,"tag":43,"props":800,"children":801},{},[802],{"type":47,"value":803},"経営者の「過去の判断の経緯を、後から引き出せるようにしたい」という要望に応えるのが、案件ごとの意思決定ノートです。進め方は次のとおりです。",{"type":42,"tag":805,"props":806,"children":807},"ol",{},[808,813,818,823],{"type":42,"tag":108,"props":809,"children":810},{},[811],{"type":47,"value":812},"案件ごとに SharePoint のフォルダ（または Teams のチャネル）を用意する",{"type":42,"tag":108,"props":814,"children":815},{},[816],{"type":47,"value":817},"会議のたびに「決定事項・決めた理由・却下した案・未決事項」を短く書いて置く（Teams 会議の要約を下書きに使ってよい）",{"type":42,"tag":108,"props":819,"children":820},{},[821],{"type":47,"value":822},"案件のノートブックを作り、見積書、議事録、顧客とのメール、決定メモを参照として追加する",{"type":42,"tag":108,"props":824,"children":825},{},[826],{"type":47,"value":827},"案件の途中や終了後に「この仕様に決めた理由は何だったか」「同じ顧客から過去に出た変更要望は何か」とノートブックに聞く",{"type":42,"tag":43,"props":829,"children":830},{},[831,833,838],{"type":47,"value":832},"ここで大切なのは、",{"type":42,"tag":66,"props":834,"children":835},{},[836],{"type":47,"value":837},"AIに材料を渡す前に、判断の理由を書いて置く習慣を作る",{"type":47,"value":839},"ことです。第2回前編で述べたとおり、暗黙知は書かれて Microsoft 365 の中に置かれて初めてAIの材料になります。ノートブックもエージェントも、書かれていない判断理由を補ってはくれません。",{"type":42,"tag":185,"props":841,"children":843},{"id":842},"非it企業でのエージェント活用例-最初に作るなら",[844],{"type":47,"value":845},"非IT企業でのエージェント活用例 ― 最初に作るなら",{"type":42,"tag":43,"props":847,"children":848},{},[849,851,856],{"type":47,"value":850},"「AIエージェントで業務効率化」と聞くと大がかりに感じますが、最初に作るべきなのは、",{"type":42,"tag":66,"props":852,"children":853},{},[854],{"type":47,"value":855},"質問の範囲がはっきりしていて、答えの根拠となる資料がすでにある",{"type":47,"value":857},"エージェントです。",{"type":42,"tag":322,"props":859,"children":860},{},[861,881],{"type":42,"tag":326,"props":862,"children":863},{},[864],{"type":42,"tag":330,"props":865,"children":866},{},[867,871,876],{"type":42,"tag":334,"props":868,"children":869},{},[870],{"type":47,"value":768},{"type":42,"tag":334,"props":872,"children":873},{},[874],{"type":47,"value":875},"参照する知識",{"type":42,"tag":334,"props":877,"children":878},{},[879],{"type":47,"value":880},"効きどころ",{"type":42,"tag":355,"props":882,"children":883},{},[884,902,920,938],{"type":42,"tag":330,"props":885,"children":886},{},[887,892,897],{"type":42,"tag":362,"props":888,"children":889},{},[890],{"type":47,"value":891},"社内規程の問い合わせ窓口",{"type":42,"tag":362,"props":893,"children":894},{},[895],{"type":47,"value":896},"就業規則、経費規程、各種申請の手順書",{"type":42,"tag":362,"props":898,"children":899},{},[900],{"type":47,"value":901},"総務への同じ質問が減る",{"type":42,"tag":330,"props":903,"children":904},{},[905,910,915],{"type":42,"tag":362,"props":906,"children":907},{},[908],{"type":47,"value":909},"新人の受け入れ案内",{"type":42,"tag":362,"props":911,"children":912},{},[913],{"type":47,"value":914},"入社手続き、部署紹介、よく使うシステムの手順",{"type":42,"tag":362,"props":916,"children":917},{},[918],{"type":47,"value":919},"教える側の負担と、聞きにくさが減る",{"type":42,"tag":330,"props":921,"children":922},{},[923,928,933],{"type":42,"tag":362,"props":924,"children":925},{},[926],{"type":47,"value":927},"見積もり前のチェック",{"type":42,"tag":362,"props":929,"children":930},{},[931],{"type":47,"value":932},"過去の見積もりの注意点、社内の値付けルール",{"type":42,"tag":362,"props":934,"children":935},{},[936],{"type":47,"value":937},"確認漏れと、ベテランへの確認待ちが減る",{"type":42,"tag":330,"props":939,"children":940},{},[941,946,951],{"type":42,"tag":362,"props":942,"children":943},{},[944],{"type":47,"value":945},"製品・サービスの問い合わせ下書き",{"type":42,"tag":362,"props":947,"children":948},{},[949],{"type":47,"value":950},"製品資料、FAQ、過去の回答例",{"type":42,"tag":362,"props":952,"children":953},{},[954],{"type":47,"value":955},"回答の品質がそろい、下書きの時間が減る",{"type":42,"tag":43,"props":957,"children":958},{},[959,961,967],{"type":47,"value":960},"ライオンの育成プログラムでも、成果物の例として「アンケートの自由回答の解析」「申請書類の事前添削」といった、部門や個人の業務に特化したエージェントが挙げられています（出典：",{"type":42,"tag":50,"props":962,"children":964},{"href":288,"rel":963},[54],[965],{"type":47,"value":966},"ライオン ニュースリリース",{"type":47,"value":968},"）。いずれも、対象の業務が具体的で、効果を測りやすいものです。",{"type":42,"tag":43,"props":970,"children":971},{},[972,974,979,981,987],{"type":47,"value":973},"一方、請求書の読み取りと基幹システムへの転記、複数のシステムをまたぐ照合のように、",{"type":42,"tag":66,"props":975,"children":976},{},[977],{"type":47,"value":978},"判断よりも決まった処理を大量に回す業務",{"type":47,"value":980},"は、Copilot のエージェントより、業務システムと直接つないだ自動化のほうが向いています。K.S.Rogers の支援でも、請求書の仕分けと転記の自動化で月次経理作業の負担を65%削減し、決算業務を2営業日前倒しした事例があります（",{"type":42,"tag":50,"props":982,"children":984},{"href":983},"\u002Fbusiness\u002Fopezero\u002F",[985],{"type":47,"value":986},"OpeZero",{"type":47,"value":988},"の導入事例）。",{"type":42,"tag":185,"props":990,"children":992},{"id":991},"誰がどこまで作るか-段階別の目安",[993],{"type":47,"value":994},"誰がどこまで作るか ― 段階別の目安",{"type":42,"tag":43,"props":996,"children":997},{},[998,1000,1005,1007,1013,1015,1020],{"type":47,"value":999},"「全社員がエージェントを作れるようになるべきか」と聞かれることがありますが、",{"type":42,"tag":66,"props":1001,"children":1002},{},[1003],{"type":47,"value":1004},"その必要はありません",{"type":47,"value":1006},"。",{"type":42,"tag":50,"props":1008,"children":1010},{"href":1009},"\u002Farticles\u002Fcopilot-shanai-kenshu-susumekata\u002F",[1011],{"type":47,"value":1012},"第7回（後編）：社内研修の進め方",{"type":47,"value":1014},"で示した入門・初級・中級・上級の段階に沿って、",{"type":42,"tag":66,"props":1016,"children":1017},{},[1018],{"type":47,"value":1019},"どこまでできれば十分か",{"type":47,"value":1021},"を整理すると、次のようになります。",{"type":42,"tag":322,"props":1023,"children":1024},{},[1025,1051],{"type":42,"tag":326,"props":1026,"children":1027},{},[1028],{"type":42,"tag":330,"props":1029,"children":1030},{},[1031,1036,1041,1046],{"type":42,"tag":334,"props":1032,"children":1033},{},[1034],{"type":47,"value":1035},"段階",{"type":42,"tag":334,"props":1037,"children":1038},{},[1039],{"type":47,"value":1040},"この段階の人に求めること",{"type":42,"tag":334,"props":1042,"children":1043},{},[1044],{"type":47,"value":1045},"作る道具",{"type":42,"tag":334,"props":1047,"children":1048},{},[1049],{"type":47,"value":1050},"求めないこと",{"type":42,"tag":355,"props":1052,"children":1053},{},[1054,1083,1113,1143,1173],{"type":42,"tag":330,"props":1055,"children":1056},{},[1057,1062,1073,1078],{"type":42,"tag":362,"props":1058,"children":1059},{},[1060],{"type":47,"value":1061},"入門（全員）",{"type":42,"tag":362,"props":1063,"children":1064},{},[1065,1067,1071],{"type":47,"value":1066},"社内で共有されたエージェントを",{"type":42,"tag":66,"props":1068,"children":1069},{},[1070],{"type":47,"value":271},{"type":47,"value":1072},"。指示の書き方の基本と、入力してよい情報が分かる",{"type":42,"tag":362,"props":1074,"children":1075},{},[1076],{"type":47,"value":1077},"―",{"type":42,"tag":362,"props":1079,"children":1080},{},[1081],{"type":47,"value":1082},"自分でエージェントを作ること",{"type":42,"tag":330,"props":1084,"children":1085},{},[1086,1091,1103,1108],{"type":42,"tag":362,"props":1087,"children":1088},{},[1089],{"type":47,"value":1090},"初級",{"type":42,"tag":362,"props":1092,"children":1093},{},[1094,1096,1101],{"type":47,"value":1095},"公開されたエージェントを",{"type":42,"tag":66,"props":1097,"children":1098},{},[1099],{"type":47,"value":1100},"業務の中で使い分けられる",{"type":47,"value":1102},"。うまく答えないときに聞き方を変えられる",{"type":42,"tag":362,"props":1104,"children":1105},{},[1106],{"type":47,"value":1107},"―（ノートブックを共有されて使うところまで）",{"type":42,"tag":362,"props":1109,"children":1110},{},[1111],{"type":47,"value":1112},"設定を変えること",{"type":42,"tag":330,"props":1114,"children":1115},{},[1116,1121,1133,1138],{"type":42,"tag":362,"props":1117,"children":1118},{},[1119],{"type":47,"value":1120},"中級",{"type":42,"tag":362,"props":1122,"children":1123},{},[1124,1126,1131],{"type":47,"value":1125},"自分やチームの案件で",{"type":42,"tag":66,"props":1127,"children":1128},{},[1129],{"type":47,"value":1130},"ノートブックを作れる",{"type":47,"value":1132},"。部署内向けの簡単なエージェントを試せる",{"type":42,"tag":362,"props":1134,"children":1135},{},[1136],{"type":47,"value":1137},"Copilot Notebooks、エージェントビルダー",{"type":42,"tag":362,"props":1139,"children":1140},{},[1141],{"type":47,"value":1142},"全社公開、外部サービスとの連携",{"type":42,"tag":330,"props":1144,"children":1145},{},[1146,1151,1163,1168],{"type":42,"tag":362,"props":1147,"children":1148},{},[1149],{"type":47,"value":1150},"上級（チャンピオン・作る人）",{"type":42,"tag":362,"props":1152,"children":1153},{},[1154,1156,1161],{"type":47,"value":1155},"部署の業務に合わせた",{"type":42,"tag":66,"props":1157,"children":1158},{},[1159],{"type":47,"value":1160},"エージェントを作って共有できる",{"type":47,"value":1162},"。台帳に登録し、見直しまで回せる",{"type":42,"tag":362,"props":1164,"children":1165},{},[1166],{"type":47,"value":1167},"エージェントビルダー、Power Automate",{"type":42,"tag":362,"props":1169,"children":1170},{},[1171],{"type":47,"value":1172},"Copilot Studio での作り込み（必要なら情シス・外部と組む）",{"type":42,"tag":330,"props":1174,"children":1175},{},[1176,1181,1186,1191],{"type":42,"tag":362,"props":1177,"children":1178},{},[1179],{"type":47,"value":1180},"情シス・推進責任者",{"type":42,"tag":362,"props":1182,"children":1183},{},[1184],{"type":47,"value":1185},"全社公開の承認、台帳の管理、権限と料金の確認",{"type":42,"tag":362,"props":1187,"children":1188},{},[1189],{"type":47,"value":1190},"管理センター、必要に応じて Copilot Studio",{"type":42,"tag":362,"props":1192,"children":1193},{},[1194],{"type":47,"value":1077},{"type":42,"tag":43,"props":1196,"children":1197},{},[1198,1203],{"type":42,"tag":66,"props":1199,"children":1200},{},[1201],{"type":47,"value":1202},"入門・初級の人は「使う」だけで十分",{"type":47,"value":1204},"です。第7回（後編）で書いたとおり、全員が上級を目指す必要はありません。作る人は各部署に1〜2名いれば回り始めます。中級の人がノートブックを作り始めたら、上級への入り口に立っています。",{"type":42,"tag":185,"props":1206,"children":1208},{"id":1207},"エージェントの作り方-5つのステップ",[1209],{"type":47,"value":1210},"エージェントの作り方 ― 5つのステップ",{"type":42,"tag":43,"props":1212,"children":1213},{},[1214],{"type":47,"value":1215},"エージェントビルダーで最初のエージェントを作るときは、次の順番で進めます。",{"type":42,"tag":805,"props":1217,"children":1218},{},[1219,1229,1239,1249,1259],{"type":42,"tag":108,"props":1220,"children":1221},{},[1222,1227],{"type":42,"tag":66,"props":1223,"children":1224},{},[1225],{"type":47,"value":1226},"業務と問いを決める",{"type":47,"value":1228}," ―― 「誰が、どんな質問をするための窓口か」を1文で書く。範囲を広げすぎない",{"type":42,"tag":108,"props":1230,"children":1231},{},[1232,1237],{"type":42,"tag":66,"props":1233,"children":1234},{},[1235],{"type":47,"value":1236},"知識を選び、権限を確認する",{"type":47,"value":1238}," ―― 参照させる資料を最新版に絞り、使う人全員がその資料を閲覧できるか確認する。古い版や下書きは混ぜない",{"type":42,"tag":108,"props":1240,"children":1241},{},[1242,1247],{"type":42,"tag":66,"props":1243,"children":1244},{},[1245],{"type":47,"value":1246},"指示を書く",{"type":47,"value":1248}," ―― 役割、答え方、分からないときの対応（「規程にないことは推測せず、担当部署を案内する」など）を書く",{"type":42,"tag":108,"props":1250,"children":1251},{},[1252,1257],{"type":42,"tag":66,"props":1253,"children":1254},{},[1255],{"type":47,"value":1256},"意地悪な質問でテストする",{"type":47,"value":1258}," ―― 範囲外の質問、あいまいな質問、資料にない質問をして、推測で答えないかを確認する",{"type":42,"tag":108,"props":1260,"children":1261},{},[1262,1267],{"type":42,"tag":66,"props":1263,"children":1264},{},[1265],{"type":47,"value":1266},"所有者と共有範囲を決めて公開する",{"type":47,"value":1268}," ―― 所有者を2名決め、共有する部署を決めてから公開する。社内台帳に登録する",{"type":42,"tag":426,"props":1270,"children":1271},{},[1272,1273,1278,1279],{"type":47,"value":430},{"type":42,"tag":432,"props":1274,"children":1277},{"media":434,"srcSet":1275,"width":436,"height":1276},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Ftsukurikata-5steps-sp.svg",542,[],{"type":47,"value":430},{"type":42,"tag":441,"props":1280,"children":1284},{"src":1281,"alt":1282,"width":445,"height":1283,"loading":447},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Ftsukurikata-5steps.svg","エージェントの作り方5ステップ：業務と問いを決める、知識を選び権限を確認する、指示を書く、意地悪な質問でテストする、所有者と共有範囲を決めて公開する",300,[],{"type":42,"tag":43,"props":1286,"children":1287},{},[1288],{"type":47,"value":1289},"特に4つ目が重要です。エージェントは資料にないことでもそれらしく答えようとするため、「分からないときの振る舞い」を指示に書き、確かめてから共有します。",{"type":42,"tag":185,"props":1291,"children":1293},{"id":1292},"野良エージェント化に注意-作る前に決める管理のルール",[1294],{"type":47,"value":1295},"野良エージェント化に注意 ― 作る前に決める管理のルール",{"type":42,"tag":43,"props":1297,"children":1298},{},[1299,1301,1305],{"type":47,"value":1300},"作る人が増えると、必ず起きるのが",{"type":42,"tag":66,"props":1302,"children":1303},{},[1304],{"type":47,"value":169},{"type":47,"value":1306},"の問題です。野良エージェントとは、作成者の異動・退職や目的の消滅によって、誰も管理していないまま社内に残るエージェントのことです。放置すると、次のような問題が起きます。",{"type":42,"tag":104,"props":1308,"children":1309},{},[1310,1320,1330],{"type":42,"tag":108,"props":1311,"children":1312},{},[1313,1315],{"type":47,"value":1314},"参照先の資料が古いまま更新されず、",{"type":42,"tag":66,"props":1316,"children":1317},{},[1318],{"type":47,"value":1319},"誤った回答を返し続ける",{"type":42,"tag":108,"props":1321,"children":1322},{},[1323,1325],{"type":47,"value":1324},"同じ目的のエージェントが部署ごとに乱立し、",{"type":42,"tag":66,"props":1326,"children":1327},{},[1328],{"type":47,"value":1329},"どれを使えばいいか分からなくなる",{"type":42,"tag":108,"props":1331,"children":1332},{},[1333],{"type":47,"value":1334},"共有範囲や参照先の権限が、作成者の意図と違うまま広がる",{"type":42,"tag":43,"props":1336,"children":1337},{},[1338,1340,1347,1348,1355],{"type":47,"value":1339},"Microsoft 365 管理センターには、エージェントを管理する機能がそろってきています。組織内で共有されたエージェントの一覧（エージェント レジストリ）で作成者や状態を確認し、安全でない・規則に合わないと判断したエージェントをブロックできます。組織全体に公開するエージェントは、管理者の承認を経てエージェントストアに掲載する流れになっており、所有者のいないエージェントに所有者を割り当てる操作も用意されています。利用できる機能は契約中のライセンスによって異なります（出典：",{"type":42,"tag":50,"props":1341,"children":1344},{"href":1342,"rel":1343},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-agent-365\u002Fadmin\u002Fmanage-copilot-agents-integrated-apps?view=o365-worldwide",[54],[1345],{"type":47,"value":1346},"Microsoft Learn「Microsoft 365 管理センターでエージェントを管理する」",{"type":47,"value":707},{"type":42,"tag":50,"props":1349,"children":1352},{"href":1350,"rel":1351},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-agent-365\u002Fadmin\u002Fagent-365-overview?view=o365-worldwide",[54],[1353],{"type":47,"value":1354},"Microsoft Learn「Microsoft 365 管理センターでのエージェントの概要」",{"type":47,"value":59},{"type":42,"tag":43,"props":1357,"children":1358},{},[1359,1361,1366],{"type":47,"value":1360},"ただし、管理機能があっても、",{"type":42,"tag":66,"props":1362,"children":1363},{},[1364],{"type":47,"value":1365},"判断の基準は社内で決める",{"type":47,"value":1367},"必要があります。作り始める前に、次のルールを決めておきます。",{"type":42,"tag":104,"props":1369,"children":1370},{},[1371,1381,1391,1401],{"type":42,"tag":108,"props":1372,"children":1373},{},[1374,1379],{"type":42,"tag":66,"props":1375,"children":1376},{},[1377],{"type":47,"value":1378},"台帳に登録する",{"type":47,"value":1380}," ―― 名前、目的、所有者、参照先の資料、共有範囲、最終見直し日を一覧にする",{"type":42,"tag":108,"props":1382,"children":1383},{},[1384,1389],{"type":42,"tag":66,"props":1385,"children":1386},{},[1387],{"type":47,"value":1388},"所有者は2名にする",{"type":47,"value":1390}," ―― 異動・退職で所有者不在にならないようにする",{"type":42,"tag":108,"props":1392,"children":1393},{},[1394,1399],{"type":42,"tag":66,"props":1395,"children":1396},{},[1397],{"type":47,"value":1398},"半年に1回見直す",{"type":47,"value":1400}," ―― 使われていない、資料が古いエージェントは更新するか削除する",{"type":42,"tag":108,"props":1402,"children":1403},{},[1404,1409],{"type":42,"tag":66,"props":1405,"children":1406},{},[1407],{"type":47,"value":1408},"全社公開は申請制にする",{"type":47,"value":1410}," ―― 部署内での共有は自由に、全社に公開するものは推進責任者が確認する",{"type":42,"tag":450,"props":1412,"children":1414},{"id":1413},"エージェントを社内で共有するハブの考え方",[1415],{"type":47,"value":1416},"エージェントを社内で共有する「ハブ」の考え方",{"type":42,"tag":43,"props":1418,"children":1419},{},[1420],{"type":47,"value":1421},"作ったエージェントを部署に閉じず、社内で見つけて使えるようにする場所を、ここではエージェントハブと呼びます。Microsoft 365 Copilot では、管理者が承認したエージェントをエージェントストアで公開できるので、ストアを社内のハブとして運用するのが基本です。",{"type":42,"tag":43,"props":1423,"children":1424},{},[1425,1427,1432],{"type":47,"value":1426},"ハブを機能させるコツは、",{"type":42,"tag":66,"props":1428,"children":1429},{},[1430],{"type":47,"value":1431},"エージェントそのものに加えて、作り方のノウハウも共有する",{"type":47,"value":1433},"ことです。どんな指示を書いたらうまくいったか、どんな質問でテストしたか——ライオンが開発ノウハウの社内共有を次の段階に掲げているように、作り方が共有されると、2体目以降のエージェントは格段に作りやすくなります。第7回で扱った社内コミュニティを、作る人の情報交換の場としても使います。",{"type":42,"tag":185,"props":1435,"children":1437},{"id":1436},"エージェントの料金とライセンス2026年9月時点",[1438],{"type":47,"value":1439},"エージェントの料金とライセンス（2026年9月時点）",{"type":42,"tag":43,"props":1441,"children":1442},{},[1443,1445,1450,1452,1457],{"type":47,"value":1444},"エージェントの料金は、",{"type":42,"tag":66,"props":1446,"children":1447},{},[1448],{"type":47,"value":1449},"エージェントを使う人のライセンス",{"type":47,"value":1451},"と、",{"type":42,"tag":66,"props":1453,"children":1454},{},[1455],{"type":47,"value":1456},"エージェントが何を参照・実行するか",{"type":47,"value":1458},"で変わります。2026年9月時点の Microsoft の説明を整理すると、次のとおりです。",{"type":42,"tag":322,"props":1460,"children":1461},{},[1462,1483],{"type":42,"tag":326,"props":1463,"children":1464},{},[1465],{"type":42,"tag":330,"props":1466,"children":1467},{},[1468,1473,1478],{"type":42,"tag":334,"props":1469,"children":1470},{},[1471],{"type":47,"value":1472},"使う人",{"type":42,"tag":334,"props":1474,"children":1475},{},[1476],{"type":47,"value":1477},"指示や公開Webだけを使うエージェント",{"type":42,"tag":334,"props":1479,"children":1480},{},[1481],{"type":47,"value":1482},"SharePoint など社内データを使うエージェント",{"type":42,"tag":355,"props":1484,"children":1485},{},[1486,1504],{"type":42,"tag":330,"props":1487,"children":1488},{},[1489,1494,1499],{"type":42,"tag":362,"props":1490,"children":1491},{},[1492],{"type":47,"value":1493},"Microsoft 365 Copilot ライセンスあり",{"type":42,"tag":362,"props":1495,"children":1496},{},[1497],{"type":47,"value":1498},"追加料金なし",{"type":42,"tag":362,"props":1500,"children":1501},{},[1502],{"type":47,"value":1503},"追加料金なし（Copilot Chat・Teams・SharePoint で使う場合）",{"type":42,"tag":330,"props":1505,"children":1506},{},[1507,1512,1516],{"type":42,"tag":362,"props":1508,"children":1509},{},[1510],{"type":47,"value":1511},"ライセンスなし（Copilot Chat のみ）",{"type":42,"tag":362,"props":1513,"children":1514},{},[1515],{"type":47,"value":1498},{"type":42,"tag":362,"props":1517,"children":1518},{},[1519],{"type":47,"value":1520},"Copilot クレジットによる従量課金",{"type":42,"tag":43,"props":1522,"children":1523},{},[1524,1526,1533,1534,1541],{"type":47,"value":1525},"（出典：",{"type":42,"tag":50,"props":1527,"children":1530},{"href":1528,"rel":1529},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-365\u002Fcopilot\u002Fextensibility\u002Fcost-considerations",[54],[1531],{"type":47,"value":1532},"Microsoft Learn「Copilot 拡張オプションのライセンスとコストに関する考慮事項」",{"type":47,"value":707},{"type":42,"tag":50,"props":1535,"children":1538},{"href":1536,"rel":1537},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-copilot-studio\u002Fbilling-licensing",[54],[1539],{"type":47,"value":1540},"Microsoft Learn「Copilot Studio のライセンス」",{"type":47,"value":532},{"type":42,"tag":43,"props":1543,"children":1544},{},[1545,1547,1554],{"type":47,"value":1546},"Copilot クレジットは、エージェントの応答や操作の量を測る単位で、1回の応答で消費される量はタスクの複雑さによって変わります。支払い方法には、月ごとの容量を前払いで購入する方法と、Azure のサブスクリプションを通じて実際に使った分だけ支払う従量課金があります。Microsoft の日本向け価格ページでは、前払いのパックが月額29,985円で25,000クレジットと表示されています（出典：",{"type":42,"tag":50,"props":1548,"children":1551},{"href":1549,"rel":1550},"https:\u002F\u002Fwww.microsoft.com\u002Fja-jp\u002Fcopilot\u002Fpricing\u002Fcopilot-studio",[54],[1552],{"type":47,"value":1553},"Microsoft「Copilot Studio の価格」",{"type":47,"value":1555},"、2026年9月時点）。",{"type":42,"tag":43,"props":1557,"children":1558},{},[1559,1561,1568,1569,1574],{"type":47,"value":1560},"ライセンスを持たない社員にも社内データを使うエージェントを配る場合、従量課金は既定で無効になっており、管理者が請求の設定をして初めて有効になります。予算の上限と通知も設定できます（出典：",{"type":42,"tag":50,"props":1562,"children":1565},{"href":1563,"rel":1564},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fcopilot\u002Fplan\u002Fpay-as-you-go-overview",[54],[1566],{"type":47,"value":1567},"Microsoft Learn「Microsoft Copilot Pay-as-You-Go Service Overview」",{"type":47,"value":59},{"type":42,"tag":66,"props":1570,"children":1571},{},[1572],{"type":47,"value":1573},"「ライセンスのない人にも配ったら、想定外の請求が来た」を防ぐため、予算上限を必ず設定",{"type":47,"value":1575},"します。",{"type":42,"tag":43,"props":1577,"children":1578},{},[1579],{"type":47,"value":1580},"エージェントに限らず、フローの中でAIに処理させる場合も、使った量に応じた費用を見込んでおく必要があります。",{"type":42,"tag":92,"props":1582,"children":1583},{},[1584,1591],{"type":42,"tag":43,"props":1585,"children":1586},{},[1587],{"type":42,"tag":66,"props":1588,"children":1589},{},[1590],{"type":47,"value":644},{"type":42,"tag":43,"props":1592,"children":1593},{},[1594],{"type":47,"value":1595},"Power Automate のフローの中で Copilot の処理を回したところ、AIのクレジットを大量に消費したことがありました。1件ずつは小さくても、毎日・毎件の処理にAIを挟むと積み上がります。根本的な回避策はまだ検討しているところですが、量の多い処理では、件数とクレジットの消費量から費用を先に見積もり、AIに任せる範囲を決めるようにしています。前述のとおり、手順で組める部分はAIを使わずに組めるので、量を見て使い分けます。",{"type":42,"tag":43,"props":1597,"children":1598},{},[1599],{"type":47,"value":1600},"料金体系・製品名・機能は変わりやすい領域です。導入や予算の判断の前には、最新の公式情報を確認してください。",{"type":42,"tag":185,"props":1602,"children":1604},{"id":1603},"シリーズ全体の振り返り",[1605],{"type":47,"value":1603},{"type":42,"tag":43,"props":1607,"children":1608},{},[1609],{"type":47,"value":1610},"最後に、全8回と特別編・番外編で扱ってきた内容を、第1回で示したロードマップのフェーズに沿って振り返ります。",{"type":42,"tag":426,"props":1612,"children":1613},{},[1614,1615,1620,1621],{"type":47,"value":430},{"type":42,"tag":432,"props":1616,"children":1619},{"media":434,"srcSet":1617,"width":436,"height":1618},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Fseries-map-sp.svg",808,[],{"type":47,"value":430},{"type":42,"tag":441,"props":1622,"children":1626},{"src":1623,"alt":1624,"width":445,"height":1625,"loading":447},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-agent-katsuyou\u002Fseries-map.svg","シリーズ全体の地図：フェーズ0現状把握、フェーズ1データガバナンス整備、フェーズ2ルール整備、フェーズ3パイロット、フェーズ4全社展開と定着化、その先のエージェント活用",422,[],{"type":42,"tag":43,"props":1628,"children":1629},{},[1630],{"type":42,"tag":66,"props":1631,"children":1632},{},[1633],{"type":47,"value":1634},"全体像",{"type":42,"tag":104,"props":1636,"children":1637},{},[1638],{"type":42,"tag":108,"props":1639,"children":1640},{},[1641,1646],{"type":42,"tag":50,"props":1642,"children":1643},{"href":85},[1644],{"type":47,"value":1645},"第1回：非IT企業のMicrosoft 365 Copilot導入ロードマップ｜ライセンスを配る前に決めるべきこと",{"type":47,"value":1647}," ―― 失敗パターン、Copilot の種類、二層構成、5フェーズのロードマップ",{"type":42,"tag":43,"props":1649,"children":1650},{},[1651],{"type":42,"tag":66,"props":1652,"children":1653},{},[1654],{"type":47,"value":1655},"フェーズ0：現状把握",{"type":42,"tag":104,"props":1657,"children":1658},{},[1659,1669,1680],{"type":42,"tag":108,"props":1660,"children":1661},{},[1662,1667],{"type":42,"tag":50,"props":1663,"children":1664},{"href":147},[1665],{"type":47,"value":1666},"第2回前編：Microsoft 365 Copilotは社内のメールやチャットを「学習」するのか",{"type":47,"value":1668}," ―― 学習の3層、データの置き場所、Box・SharePoint・OneDrive の判断",{"type":42,"tag":108,"props":1670,"children":1671},{},[1672,1678],{"type":42,"tag":50,"props":1673,"children":1675},{"href":1674},"\u002Farticles\u002Fcopilot-mail-chat-ikou-checklist\u002F",[1676],{"type":47,"value":1677},"第2回後編：Exchange Online移行の注意点とLINE WORKSからの移行",{"type":47,"value":1679}," ―― メールとチャットの移行、導入前チェックリスト",{"type":42,"tag":108,"props":1681,"children":1682},{},[1683,1689],{"type":42,"tag":50,"props":1684,"children":1686},{"href":1685},"\u002Farticles\u002Fm365-copilot-iranai-google-hikaku\u002F",[1687],{"type":47,"value":1688},"番外編：Microsoft 365 Copilotはいらない？",{"type":47,"value":1690}," ―― 「Googleより高い」への答え方と判断基準",{"type":42,"tag":43,"props":1692,"children":1693},{},[1694],{"type":42,"tag":66,"props":1695,"children":1696},{},[1697],{"type":47,"value":1698},"フェーズ1：データガバナンス整備",{"type":42,"tag":104,"props":1700,"children":1701},{},[1702,1713,1724],{"type":42,"tag":108,"props":1703,"children":1704},{},[1705,1711],{"type":42,"tag":50,"props":1706,"children":1708},{"href":1707},"\u002Farticles\u002Fcopilot-joho-rouei-sharepoint-kengen\u002F",[1709],{"type":47,"value":1710},"第3回：Microsoft 365 Copilotの情報漏洩対策",{"type":47,"value":1712}," ―― SharePoint・OneDrive・Teams の権限の棚卸しと是正",{"type":42,"tag":108,"props":1714,"children":1715},{},[1716,1722],{"type":42,"tag":50,"props":1717,"children":1719},{"href":1718},"\u002Farticles\u002Fcopilot-security-settei-chusho\u002F",[1720],{"type":47,"value":1721},"第4回前編：Microsoft 365 Copilotのセキュリティ設定",{"type":47,"value":1723}," ―― 中小企業に秘密度ラベルとDLPは必要かの判定",{"type":42,"tag":108,"props":1725,"children":1726},{},[1727,1733],{"type":42,"tag":50,"props":1728,"children":1730},{"href":1729},"\u002Farticles\u002Fcopilot-sensitivity-label-dlp\u002F",[1731],{"type":47,"value":1732},"第4回後編：秘密度ラベルとDLP",{"type":47,"value":1734}," ―― 「警告」から始める段階設計とライセンス",{"type":42,"tag":43,"props":1736,"children":1737},{},[1738],{"type":42,"tag":66,"props":1739,"children":1740},{},[1741],{"type":47,"value":1742},"フェーズ2：ルール整備",{"type":42,"tag":104,"props":1744,"children":1745},{},[1746,1757,1768],{"type":42,"tag":108,"props":1747,"children":1748},{},[1749,1755],{"type":42,"tag":50,"props":1750,"children":1752},{"href":1751},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample\u002F",[1753],{"type":47,"value":1754},"第5回前編：生成AIの社内ルールの作り方（サンプル条文付き）",{"type":47,"value":1756}," ―― 利用ガイドラインの作り方",{"type":42,"tag":108,"props":1758,"children":1759},{},[1760,1766],{"type":42,"tag":50,"props":1761,"children":1763},{"href":1762},"\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002F",[1764],{"type":47,"value":1765},"第5回後編：システム開発を外注するときのAI利用ルール",{"type":47,"value":1767}," ―― 開発会社に求める5つの約束",{"type":42,"tag":108,"props":1769,"children":1770},{},[1771,1777],{"type":42,"tag":50,"props":1772,"children":1774},{"href":1773},"\u002Farticles\u002Fcopilot-shanai-kitei-edp\u002F",[1775],{"type":47,"value":1776},"特別編：その社内規則、Microsoft 365 Copilotを禁止していますか？",{"type":47,"value":1778}," ―― 規程の禁止文言と EDP の読み合わせ",{"type":42,"tag":43,"props":1780,"children":1781},{},[1782],{"type":42,"tag":66,"props":1783,"children":1784},{},[1785],{"type":47,"value":1786},"フェーズ3：パイロット",{"type":42,"tag":104,"props":1788,"children":1789},{},[1790,1801],{"type":42,"tag":108,"props":1791,"children":1792},{},[1793,1799],{"type":42,"tag":50,"props":1794,"children":1796},{"href":1795},"\u002Farticles\u002Fcopilot-pilot-kouka-sokutei\u002F",[1797],{"type":47,"value":1798},"第6回：Microsoft 365 Copilotのパイロット導入と効果測定",{"type":47,"value":1800}," ―― 指標と Go\u002FNo-Go 判断",{"type":42,"tag":108,"props":1802,"children":1803},{},[1804,1810],{"type":42,"tag":50,"props":1805,"children":1807},{"href":1806},"\u002Farticles\u002Fcopilot-kaitou-troubleshoot\u002F",[1808],{"type":47,"value":1809},"番外編：Microsoft 365 Copilotが使えない・期待した回答を返さない原因と対処",{"type":47,"value":1811}," ―― 切り分けフローチャート",{"type":42,"tag":43,"props":1813,"children":1814},{},[1815],{"type":42,"tag":66,"props":1816,"children":1817},{},[1818],{"type":47,"value":1819},"フェーズ4：全社展開と定着化、その先へ",{"type":42,"tag":104,"props":1821,"children":1822},{},[1823,1834,1844,1855],{"type":42,"tag":108,"props":1824,"children":1825},{},[1826,1832],{"type":42,"tag":50,"props":1827,"children":1829},{"href":1828},"\u002Farticles\u002Fcopilot-zensha-tenkai-teichaku\u002F",[1830],{"type":47,"value":1831},"第7回前編：Microsoft 365 Copilotの定着化",{"type":47,"value":1833}," ―― チャンピオン制度と「使われない」を防ぐ仕組み",{"type":42,"tag":108,"props":1835,"children":1836},{},[1837,1842],{"type":42,"tag":50,"props":1838,"children":1839},{"href":1009},[1840],{"type":47,"value":1841},"第7回後編：Microsoft 365 Copilotの社内研修の進め方",{"type":47,"value":1843}," ―― 段階別研修と復習の仕組み",{"type":42,"tag":108,"props":1845,"children":1846},{},[1847,1853],{"type":42,"tag":50,"props":1848,"children":1850},{"href":1849},"\u002Farticles\u002Fcopilot-hitori-joshisu\u002F",[1851],{"type":47,"value":1852},"番外編：情シスがいない会社のMicrosoft 365 Copilot導入",{"type":47,"value":1854}," ―― 一人情シス・兼務でも回る体制",{"type":42,"tag":108,"props":1856,"children":1857},{},[1858],{"type":47,"value":1859},"第8回：本記事（エージェントの作り方と活用）",{"type":42,"tag":43,"props":1861,"children":1862},{},[1863,1865,1871,1873,1879],{"type":47,"value":1864},"このほか、シリーズと並行して、AI利用のルールづくりの実務として",{"type":42,"tag":50,"props":1866,"children":1868},{"href":1867},"\u002Farticles\u002Fclaude-code-deny-settei\u002F",[1869],{"type":47,"value":1870},"Claude Codeの秘密情報対策",{"type":47,"value":1872},"と",{"type":42,"tag":50,"props":1874,"children":1876},{"href":1875},"\u002Farticles\u002Fclaude-code-hooks-guardrails\u002F",[1877],{"type":47,"value":1878},"hooksの設定例",{"type":47,"value":1880},"も公開しています（開発に生成AIを使う場合の話です）。",{"type":42,"tag":43,"props":1882,"children":1883},{},[1884,1886,1891],{"type":47,"value":1885},"シリーズを通して伝えてきたことは、1つに集約できます。",{"type":42,"tag":66,"props":1887,"children":1888},{},[1889],{"type":47,"value":1890},"Copilot 導入の成否は、AIの性能ではなく、社内の情報の扱い方を整えられるかで決まる",{"type":47,"value":1892},"ということです。データを置く場所、見せてよい範囲、使ってよいルール、使う人を支える仕組み——これらはエージェントを作る段階でも、そのまま土台になります。",{"type":42,"tag":185,"props":1894,"children":1896},{"id":1895},"ksrogers-の支援",[1897],{"type":47,"value":1898},"K.S.Rogers の支援",{"type":42,"tag":43,"props":1900,"children":1901},{},[1902],{"type":47,"value":1903},"K.S.Rogers では、Microsoft 365 Copilot の導入ロードマップの策定から、データの置き場所と権限の整備、ガイドライン策定、定着化、そしてエージェントづくりまでを一貫して伴走しています。エージェントについては、最初の1体を現場の方と一緒に作り、台帳と見直しのルールまで含めて社内に残る形で支援します。",{"type":42,"tag":43,"props":1905,"children":1906},{},[1907,1909,1913,1915,1922],{"type":47,"value":1908},"Copilot のエージェントの範囲を超えて、基幹システムとつないだ定型業務の自動化が必要な場合は、",{"type":42,"tag":50,"props":1910,"children":1911},{"href":983},[1912],{"type":47,"value":986},{"type":47,"value":1914},"でシステム環境調査（20万円〜）から構築・運用まで対応します。また、「どの業務をAIに任せるか」から整理したい場合は、",{"type":42,"tag":50,"props":1916,"children":1919},{"href":1917,"rel":1918},"https:\u002F\u002Fks-rogers.co.jp\u002Frd\u002F",[54],[1920],{"type":47,"value":1921},"要件定義支援",{"type":47,"value":1923},"の相談・壁打ち（月10万円・税別）から始めることもできます。",{"type":42,"tag":43,"props":1925,"children":1926},{},[1927,1929,1935],{"type":47,"value":1928},"M365 の導入・ファイル移行から Power Platform・Copilot の活用までの支援の範囲と進め方は、",{"type":42,"tag":50,"props":1930,"children":1932},{"href":1931},"\u002Fbusiness\u002Fm365\u002F",[1933],{"type":47,"value":1934},"Microsoft 365 導入・活用支援",{"type":47,"value":1936},"のページにまとめています。",{"type":42,"tag":43,"props":1938,"children":1939},{},[1940,1942,1948],{"type":47,"value":1941},"シリーズのどの段階からでも、",{"type":42,"tag":50,"props":1943,"children":1945},{"href":1944},"\u002Fcontact\u002F",[1946],{"type":47,"value":1947},"お問い合わせ",{"type":47,"value":1949},"よりお気軽にご相談ください。",{"type":42,"tag":185,"props":1951,"children":1953},{"id":1952},"まとめ",[1954],{"type":47,"value":1952},{"type":42,"tag":104,"props":1956,"children":1957},{},[1958,1970,1982,1994,1999],{"type":42,"tag":108,"props":1959,"children":1960},{},[1961,1963,1968],{"type":47,"value":1962},"エージェントは、指示・知識・操作を設定した業務専用の Copilot です。",{"type":42,"tag":66,"props":1964,"children":1965},{},[1966],{"type":47,"value":1967},"エージェントビルダーで小さく始め",{"type":47,"value":1969},"、外部連携が必要になったら Copilot Studio、案件ごとの資料の束は Copilot Notebooks を使います",{"type":42,"tag":108,"props":1971,"children":1972},{},[1973,1975,1980],{"type":47,"value":1974},"決まった手順を自動で流すだけなら、",{"type":42,"tag":66,"props":1976,"children":1977},{},[1978],{"type":47,"value":1979},"Copilot Studio の前に Power Automate",{"type":47,"value":1981},"で足ります。判断が要るところだけ、フローの中でAIに任せます",{"type":42,"tag":108,"props":1983,"children":1984},{},[1985,1987,1992],{"type":47,"value":1986},"ノートブックとエージェントは「学習の3層」の③整理・蓄積を形にする道具です。",{"type":42,"tag":66,"props":1988,"children":1989},{},[1990],{"type":47,"value":1991},"判断の理由を書いて置く習慣",{"type":47,"value":1993},"が前提になります",{"type":42,"tag":108,"props":1995,"children":1996},{},[1997],{"type":47,"value":1998},"野良エージェントを防ぐため、台帳・所有者2名・半年ごとの見直し・全社公開の申請制を、作り始める前に決めます",{"type":42,"tag":108,"props":2000,"children":2001},{},[2002,2004,2009],{"type":47,"value":2003},"料金は使う人のライセンスと参照するデータで変わります。",{"type":42,"tag":66,"props":2005,"children":2006},{},[2007],{"type":47,"value":2008},"従量課金を使う場合は予算上限を設定",{"type":47,"value":2010},"し、最新の公式情報を確認します",{"type":42,"tag":43,"props":2012,"children":2013},{},[2014],{"type":47,"value":2015},"本シリーズは今回で完結です。最後までお読みいただき、ありがとうございました。",{"title":7,"searchDepth":2017,"depth":2017,"links":2018},2,[2019,2020,2021,2028,2031,2032,2033,2034,2037,2038,2039,2040],{"id":187,"depth":2017,"text":190},{"id":258,"depth":2017,"text":261},{"id":317,"depth":2017,"text":320,"children":2022},[2023,2025,2026,2027],{"id":452,"depth":2024,"text":455},3,{"id":497,"depth":2024,"text":500},{"id":672,"depth":2024,"text":675},{"id":690,"depth":2024,"text":693},{"id":723,"depth":2017,"text":726,"children":2029},[2030],{"id":796,"depth":2024,"text":796},{"id":842,"depth":2017,"text":845},{"id":991,"depth":2017,"text":994},{"id":1207,"depth":2017,"text":1210},{"id":1292,"depth":2017,"text":1295,"children":2035},[2036],{"id":1413,"depth":2024,"text":1416},{"id":1436,"depth":2017,"text":1439},{"id":1603,"depth":2017,"text":1603},{"id":1895,"depth":2017,"text":1898},{"id":1952,"depth":2017,"text":1952},"markdown","content:articles:copilot-agent-katsuyou.md","content","articles\u002Fcopilot-agent-katsuyou.md","articles\u002Fcopilot-agent-katsuyou","md",[2048,2053,2058,2062,2067,2072,2076,2081,2086,2091,2096,2101,2105,2110,2115,2119],{"_path":2049,"title":2050,"seriesNo":2051,"seriesLabel":2052},"\u002Farticles\u002Fm365-copilot-donyu-roadmap","Microsoft 365 Copilot 導入ロードマップ｜非IT企業がライセンス配布前に決めること",1,"第1回",{"_path":2054,"title":2055,"seriesNo":2056,"seriesLabel":2057},"\u002Farticles\u002Fcopilot-shanai-kitei-edp","Copilotのエンタープライズデータ保護（EDP）とは｜「外部AI禁止」の社内規程でも使えるかの判断手順",1.5,"特別編",{"_path":2059,"title":2060,"seriesNo":2017,"seriesLabel":2061},"\u002Farticles\u002Fcopilot-data-okiba-box-sharepoint","Copilotは社内データを学習する？｜参照できるデータの条件とSharePoint・OneDrive・Boxの使い分け","第2回（前編）",{"_path":2063,"title":2064,"seriesNo":2065,"seriesLabel":2066},"\u002Farticles\u002Fcopilot-mail-chat-ikou-checklist","Exchange Online移行の注意点とLINE WORKSからTeamsへの判断｜Microsoft 365 Copilot導入前チェックリスト",2.5,"第2回（後編）",{"_path":2068,"title":2069,"seriesNo":2070,"seriesLabel":2071},"\u002Farticles\u002Fm365-copilot-iranai-google-hikaku","Microsoft 365 Copilotはいらない？無料版との違い・料金と「Googleより高い」への答え方",2.8,"番外編",{"_path":2073,"title":2074,"seriesNo":2024,"seriesLabel":2075},"\u002Farticles\u002Fcopilot-joho-rouei-sharepoint-kengen","Microsoft 365 Copilotの情報漏洩対策｜SharePoint・OneDrive・Teamsの権限を棚卸しして是正する手順","第3回",{"_path":2077,"title":2078,"seriesNo":2079,"seriesLabel":2080},"\u002Farticles\u002Fcopilot-security-settei-chusho","Microsoft 365 Copilotのセキュリティ設定｜中小企業に秘密度ラベルとDLPは必要か",4,"第4回（前編）",{"_path":2082,"title":2083,"seriesNo":2084,"seriesLabel":2085},"\u002Farticles\u002Fcopilot-sensitivity-label-dlp","Microsoft 365 Copilotの秘密度ラベルとDLP｜「警告」から始める段階設計とライセンス要件",4.5,"第4回（後編）",{"_path":2087,"title":2088,"seriesNo":2089,"seriesLabel":2090},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample","生成AIの社内ルールの作り方【サンプル条文付き】｜Microsoft 365 Copilot時代の利用ガイドライン",5,"第5回（前編）",{"_path":2092,"title":2093,"seriesNo":2094,"seriesLabel":2095},"\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule","システム開発を外注するときのAI利用ルール｜開発会社に求める5つの約束と秘密情報の扱い",5.2,"第5回（後編）",{"_path":2097,"title":2098,"seriesNo":2099,"seriesLabel":2100},"\u002Farticles\u002Fcopilot-pilot-kouka-sokutei","Microsoft 365 Copilotのパイロット導入と効果測定｜導入効果を経営に説明する指標とGo\u002FNo-Go判断",6,"第6回",{"_path":2102,"title":2103,"seriesNo":2104,"seriesLabel":2071},"\u002Farticles\u002Fcopilot-kaitou-troubleshoot","Microsoft 365 Copilotが使えない・期待した回答を返さない原因と対処｜切り分けフローチャート",6.5,{"_path":2106,"title":2107,"seriesNo":2108,"seriesLabel":2109},"\u002Farticles\u002Fcopilot-zensha-tenkai-teichaku","Microsoft 365 Copilotの定着化｜全社展開で「使われない」を防ぐチャンピオン制度と事例共有",7,"第7回（前編）",{"_path":2111,"title":2112,"seriesNo":2113,"seriesLabel":2114},"\u002Farticles\u002Fcopilot-shanai-kenshu-susumekata","Microsoft 365 Copilotの社内研修の進め方｜リテラシーの差を越える段階別研修と復習の仕組み",7.2,"第7回（後編）",{"_path":2116,"title":2117,"seriesNo":2118,"seriesLabel":2071},"\u002Farticles\u002Fcopilot-hitori-joshisu","情シスがいない会社のMicrosoft 365 Copilot導入｜一人情シス・兼務でも回る体制と外部に任せる範囲",7.5,{"_path":4,"title":8,"seriesNo":13,"seriesLabel":14},1794237333319]