[{"data":1,"prerenderedAt":1581},["ShallowReactive",2],{"article-\u002Farticles\u002Fcopilot-hitori-joshisu":3,"article-series-m365-copilot":1514},{"_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":44,"_type":1508,"_id":1509,"_source":1510,"_file":1511,"_stem":1512,"_extension":1513},"\u002Farticles\u002Fcopilot-hitori-joshisu","articles",false,"","情シスがいない会社のMicrosoft 365 Copilot導入｜一人情シス・兼務でも回る体制と外部に任せる範囲","情シスがいない、または一人情シスが兼務している会社が、Microsoft 365 Copilotを導入するための体制を解説します。「情シスに丸投げしない」役割分担、社内に残す判断と外部に任せてよい作業、最低限の運用まで。","2026-11-02","Microsoft 365 活用","m365-copilot",7.5,"番外編","K.S.ロジャース株式会社","\u002Fimg\u002Fcontents\u002Fnews\u002Fthumb128.jpg",[18,19,20,21],"Microsoft 365 Copilot","一人情シス","中小企業","AIガバナンス",[23,26,29,32,35,38,41],{"q":24,"a":25},"情報システム担当がいない会社でも、Microsoft 365 Copilotは導入できますか？","導入できます。ただし、設定作業を外部に任せても、誰に配るか・何を使ってよいかといった判断は社内に残す必要があります。経営側の推進責任者、現場の代表、外部パートナーで役割を分け、アカウント管理と問い合わせ窓口だけは社内に担当者を決めておきます。",{"q":27,"a":28},"一人情シスの場合、Copilot導入で何を外部に任せるべきですか？","権限の棚卸しの実作業、セキュリティ設定、研修資料の作成、移行作業など、専門知識が必要で一度きりの作業は外部に任せてかまいません。一方、利用ルールの決定、ライセンスを配る相手の決定、機密情報の区分の決定は社内で行います。",{"q":30,"a":31},"メールと予定表を Outlook に移すときは、何から始めればよいですか？","今の DNS の棚卸しから始めます。移行には MX レコードの書き換えが必要ですが、MX だけでなく CNAME やサブドメインも含めて、各レコードが何に使われているかを1つずつ確かめます。情シス部門がある会社でも用途の分からないレコードが見つかることがあるため、移行の期間にこの確認の時間を含めておきます。",{"q":33,"a":34},"社員50人の会社だと、Copilot導入にどのくらいの期間がかかりますか？","すでに Microsoft 365 を使っている社員50人前後の会社で、現状把握から全社展開まで3〜4か月が目安です。内訳は現状把握2〜3週間、データの置き場所と権限の整備4〜6週間、利用ルールの整備2〜3週間（並行可）、パイロット4週間、全社展開と定着4〜6週間です。共有フォルダの権限が長年整理されていない場合は、権限の整備だけで2〜3か月かかることもあります。",{"q":36,"a":37},"外部パートナーとは、どのくらい面着で打ち合わせが必要ですか？","社員50人前後の会社で、導入完了までに合計5〜7回（多くは半日）が目安です。キックオフ、権限の是正方針の相談、利用ルールの読み合わせ、最初の研修、部門ごとの研修が面着に向く場面です。進捗確認や設定作業はオンラインで進められます。",{"q":39,"a":40},"管理者アカウントを外部パートナーに渡してもよいですか？","社内の管理者アカウントを共有するのは避けます。Microsoft はグローバル管理者を最小限にし、作業に必要な最小限の権限の管理者ロールを割り当てることを推奨しています。パートナーには専用のアカウントや代理管理の仕組みで必要な権限だけを付与し、作業が終わったら見直します。",{"q":42,"a":43},"中小企業向けのCopilotのライセンスはありますか？","300ユーザーまでの組織向けに「Copilot Business」が提供されています。Microsoft の日本向け価格ページでは、年払いで1ユーザーあたり月額3,148円相当と表示されています（2026年9月時点）。前提となるプランや最新の価格は、購入前に公式サイトで確認してください。",{"type":45,"children":46,"toc":1490},"root",[47,66,71,76,95,146,153,158,245,257,263,268,367,390,402,414,420,432,567,583,588,593,617,623,635,813,832,837,870,885,897,903,908,915,920,943,957,963,968,981,986,1019,1025,1030,1110,1126,1147,1162,1167,1172,1244,1249,1254,1259,1299,1313,1318,1323,1376,1382,1387,1400,1413,1426,1431,1485],{"type":48,"tag":49,"props":50,"children":51},"element","p",{},[52,55,64],{"type":53,"value":54},"text","※ Microsoft 365 Copilot は、2026年8月から「Microsoft Copilot」に名称が変わりました（Copilot Chat は「Microsoft Copilot Chat」）。移行期間中は旧名称も併用されているため、本記事では広く使われている「Microsoft 365 Copilot」の表記で統一しています（出典：",{"type":48,"tag":56,"props":57,"children":61},"a",{"href":58,"rel":59},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fcopilot\u002Fmicrosoft-365\u002Fmicrosoft-365-copilot-privacy",[60],"nofollow",[62],{"type":53,"value":63},"Microsoft Learn「Microsoft Copilot のデータ、プライバシー、セキュリティ」",{"type":53,"value":65},"）。",{"type":48,"tag":49,"props":67,"children":68},{},[69],{"type":53,"value":70},"「うちには情報システム部門がない。IT担当は1人で、基幹システムの保守とパソコンの面倒で手一杯。Copilot を入れたいが、誰がやるのか」——非IT企業で Microsoft 365 Copilot の相談を受けると、かなりの確率で最初にこの壁に当たります。",{"type":48,"tag":49,"props":72,"children":73},{},[74],{"type":53,"value":75},"いわゆる「一人情シス」は、社内のIT全般を1人で担う状態を指します。専任ではなく、総務や経理と兼務しているケースも珍しくありません。こうした会社で Copilot 導入を「情シスの仕事」として割り振ると、ほぼ確実に後回しになり、担当者が退職した瞬間にすべてが止まります。",{"type":48,"tag":49,"props":77,"children":78},{},[79,85,87,93],{"type":48,"tag":56,"props":80,"children":82},{"href":81},"\u002Farticles\u002Fm365-copilot-donyu-roadmap\u002F",[83],{"type":53,"value":84},"第1回：非IT企業のMicrosoft 365 Copilot導入ロードマップ",{"type":53,"value":86},"では、体制づくりの要点として「情シスに丸投げしない」ことを挙げました。本記事はその深掘りとして、",{"type":48,"tag":88,"props":89,"children":90},"strong",{},[91],{"type":53,"value":92},"専任の情報システム担当がいない会社が、どう役割を分け、何を外部に任せ、何を社内に残すか",{"type":53,"value":94},"を具体的に整理します。",{"type":48,"tag":96,"props":97,"children":98},"blockquote",{},[99,107],{"type":48,"tag":49,"props":100,"children":101},{},[102],{"type":48,"tag":88,"props":103,"children":104},{},[105],{"type":53,"value":106},"この記事の要点",{"type":48,"tag":108,"props":109,"children":110},"ul",{},[111,124,129,134],{"type":48,"tag":112,"props":113,"children":114},"li",{},[115,117,122],{"type":53,"value":116},"情シス不在の会社の Copilot 導入は、",{"type":48,"tag":88,"props":118,"children":119},{},[120],{"type":53,"value":121},"判断は社内、作業は外部に任せてよい",{"type":53,"value":123},"と切り分けると進みます。経営・現場・情シス・外部パートナーの4者で役割を分けます",{"type":48,"tag":112,"props":125,"children":126},{},[127],{"type":53,"value":128},"外部に任せても社内に残すべきなのは、利用ルール、ライセンスを配る相手、機密情報の区分、パートナーに渡す権限の4つの判断です",{"type":48,"tag":112,"props":130,"children":131},{},[132],{"type":53,"value":133},"運用で最低限決めるのは、アカウントの入退社手続き、管理者権限の持ち方、問い合わせ窓口の3つです。月1時間の定期チェックで回せる形にします",{"type":48,"tag":112,"props":135,"children":136},{},[137,139,144],{"type":53,"value":138},"当社の支援でも、情シスがいない会社ではシステム構成や DNS の使い方を把握している人がいないことが多く、",{"type":48,"tag":88,"props":140,"children":141},{},[142],{"type":53,"value":143},"外部が先に調べて判断の材料をそろえる",{"type":53,"value":145},"ところから始めています",{"type":48,"tag":147,"props":148,"children":150},"h2",{"id":149},"一人情シス情シス不在の会社でcopilot導入が止まる理由",[151],{"type":53,"value":152},"一人情シス・情シス不在の会社でCopilot導入が止まる理由",{"type":48,"tag":49,"props":154,"children":155},{},[156],{"type":53,"value":157},"情シスが1人しかいない、あるいはいない会社で Copilot 導入が止まるパターンは、おおむね3つです。",{"type":48,"tag":159,"props":160,"children":161},"table",{},[162,186],{"type":48,"tag":163,"props":164,"children":165},"thead",{},[166],{"type":48,"tag":167,"props":168,"children":169},"tr",{},[170,176,181],{"type":48,"tag":171,"props":172,"children":173},"th",{},[174],{"type":53,"value":175},"パターン",{"type":48,"tag":171,"props":177,"children":178},{},[179],{"type":53,"value":180},"起きていること",{"type":48,"tag":171,"props":182,"children":183},{},[184],{"type":53,"value":185},"結果",{"type":48,"tag":187,"props":188,"children":189},"tbody",{},[190,209,227],{"type":48,"tag":167,"props":191,"children":192},{},[193,199,204],{"type":48,"tag":194,"props":195,"children":196},"td",{},[197],{"type":53,"value":198},"丸投げ",{"type":48,"tag":194,"props":200,"children":201},{},[202],{"type":53,"value":203},"経営が「ITのことだから」と一人情シスに一任する",{"type":48,"tag":194,"props":205,"children":206},{},[207],{"type":53,"value":208},"ルールや配布先まで1人で決めることになり、判断に責任を持てず止まる",{"type":48,"tag":167,"props":210,"children":211},{},[212,217,222],{"type":48,"tag":194,"props":213,"children":214},{},[215],{"type":53,"value":216},"兼務で後回し",{"type":48,"tag":194,"props":218,"children":219},{},[220],{"type":53,"value":221},"基幹システムの保守や日々の問い合わせが優先される",{"type":48,"tag":194,"props":223,"children":224},{},[225],{"type":53,"value":226},"権限の棚卸しなど時間のかかる準備が終わらない",{"type":48,"tag":167,"props":228,"children":229},{},[230,235,240],{"type":48,"tag":194,"props":231,"children":232},{},[233],{"type":53,"value":234},"属人化",{"type":48,"tag":194,"props":236,"children":237},{},[238],{"type":53,"value":239},"1人で設定を進め、記録が残らない",{"type":48,"tag":194,"props":241,"children":242},{},[243],{"type":53,"value":244},"担当者の異動・退職で、誰も設定の意図が分からなくなる",{"type":48,"tag":49,"props":246,"children":247},{},[248,250,255],{"type":53,"value":249},"共通しているのは、",{"type":48,"tag":88,"props":251,"children":252},{},[253],{"type":53,"value":254},"Copilot 導入を「ITツールの設定作業」と捉えている",{"type":53,"value":256},"ことです。第1回で述べたとおり、Copilot 導入の本丸は、データの置き場所・権限・利用ルールという社内の情報の扱い方を決めることです。これは本来、情シス1人で決められるものではありません。",{"type":48,"tag":147,"props":258,"children":260},{"id":259},"情シスに丸投げしない体制-4者の役割分担",[261],{"type":53,"value":262},"「情シスに丸投げしない」体制 ― 4者の役割分担",{"type":48,"tag":49,"props":264,"children":265},{},[266],{"type":53,"value":267},"情シス不在・一人情シスの会社では、次の4者で役割を分けます。",{"type":48,"tag":159,"props":269,"children":270},{},[271,292],{"type":48,"tag":163,"props":272,"children":273},{},[274],{"type":48,"tag":167,"props":275,"children":276},{},[277,282,287],{"type":48,"tag":171,"props":278,"children":279},{},[280],{"type":53,"value":281},"役割",{"type":48,"tag":171,"props":283,"children":284},{},[285],{"type":53,"value":286},"誰が担うか",{"type":48,"tag":171,"props":288,"children":289},{},[290],{"type":53,"value":291},"主な責任",{"type":48,"tag":187,"props":293,"children":294},{},[295,313,331,349],{"type":48,"tag":167,"props":296,"children":297},{},[298,303,308],{"type":48,"tag":194,"props":299,"children":300},{},[301],{"type":53,"value":302},"推進責任者",{"type":48,"tag":194,"props":304,"children":305},{},[306],{"type":53,"value":307},"役員・経営企画・管理部門長など、経営に近い人",{"type":48,"tag":194,"props":309,"children":310},{},[311],{"type":53,"value":312},"目的と予算を決める。社内ルールを承認する。部門間の調整をする",{"type":48,"tag":167,"props":314,"children":315},{},[316,321,326],{"type":48,"tag":194,"props":317,"children":318},{},[319],{"type":53,"value":320},"情シス担当（兼務可）",{"type":48,"tag":194,"props":322,"children":323},{},[324],{"type":53,"value":325},"一人情シス、総務・経理の兼務担当",{"type":48,"tag":194,"props":327,"children":328},{},[329],{"type":53,"value":330},"アカウントとライセンスの日常管理、パートナーとの窓口、設定の記録の保管",{"type":48,"tag":167,"props":332,"children":333},{},[334,339,344],{"type":48,"tag":194,"props":335,"children":336},{},[337],{"type":53,"value":338},"現場代表",{"type":48,"tag":194,"props":340,"children":341},{},[342],{"type":53,"value":343},"各部門で業務に詳しい人（チャンピオン候補）",{"type":48,"tag":194,"props":345,"children":346},{},[347],{"type":53,"value":348},"使い道を出す、部門内の相談に乗る、ルールの使いにくさを伝える",{"type":48,"tag":167,"props":350,"children":351},{},[352,357,362],{"type":48,"tag":194,"props":353,"children":354},{},[355],{"type":53,"value":356},"外部パートナー",{"type":48,"tag":194,"props":358,"children":359},{},[360],{"type":53,"value":361},"Microsoft 365 の導入支援会社など",{"type":48,"tag":194,"props":363,"children":364},{},[365],{"type":53,"value":366},"専門知識が要る設定・棚卸しの実作業、ルールのたたき台、研修の実施",{"type":48,"tag":368,"props":369,"children":370},"picture",{},[371,373,381,382],{"type":53,"value":372},"\n  ",{"type":48,"tag":374,"props":375,"children":380},"source",{"media":376,"srcSet":377,"width":378,"height":379},"(max-width: 768px)","\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-hitori-joshisu\u002Ftaisei-4sha-sp.svg",420,590,[],{"type":53,"value":372},{"type":48,"tag":383,"props":384,"children":389},"img",{"src":385,"alt":386,"width":387,"height":378,"loading":388},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-hitori-joshisu\u002Ftaisei-4sha.svg","情シスに丸投げしない体制：推進責任者が目的・予算・ルールを決め、情シス担当が日常管理と窓口、現場代表が使い道と部門の相談、外部パートナーが専門作業とたたき台を担う",800,"lazy",[],{"type":48,"tag":49,"props":391,"children":392},{},[393,395,400],{"type":53,"value":394},"ポイントは、",{"type":48,"tag":88,"props":396,"children":397},{},[398],{"type":53,"value":399},"推進責任者を情シス担当とは別の人にする",{"type":53,"value":401},"ことです。情シス担当が推進責任者を兼ねると、「誰に配るか」「どこまで使ってよいか」といった経営判断まで1人で抱えることになります。推進責任者は IT に詳しくなくてかまいません。必要なのは、決める権限と、部門をまたいで話を通せる立場です。",{"type":48,"tag":49,"props":403,"children":404},{},[405,407,412],{"type":53,"value":406},"また、一人情シスの負担を増やさないために、",{"type":48,"tag":88,"props":408,"children":409},{},[410],{"type":53,"value":411},"情シス担当の役割を「日常管理と窓口」に限定する",{"type":53,"value":413},"ことも大切です。権限の棚卸しやセキュリティ設定の設計のような、一度きりで専門知識が要る作業は、外部パートナーに任せる前提で計画します。",{"type":48,"tag":147,"props":415,"children":417},{"id":416},"社内に残す判断と外部に任せてよい作業",[418],{"type":53,"value":419},"社内に残す判断と、外部に任せてよい作業",{"type":48,"tag":49,"props":421,"children":422},{},[423,425,430],{"type":53,"value":424},"外部パートナーに頼むとき、最も多い失敗は「全部お任せします」です。任せ方の原則は、",{"type":48,"tag":88,"props":426,"children":427},{},[428],{"type":53,"value":429},"判断は社内に残し、作業は任せてよい",{"type":53,"value":431},"です。",{"type":48,"tag":159,"props":433,"children":434},{},[435,456],{"type":48,"tag":163,"props":436,"children":437},{},[438],{"type":48,"tag":167,"props":439,"children":440},{},[441,446,451],{"type":48,"tag":171,"props":442,"children":443},{},[444],{"type":53,"value":445},"領域",{"type":48,"tag":171,"props":447,"children":448},{},[449],{"type":53,"value":450},"社内に残す判断",{"type":48,"tag":171,"props":452,"children":453},{},[454],{"type":53,"value":455},"外部に任せてよい作業",{"type":48,"tag":187,"props":457,"children":458},{},[459,477,495,513,531,549],{"type":48,"tag":167,"props":460,"children":461},{},[462,467,472],{"type":48,"tag":194,"props":463,"children":464},{},[465],{"type":53,"value":466},"利用ルール",{"type":48,"tag":194,"props":468,"children":469},{},[470],{"type":53,"value":471},"何に使ってよいか、何を入力してはいけないかの最終決定",{"type":48,"tag":194,"props":473,"children":474},{},[475],{"type":53,"value":476},"ガイドラインのたたき台作成、他社の一般的な例の紹介",{"type":48,"tag":167,"props":478,"children":479},{},[480,485,490],{"type":48,"tag":194,"props":481,"children":482},{},[483],{"type":53,"value":484},"ライセンス",{"type":48,"tag":194,"props":486,"children":487},{},[488],{"type":53,"value":489},"誰に有償の席を配るか、使われない席をどうするか",{"type":48,"tag":194,"props":491,"children":492},{},[493],{"type":53,"value":494},"使用状況レポートの集計、配布計画の案",{"type":48,"tag":167,"props":496,"children":497},{},[498,503,508],{"type":48,"tag":194,"props":499,"children":500},{},[501],{"type":53,"value":502},"データと権限",{"type":48,"tag":194,"props":504,"children":505},{},[506],{"type":53,"value":507},"どの情報が機密か、どの部門に見せてよいか",{"type":48,"tag":194,"props":509,"children":510},{},[511],{"type":53,"value":512},"SharePoint の共有設定の棚卸し、是正作業、秘密度ラベルの設定",{"type":48,"tag":167,"props":514,"children":515},{},[516,521,526],{"type":48,"tag":194,"props":517,"children":518},{},[519],{"type":53,"value":520},"セキュリティ",{"type":48,"tag":194,"props":522,"children":523},{},[524],{"type":53,"value":525},"どこまでのリスクを許容するか",{"type":48,"tag":194,"props":527,"children":528},{},[529],{"type":53,"value":530},"多要素認証や条件付きアクセスの設定、監査ログの有効化",{"type":48,"tag":167,"props":532,"children":533},{},[534,539,544],{"type":48,"tag":194,"props":535,"children":536},{},[537],{"type":53,"value":538},"パートナーの権限",{"type":48,"tag":194,"props":540,"children":541},{},[542],{"type":53,"value":543},"どの権限を、いつまで渡すか",{"type":48,"tag":194,"props":545,"children":546},{},[547],{"type":53,"value":548},"作業に必要な権限の洗い出しと申請",{"type":48,"tag":167,"props":550,"children":551},{},[552,557,562],{"type":48,"tag":194,"props":553,"children":554},{},[555],{"type":53,"value":556},"研修・定着",{"type":48,"tag":194,"props":558,"children":559},{},[560],{"type":53,"value":561},"どの部門から始めるか、評価にどう反映するか",{"type":48,"tag":194,"props":563,"children":564},{},[565],{"type":53,"value":566},"研修資料の作成、ハンズオンの講師",{"type":48,"tag":368,"props":568,"children":569},{},[570,571,576,577],{"type":53,"value":372},{"type":48,"tag":374,"props":572,"children":575},{"media":376,"srcSet":573,"width":378,"height":574},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-hitori-joshisu\u002Fnokosu-makaseru-sp.svg",640,[],{"type":53,"value":372},{"type":48,"tag":383,"props":578,"children":582},{"src":579,"alt":580,"width":387,"height":581,"loading":388},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-hitori-joshisu\u002Fnokosu-makaseru.svg","社内に残す判断（利用ルール・配布先・機密区分・パートナーの権限）と、外部に任せてよい作業（権限の棚卸し・セキュリティ設定・ルールのたたき台・研修）の仕分け",360,[],{"type":48,"tag":49,"props":584,"children":585},{},[586],{"type":53,"value":587},"「機密かどうか」「誰に見せてよいか」は、業務を知っている社内の人にしか決められません。外部パートナーは、判断に必要な材料（今どこに何があり、誰が見られる状態か）を揃え、選択肢を示すところまでを担います。この線引きを最初に合意しておくと、「任せたはずなのに決まっていない」という状態を防げます。",{"type":48,"tag":49,"props":589,"children":590},{},[591],{"type":53,"value":592},"情シスがいない会社では、この材料をそろえる作業が、外部パートナーの最初の大きな仕事になります。",{"type":48,"tag":96,"props":594,"children":595},{},[596,604],{"type":48,"tag":49,"props":597,"children":598},{},[599],{"type":48,"tag":88,"props":600,"children":601},{},[602],{"type":53,"value":603},"K.S.Rogers の現場から",{"type":48,"tag":49,"props":605,"children":606},{},[607,609,615],{"type":53,"value":608},"情シスがいない会社では、社内にシステム構成を把握している人がいない、構成の資料もない、ということがよくあります。聞いていた構成と実際の動き方が違い、できると考えていたことが後からできないと分かった経験もあります（",{"type":48,"tag":56,"props":610,"children":612},{"href":611},"\u002Farticles\u002Fai-gyomu-jidoka-hajimekata\u002F",[613],{"type":53,"value":614},"AI業務自動化の始め方",{"type":53,"value":616},"で紹介）。今は、当社側で最初にシステム構成を調べ、その結果を材料に社内で判断していただく順番にしています。",{"type":48,"tag":147,"props":618,"children":620},{"id":619},"_50人規模の会社ならどのくらいの期間で入れられるか",[621],{"type":53,"value":622},"50人規模の会社なら、どのくらいの期間で入れられるか",{"type":48,"tag":49,"props":624,"children":625},{},[626,628,633],{"type":53,"value":627},"「うちの規模で、どのくらいかかるのか」は最初に聞かれる質問です。社員50人前後・拠点1〜2か所・すでに Microsoft 365 を使っている会社を想定した、当社の支援での目安が次の表です。",{"type":48,"tag":56,"props":629,"children":630},{"href":81},[631],{"type":53,"value":632},"第1回",{"type":53,"value":634},"の5フェーズに沿っています。",{"type":48,"tag":159,"props":636,"children":637},{},[638,664],{"type":48,"tag":163,"props":639,"children":640},{},[641],{"type":48,"tag":167,"props":642,"children":643},{},[644,649,654,659],{"type":48,"tag":171,"props":645,"children":646},{},[647],{"type":53,"value":648},"フェーズ",{"type":48,"tag":171,"props":650,"children":651},{},[652],{"type":53,"value":653},"期間の目安",{"type":48,"tag":171,"props":655,"children":656},{},[657],{"type":53,"value":658},"情シス担当（兼務）の負担",{"type":48,"tag":171,"props":660,"children":661},{},[662],{"type":53,"value":663},"外部パートナーの関わり方",{"type":48,"tag":187,"props":665,"children":666},{},[667,697,726,755,784],{"type":48,"tag":167,"props":668,"children":669},{},[670,675,680,685],{"type":48,"tag":194,"props":671,"children":672},{},[673],{"type":53,"value":674},"0. 現状把握",{"type":48,"tag":194,"props":676,"children":677},{},[678],{"type":53,"value":679},"2〜3週間",{"type":48,"tag":194,"props":681,"children":682},{},[683],{"type":53,"value":684},"週2〜3時間（資料出し、ヒアリングの同席）",{"type":48,"tag":194,"props":686,"children":687},{},[688,690,695],{"type":53,"value":689},"キックオフと現状共有で",{"type":48,"tag":88,"props":691,"children":692},{},[693],{"type":53,"value":694},"面着1回",{"type":53,"value":696},"（半日）。以降はオンライン",{"type":48,"tag":167,"props":698,"children":699},{},[700,705,710,715],{"type":48,"tag":194,"props":701,"children":702},{},[703],{"type":53,"value":704},"1. データの置き場所と権限の整備",{"type":48,"tag":194,"props":706,"children":707},{},[708],{"type":53,"value":709},"4〜6週間",{"type":48,"tag":194,"props":711,"children":712},{},[713],{"type":53,"value":714},"週2〜3時間（是正する範囲の確認）",{"type":48,"tag":194,"props":716,"children":717},{},[718,720,724],{"type":53,"value":719},"棚卸しの結果報告と是正方針の相談で",{"type":48,"tag":88,"props":721,"children":722},{},[723],{"type":53,"value":694},{"type":53,"value":725},"。実作業はパートナー側",{"type":48,"tag":167,"props":727,"children":728},{},[729,734,739,744],{"type":48,"tag":194,"props":730,"children":731},{},[732],{"type":53,"value":733},"2. 利用ルールの整備",{"type":48,"tag":194,"props":735,"children":736},{},[737],{"type":53,"value":738},"2〜3週間（フェーズ1と並行可）",{"type":48,"tag":194,"props":740,"children":741},{},[742],{"type":53,"value":743},"週1〜2時間",{"type":48,"tag":194,"props":745,"children":746},{},[747,749,753],{"type":53,"value":748},"たたき台の読み合わせで",{"type":48,"tag":88,"props":750,"children":751},{},[752],{"type":53,"value":694},{"type":53,"value":754},"（推進責任者が同席）",{"type":48,"tag":167,"props":756,"children":757},{},[758,763,768,773],{"type":48,"tag":194,"props":759,"children":760},{},[761],{"type":53,"value":762},"3. パイロット（1部門10名程度）",{"type":48,"tag":194,"props":764,"children":765},{},[766],{"type":53,"value":767},"4週間",{"type":48,"tag":194,"props":769,"children":770},{},[771],{"type":53,"value":772},"週2時間（参加者の声の集約）",{"type":48,"tag":194,"props":774,"children":775},{},[776,778,782],{"type":53,"value":777},"最初の研修で",{"type":48,"tag":88,"props":779,"children":780},{},[781],{"type":53,"value":694},{"type":53,"value":783},"。中間と振り返りはオンライン",{"type":48,"tag":167,"props":785,"children":786},{},[787,792,796,801],{"type":48,"tag":194,"props":788,"children":789},{},[790],{"type":53,"value":791},"4. 全社展開と定着",{"type":48,"tag":194,"props":793,"children":794},{},[795],{"type":53,"value":709},{"type":48,"tag":194,"props":797,"children":798},{},[799],{"type":53,"value":800},"週2〜3時間（問い合わせの一次対応の調整）",{"type":48,"tag":194,"props":802,"children":803},{},[804,806,811],{"type":53,"value":805},"部門ごとの研修で",{"type":48,"tag":88,"props":807,"children":808},{},[809],{"type":53,"value":810},"面着1〜2回",{"type":53,"value":812},"。以降は月1回のオンライン定例",{"type":48,"tag":49,"props":814,"children":815},{},[816,818,823,825,830],{"type":53,"value":817},"全体では ",{"type":48,"tag":88,"props":819,"children":820},{},[821],{"type":53,"value":822},"3〜4か月",{"type":53,"value":824},"、面着は ",{"type":48,"tag":88,"props":826,"children":827},{},[828],{"type":53,"value":829},"合計5〜7回（多くは半日）",{"type":53,"value":831}," が目安です。第1回で示した標準的な期間感（3〜6か月）の、早いほうに収まる規模です。",{"type":48,"tag":49,"props":833,"children":834},{},[835],{"type":53,"value":836},"次のような場合は、ここから伸びます。",{"type":48,"tag":108,"props":838,"children":839},{},[840,850,860],{"type":48,"tag":112,"props":841,"children":842},{},[843,848],{"type":48,"tag":88,"props":844,"children":845},{},[846],{"type":53,"value":847},"共有フォルダの権限が長年整理されていない",{"type":53,"value":849}," ―― フェーズ1が2〜3か月に延びることがあります。最も読みにくいのがここなので、フェーズ0の棚卸しで規模を先に把握します",{"type":48,"tag":112,"props":851,"children":852},{},[853,858],{"type":48,"tag":88,"props":854,"children":855},{},[856],{"type":53,"value":857},"ファイルサーバーや他社のグループウェアから移行する",{"type":53,"value":859}," ―― 移行そのものの期間が別途必要です",{"type":48,"tag":112,"props":861,"children":862},{},[863,868],{"type":48,"tag":88,"props":864,"children":865},{},[866],{"type":53,"value":867},"繁忙期と重なる",{"type":53,"value":869}," ―― パイロットの参加部門が動けず、フェーズ3が止まりがちです。逆に、決算期などを避けて計画すれば縮みます",{"type":48,"tag":96,"props":871,"children":872},{},[873,880],{"type":48,"tag":49,"props":874,"children":875},{},[876],{"type":48,"tag":88,"props":877,"children":878},{},[879],{"type":53,"value":603},{"type":48,"tag":49,"props":881,"children":882},{},[883],{"type":53,"value":884},"Outlook への移行では MX レコードの書き換えが要りますが、今の DNS がどう運用されているか分からないことが多く、MX・CNAME・サブドメインまでレコードを1つずつ確かめる棚卸しから始めます。情シス部門がある会社でも、各レコードの用途が分からなかったことがありました。",{"type":48,"tag":49,"props":886,"children":887},{},[888,890,895],{"type":53,"value":889},"面着とオンラインの使い分けは、",{"type":48,"tag":88,"props":891,"children":892},{},[893],{"type":53,"value":894},"決める場面は面着、確認と作業はオンライン",{"type":53,"value":896},"が基本です。役割分担・是正方針・ルールの承認のように、その場で意思決定が要る場面と、最初の研修は面着のほうが早く進みます。進捗確認や設定作業はオンラインで十分です。当社は全国に伺っていますが、関西・関東・名古屋は特に伺いやすい地域です。",{"type":48,"tag":147,"props":898,"children":900},{"id":899},"最低限の運用-アカウント権限問い合わせ窓口",[901],{"type":53,"value":902},"最低限の運用 ― アカウント・権限・問い合わせ窓口",{"type":48,"tag":49,"props":904,"children":905},{},[906],{"type":53,"value":907},"導入後の運用で、情シス担当（兼務）が回せるように、決めておくことを3つに絞ります。",{"type":48,"tag":909,"props":910,"children":912},"h3",{"id":911},"_1-アカウントの入退社手続き",[913],{"type":53,"value":914},"1. アカウントの入退社手続き",{"type":48,"tag":49,"props":916,"children":917},{},[918],{"type":53,"value":919},"Copilot は「その人が閲覧できる情報」を横断的に参照します。退職者のアカウントが残っていたり、異動前の部門のファイルが見えるままだったりすると、それがそのまま回答に反映されます。次の手続きを、人事・総務の入退社の手続きに組み込みます。",{"type":48,"tag":108,"props":921,"children":922},{},[923,933],{"type":48,"tag":112,"props":924,"children":925},{},[926,931],{"type":48,"tag":88,"props":927,"children":928},{},[929],{"type":53,"value":930},"入社・異動時",{"type":53,"value":932},"：アカウント作成、所属グループ（部門のチームやサイト）への追加、必要なら Copilot ライセンスの割り当て",{"type":48,"tag":112,"props":934,"children":935},{},[936,941],{"type":48,"tag":88,"props":937,"children":938},{},[939],{"type":53,"value":940},"退職・異動時",{"type":53,"value":942},"：前の部門のグループから外す、Copilot ライセンスを外して別の人に回す、退職者のアカウントを停止する",{"type":48,"tag":49,"props":944,"children":945},{},[946,948,955],{"type":53,"value":947},"ライセンスの割り当てと解除は、Microsoft 365 管理センターの「課金 ＞ ライセンス」から行えます（出典：",{"type":48,"tag":56,"props":949,"children":952},{"href":950,"rel":951},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fcopilot\u002Fmicrosoft-365\u002Fmicrosoft-365-copilot-setup",[60],[953],{"type":53,"value":954},"Microsoft Learn「Microsoft Copilot を設定し、ライセンスを割り当てる」",{"type":53,"value":956},"）。手続きを人事の書類とセットにしておけば、情シス担当が不在の日でも抜け漏れに気づけます。",{"type":48,"tag":909,"props":958,"children":960},{"id":959},"_2-管理者権限の持ち方",[961],{"type":53,"value":962},"2. 管理者権限の持ち方",{"type":48,"tag":49,"props":964,"children":965},{},[966],{"type":53,"value":967},"一人情シスの会社でよくあるのが、「管理者アカウントのパスワードを、情シス担当と外部業者と社長が共有している」状態です。これは避けます。",{"type":48,"tag":49,"props":969,"children":970},{},[971,973,980],{"type":53,"value":972},"Microsoft は、グローバル管理者（ほぼすべての設定とデータにアクセスできる最上位の管理者）をできるだけ少なくし、作業に必要な最小限の権限を持つロールを割り当てること、管理者には多要素認証を必須にすることを推奨しています。また、グローバル管理者が自分のアカウントからロックアウトされたときに備えて、パスワードをリセットできる別の管理者を用意しておくよう示しています（出典：",{"type":48,"tag":56,"props":974,"children":977},{"href":975,"rel":976},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-365\u002Fadmin\u002Fadd-users\u002Fabout-admin-roles?view=o365-worldwide",[60],[978],{"type":53,"value":979},"Microsoft Learn「Microsoft 365 管理センターの管理者ロールについて」",{"type":53,"value":65},{"type":48,"tag":49,"props":982,"children":983},{},[984],{"type":53,"value":985},"情シス不在の会社では、次の形が現実的です。",{"type":48,"tag":108,"props":987,"children":988},{},[989,999,1009],{"type":48,"tag":112,"props":990,"children":991},{},[992,997],{"type":48,"tag":88,"props":993,"children":994},{},[995],{"type":53,"value":996},"グローバル管理者は社内の2名",{"type":53,"value":998},"（情シス担当と推進責任者など）。個人ごとにアカウントを分け、共有しない",{"type":48,"tag":112,"props":1000,"children":1001},{},[1002,1007],{"type":48,"tag":88,"props":1003,"children":1004},{},[1005],{"type":53,"value":1006},"日常の作業は限定したロールで行う",{"type":53,"value":1008},"（ライセンスの付け外しならライセンス管理者、ユーザーの追加ならユーザー管理者など）。Copilot の設定やエージェントの管理には「AI 管理者」というロールもあります",{"type":48,"tag":112,"props":1010,"children":1011},{},[1012,1017],{"type":48,"tag":88,"props":1013,"children":1014},{},[1015],{"type":53,"value":1016},"外部パートナーには専用のアカウントか、Microsoft のパートナー向けの代理管理の仕組みで必要な権限だけを渡す",{"type":53,"value":1018},"。作業が終わったら権限を見直す",{"type":48,"tag":909,"props":1020,"children":1022},{"id":1021},"_3-問い合わせ窓口",[1023],{"type":53,"value":1024},"3. 問い合わせ窓口",{"type":48,"tag":49,"props":1026,"children":1027},{},[1028],{"type":53,"value":1029},"「Copilot がうまく答えない」「このファイルは入力してよいか」といった問い合わせが、すべて一人情シスに集まると、本業が止まります。問い合わせは3段階で受けます。",{"type":48,"tag":159,"props":1031,"children":1032},{},[1033,1054],{"type":48,"tag":163,"props":1034,"children":1035},{},[1036],{"type":48,"tag":167,"props":1037,"children":1038},{},[1039,1044,1049],{"type":48,"tag":171,"props":1040,"children":1041},{},[1042],{"type":53,"value":1043},"段階",{"type":48,"tag":171,"props":1045,"children":1046},{},[1047],{"type":53,"value":1048},"受ける人",{"type":48,"tag":171,"props":1050,"children":1051},{},[1052],{"type":53,"value":1053},"扱う内容",{"type":48,"tag":187,"props":1055,"children":1056},{},[1057,1075,1093],{"type":48,"tag":167,"props":1058,"children":1059},{},[1060,1065,1070],{"type":48,"tag":194,"props":1061,"children":1062},{},[1063],{"type":53,"value":1064},"一次",{"type":48,"tag":194,"props":1066,"children":1067},{},[1068],{"type":53,"value":1069},"各部門の現場代表（チャンピオン）",{"type":48,"tag":194,"props":1071,"children":1072},{},[1073],{"type":53,"value":1074},"使い方、指示の出し方、「この用途に使ってよいか」の一般的な判断",{"type":48,"tag":167,"props":1076,"children":1077},{},[1078,1083,1088],{"type":48,"tag":194,"props":1079,"children":1080},{},[1081],{"type":53,"value":1082},"二次",{"type":48,"tag":194,"props":1084,"children":1085},{},[1086],{"type":53,"value":1087},"情シス担当",{"type":48,"tag":194,"props":1089,"children":1090},{},[1091],{"type":53,"value":1092},"アカウント、ライセンス、「見えてはいけないファイルが見える」などの権限の問題",{"type":48,"tag":167,"props":1094,"children":1095},{},[1096,1101,1105],{"type":48,"tag":194,"props":1097,"children":1098},{},[1099],{"type":53,"value":1100},"三次",{"type":48,"tag":194,"props":1102,"children":1103},{},[1104],{"type":53,"value":356},{"type":48,"tag":194,"props":1106,"children":1107},{},[1108],{"type":53,"value":1109},"設定の変更、原因の調査、Microsoft へのサポート依頼",{"type":48,"tag":368,"props":1111,"children":1112},{},[1113,1114,1119,1120],{"type":53,"value":372},{"type":48,"tag":374,"props":1115,"children":1118},{"media":376,"srcSet":1116,"width":378,"height":1117},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-hitori-joshisu\u002Ftoiawase-3dan-sp.svg",558,[],{"type":53,"value":372},{"type":48,"tag":383,"props":1121,"children":1125},{"src":1122,"alt":1123,"width":387,"height":1124,"loading":388},"\u002Fimg\u002Fcontents\u002Farticles\u002Fcopilot-hitori-joshisu\u002Ftoiawase-3dan.svg","問い合わせの3段階：一次は各部門のチャンピオンが使い方を受け、二次は情シス担当がアカウントと権限、三次は外部パートナーが設定変更と調査を担う",252,[],{"type":48,"tag":49,"props":1127,"children":1128},{},[1129,1131,1137,1139,1145],{"type":53,"value":1130},"使い方の質問は、社内コミュニティ（Teams のチャネルなど）で受けると、同じ質問が繰り返し情シス担当に来るのを防げます。研修やチャンピオン制度の作り方は、",{"type":48,"tag":56,"props":1132,"children":1134},{"href":1133},"\u002Farticles\u002Fcopilot-zensha-tenkai-teichaku\u002F",[1135],{"type":53,"value":1136},"第7回前編：Copilotの定着化",{"type":53,"value":1138},"と",{"type":48,"tag":56,"props":1140,"children":1142},{"href":1141},"\u002Farticles\u002Fcopilot-shanai-kenshu-susumekata\u002F",[1143],{"type":53,"value":1144},"第7回後編：社内研修の進め方",{"type":53,"value":1146},"で詳しく扱っています。",{"type":48,"tag":96,"props":1148,"children":1149},{},[1150,1157],{"type":48,"tag":49,"props":1151,"children":1152},{},[1153],{"type":48,"tag":88,"props":1154,"children":1155},{},[1156],{"type":53,"value":603},{"type":48,"tag":49,"props":1158,"children":1159},{},[1160],{"type":53,"value":1161},"当社の支援先で、ITリテラシーが壁になり、導入に時間がかかったことがありました。そのときは、手順書を作り、ハンズオンで実際に操作しながら覚えていただく形に切り替えました。手順書は社内に残るので、あとから入った人にも渡せ、同じ説明を情シス担当が繰り返さずに済みます。情シスがいない会社ほど、説明会だけで終わらせず、手を動かす場と手元に残る資料を最初に用意しておくのが近道です。",{"type":48,"tag":147,"props":1163,"children":1165},{"id":1164},"月1時間の運用チェックリスト",[1166],{"type":53,"value":1164},{"type":48,"tag":49,"props":1168,"children":1169},{},[1170],{"type":53,"value":1171},"兼務の情シス担当が回せるよう、定期作業は月1回・1時間程度に収まる範囲に絞ります。",{"type":48,"tag":108,"props":1173,"children":1176},{"className":1174},[1175],"contains-task-list",[1177,1199,1208,1217,1226,1235],{"type":48,"tag":112,"props":1178,"children":1181},{"className":1179},[1180],"task-list-item",[1182,1188,1190,1197],{"type":48,"tag":1183,"props":1184,"children":1187},"input",{"disabled":1185,"type":1186},true,"checkbox",[],{"type":53,"value":1189}," Microsoft 365 管理センターの Copilot 使用状況レポートで、長く使われていない席を確認した（出典：",{"type":48,"tag":56,"props":1191,"children":1194},{"href":1192,"rel":1193},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fmicrosoft-365\u002Fadmin\u002Factivity-reports\u002Fmicrosoft-365-copilot-usage",[60],[1195],{"type":53,"value":1196},"Microsoft Learn「Microsoft Copilot の使用状況レポート」",{"type":53,"value":1198},"）",{"type":48,"tag":112,"props":1200,"children":1202},{"className":1201},[1180],[1203,1206],{"type":48,"tag":1183,"props":1204,"children":1205},{"disabled":1185,"type":1186},[],{"type":53,"value":1207}," 今月の入社・退職・異動者のアカウントとライセンスが、手続きどおりに処理されている",{"type":48,"tag":112,"props":1209,"children":1211},{"className":1210},[1180],[1212,1215],{"type":48,"tag":1183,"props":1213,"children":1214},{"disabled":1185,"type":1186},[],{"type":53,"value":1216}," グローバル管理者が社内の決めた人数のままで、不要な管理者ロールが残っていない",{"type":48,"tag":112,"props":1218,"children":1220},{"className":1219},[1180],[1221,1224],{"type":48,"tag":1183,"props":1222,"children":1223},{"disabled":1185,"type":1186},[],{"type":53,"value":1225}," 外部パートナーに渡した権限が、作業の終了に合わせて見直されている",{"type":48,"tag":112,"props":1227,"children":1229},{"className":1228},[1180],[1230,1233],{"type":48,"tag":1183,"props":1231,"children":1232},{"disabled":1185,"type":1186},[],{"type":53,"value":1234}," 管理センターのメッセージセンターで、Copilot に関する大きな変更のお知らせを確認した",{"type":48,"tag":112,"props":1236,"children":1238},{"className":1237},[1180],[1239,1242],{"type":48,"tag":1183,"props":1240,"children":1241},{"disabled":1185,"type":1186},[],{"type":53,"value":1243}," 現場から上がった「見えてはいけないファイルが見えた」報告を、推進責任者に共有した",{"type":48,"tag":49,"props":1245,"children":1246},{},[1247],{"type":53,"value":1248},"最後の項目は、判断を社内に残すための仕組みです。権限の問題を情シス担当が1人で抱えず、推進責任者と共有して是正の優先順位を決めます。",{"type":48,"tag":147,"props":1250,"children":1252},{"id":1251},"中小企業向けのライセンスを確認する",[1253],{"type":53,"value":1251},{"type":48,"tag":49,"props":1255,"children":1256},{},[1257],{"type":53,"value":1258},"情シス不在の会社の多くは中小規模です。ライセンス選びでは、次の2点を押さえます。",{"type":48,"tag":108,"props":1260,"children":1261},{},[1262,1272],{"type":48,"tag":112,"props":1263,"children":1264},{},[1265,1270],{"type":48,"tag":88,"props":1266,"children":1267},{},[1268],{"type":53,"value":1269},"Copilot Chat は追加費用なしで使える",{"type":53,"value":1271}," ―― 対象の Microsoft 365 プランを使っていれば、Web の情報をもとにしたAIチャットを追加費用なしで利用できます。第1回で紹介した「全社に Copilot Chat、有償席は絞る」の二層構成は、管理の手間を抑える意味でも有効です",{"type":48,"tag":112,"props":1273,"children":1274},{},[1275,1280,1282,1289,1291,1298],{"type":48,"tag":88,"props":1276,"children":1277},{},[1278],{"type":53,"value":1279},"300ユーザーまでなら Copilot Business がある",{"type":53,"value":1281}," ―― 社内のメールやファイルを参照する有償の Copilot には、300ユーザーまでの組織向けに「Copilot Business」が用意されています（出典：",{"type":48,"tag":56,"props":1283,"children":1286},{"href":1284,"rel":1285},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fpartner-center\u002Fannouncements\u002F2025-december",[60],[1287],{"type":53,"value":1288},"Microsoft Learn「Partner Center の発表（2025年12月）」",{"type":53,"value":1290},"）。前提として Microsoft 365 Business Basic・Business Standard・Business Premium などのプランが必要です（出典：",{"type":48,"tag":56,"props":1292,"children":1295},{"href":1293,"rel":1294},"https:\u002F\u002Flearn.microsoft.com\u002Fja-jp\u002Fcopilot\u002Fmicrosoft-365\u002Fmicrosoft-365-copilot-licensing",[60],[1296],{"type":53,"value":1297},"Microsoft Learn「Microsoft Copilot のライセンス オプション」",{"type":53,"value":1198},{"type":48,"tag":49,"props":1300,"children":1301},{},[1302,1304,1311],{"type":53,"value":1303},"価格は、Microsoft の日本向け価格ページで、Copilot Business が年払いで1ユーザーあたり月額3,148円相当と表示されています。2026年7月1日から12月31日までは、対象のビジネスプランを利用中の顧客向けに月額2,698円相当の期間限定価格も示されています（出典：",{"type":48,"tag":56,"props":1305,"children":1308},{"href":1306,"rel":1307},"https:\u002F\u002Fwww.microsoft.com\u002Fja-jp\u002Fmicrosoft-365-copilot\u002Fpricing",[60],[1309],{"type":53,"value":1310},"Microsoft 365 Copilot の価格",{"type":53,"value":1312},"、2026年9月時点）。価格と条件は変わりやすいため、購入前に必ず公式サイトで確認してください。",{"type":48,"tag":147,"props":1314,"children":1316},{"id":1315},"外部パートナーを選ぶときの確認ポイント",[1317],{"type":53,"value":1315},{"type":48,"tag":49,"props":1319,"children":1320},{},[1321],{"type":53,"value":1322},"情シス不在の会社にとって、外部パートナーは「足りない手」です。ただし、任せ方を誤ると、今度は社外に属人化します。次の点を確認します。",{"type":48,"tag":108,"props":1324,"children":1325},{},[1326,1336,1346,1356,1366],{"type":48,"tag":112,"props":1327,"children":1328},{},[1329,1334],{"type":48,"tag":88,"props":1330,"children":1331},{},[1332],{"type":53,"value":1333},"判断と作業を分けて提案してくれるか",{"type":53,"value":1335}," ―― 「全部お任せください」ではなく、社内で決めるべきことを明示してくれるか",{"type":48,"tag":112,"props":1337,"children":1338},{},[1339,1344],{"type":48,"tag":88,"props":1340,"children":1341},{},[1342],{"type":53,"value":1343},"権限の渡し方を相談できるか",{"type":53,"value":1345}," ―― 管理者アカウントの共有を求めず、必要な権限だけで作業する前提か",{"type":48,"tag":112,"props":1347,"children":1348},{},[1349,1354],{"type":48,"tag":88,"props":1350,"children":1351},{},[1352],{"type":53,"value":1353},"設定の記録を残してくれるか",{"type":53,"value":1355}," ―― 何を、なぜ、どう設定したかを文書で受け取れるか。担当者が変わっても引き継げるか",{"type":48,"tag":112,"props":1357,"children":1358},{},[1359,1364],{"type":48,"tag":88,"props":1360,"children":1361},{},[1362],{"type":53,"value":1363},"業務の話ができるか",{"type":53,"value":1365}," ―― Copilot の機能説明だけでなく、自社の業務のどこで使うかを一緒に考えられるか",{"type":48,"tag":112,"props":1367,"children":1368},{},[1369,1374],{"type":48,"tag":88,"props":1370,"children":1371},{},[1372],{"type":53,"value":1373},"導入後の窓口が決まっているか",{"type":53,"value":1375}," ―― 三次窓口として、どの範囲の問い合わせをどう受けるかが明確か",{"type":48,"tag":147,"props":1377,"children":1379},{"id":1378},"ksrogers-の支援",[1380],{"type":53,"value":1381},"K.S.Rogers の支援",{"type":48,"tag":49,"props":1383,"children":1384},{},[1385],{"type":53,"value":1386},"K.S.Rogers では、専任の情シスがいない会社の Microsoft 365 Copilot 導入を、本記事の「判断は社内、作業は外部」の考え方で支援しています。推進責任者と一緒に判断すべき事項を整理し、権限の棚卸しやセキュリティ設定、ガイドラインのたたき台、研修の実施までを担い、設定の記録を社内に残します。",{"type":48,"tag":49,"props":1388,"children":1389},{},[1390,1392,1398],{"type":53,"value":1391},"Copilot の範囲を超えて、基幹システムとつないだ転記や照合などの定型業務を自動化したい場合は、AI業務自動化の導入支援サービス",{"type":48,"tag":56,"props":1393,"children":1395},{"href":1394},"\u002Fbusiness\u002Fopezero\u002F",[1396],{"type":53,"value":1397},"OpeZero",{"type":53,"value":1399},"で、システム環境調査（20万円〜）から構築・運用までまとめてお任せいただけます。構築費は0円、稼働後は月額固定の運用報酬型です。",{"type":48,"tag":49,"props":1401,"children":1402},{},[1403,1405,1411],{"type":53,"value":1404},"M365 の導入・ファイル移行から Power Platform・Copilot の活用までの支援の範囲と進め方は、",{"type":48,"tag":56,"props":1406,"children":1408},{"href":1407},"\u002Fbusiness\u002Fm365\u002F",[1409],{"type":53,"value":1410},"Microsoft 365 導入・活用支援",{"type":53,"value":1412},"のページにまとめています。",{"type":48,"tag":49,"props":1414,"children":1415},{},[1416,1418,1424],{"type":53,"value":1417},"「IT担当が1人で、どこから手をつければいいか分からない」という段階から、",{"type":48,"tag":56,"props":1419,"children":1421},{"href":1420},"\u002Fcontact\u002F",[1422],{"type":53,"value":1423},"お問い合わせ",{"type":53,"value":1425},"よりご相談ください。",{"type":48,"tag":147,"props":1427,"children":1429},{"id":1428},"まとめ",[1430],{"type":53,"value":1428},{"type":48,"tag":108,"props":1432,"children":1433},{},[1434,1446,1457,1462,1480],{"type":48,"tag":112,"props":1435,"children":1436},{},[1437,1439,1444],{"type":53,"value":1438},"情シス不在・一人情シスの会社で Copilot 導入が止まるのは、",{"type":48,"tag":88,"props":1440,"children":1441},{},[1442],{"type":53,"value":1443},"丸投げ・兼務で後回し・属人化",{"type":53,"value":1445},"の3つが原因です",{"type":48,"tag":112,"props":1447,"children":1448},{},[1449,1451,1455],{"type":53,"value":1450},"推進責任者・情シス担当・現場代表・外部パートナーの4者で役割を分け、",{"type":48,"tag":88,"props":1452,"children":1453},{},[1454],{"type":53,"value":121},{"type":53,"value":1456},"と切り分けます",{"type":48,"tag":112,"props":1458,"children":1459},{},[1460],{"type":53,"value":1461},"運用で最低限決めるのは、アカウントの入退社手続き、管理者権限の持ち方、3段階の問い合わせ窓口です",{"type":48,"tag":112,"props":1463,"children":1464},{},[1465,1467,1471,1473,1478],{"type":53,"value":1466},"社員50人前後の会社なら、現状把握から全社展開まで",{"type":48,"tag":88,"props":1468,"children":1469},{},[1470],{"type":53,"value":822},{"type":53,"value":1472},"、外部パートナーとの面着は",{"type":48,"tag":88,"props":1474,"children":1475},{},[1476],{"type":53,"value":1477},"合計5〜7回",{"type":53,"value":1479},"が目安です",{"type":48,"tag":112,"props":1481,"children":1482},{},[1483],{"type":53,"value":1484},"300ユーザーまでなら Copilot Business も選択肢です。価格と条件は変わりやすいので、公式サイトで最新の情報を確認します",{"type":48,"tag":49,"props":1486,"children":1487},{},[1488],{"type":53,"value":1489},"次回の第8回はシリーズの完結編として、Copilot を「使う」段階から、エージェントを「作る」段階へ進む方法を扱います。",{"title":7,"searchDepth":1491,"depth":1491,"links":1492},2,[1493,1494,1495,1496,1497,1503,1504,1505,1506,1507],{"id":149,"depth":1491,"text":152},{"id":259,"depth":1491,"text":262},{"id":416,"depth":1491,"text":419},{"id":619,"depth":1491,"text":622},{"id":899,"depth":1491,"text":902,"children":1498},[1499,1501,1502],{"id":911,"depth":1500,"text":914},3,{"id":959,"depth":1500,"text":962},{"id":1021,"depth":1500,"text":1024},{"id":1164,"depth":1491,"text":1164},{"id":1251,"depth":1491,"text":1251},{"id":1315,"depth":1491,"text":1315},{"id":1378,"depth":1491,"text":1381},{"id":1428,"depth":1491,"text":1428},"markdown","content:articles:copilot-hitori-joshisu.md","content","articles\u002Fcopilot-hitori-joshisu.md","articles\u002Fcopilot-hitori-joshisu","md",[1515,1519,1524,1528,1533,1537,1541,1546,1551,1556,1561,1566,1570,1575,1580],{"_path":1516,"title":1517,"seriesNo":1518,"seriesLabel":632},"\u002Farticles\u002Fm365-copilot-donyu-roadmap","Microsoft 365 Copilot 導入ロードマップ｜非IT企業がライセンス配布前に決めること",1,{"_path":1520,"title":1521,"seriesNo":1522,"seriesLabel":1523},"\u002Farticles\u002Fcopilot-shanai-kitei-edp","Copilotのエンタープライズデータ保護（EDP）とは｜「外部AI禁止」の社内規程でも使えるかの判断手順",1.5,"特別編",{"_path":1525,"title":1526,"seriesNo":1491,"seriesLabel":1527},"\u002Farticles\u002Fcopilot-data-okiba-box-sharepoint","Copilotは社内データを学習する？｜参照できるデータの条件とSharePoint・OneDrive・Boxの使い分け","第2回（前編）",{"_path":1529,"title":1530,"seriesNo":1531,"seriesLabel":1532},"\u002Farticles\u002Fcopilot-mail-chat-ikou-checklist","Exchange Online移行の注意点とLINE WORKSからTeamsへの判断｜Microsoft 365 Copilot導入前チェックリスト",2.5,"第2回（後編）",{"_path":1534,"title":1535,"seriesNo":1536,"seriesLabel":14},"\u002Farticles\u002Fm365-copilot-iranai-google-hikaku","Microsoft 365 Copilotはいらない？無料版との違い・料金と「Googleより高い」への答え方",2.8,{"_path":1538,"title":1539,"seriesNo":1500,"seriesLabel":1540},"\u002Farticles\u002Fcopilot-joho-rouei-sharepoint-kengen","Microsoft 365 Copilotの情報漏洩対策｜SharePoint・OneDrive・Teamsの権限を棚卸しして是正する手順","第3回",{"_path":1542,"title":1543,"seriesNo":1544,"seriesLabel":1545},"\u002Farticles\u002Fcopilot-security-settei-chusho","Microsoft 365 Copilotのセキュリティ設定｜中小企業に秘密度ラベルとDLPは必要か",4,"第4回（前編）",{"_path":1547,"title":1548,"seriesNo":1549,"seriesLabel":1550},"\u002Farticles\u002Fcopilot-sensitivity-label-dlp","Microsoft 365 Copilotの秘密度ラベルとDLP｜「警告」から始める段階設計とライセンス要件",4.5,"第4回（後編）",{"_path":1552,"title":1553,"seriesNo":1554,"seriesLabel":1555},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample","生成AIの社内ルールの作り方【サンプル条文付き】｜Microsoft 365 Copilot時代の利用ガイドライン",5,"第5回（前編）",{"_path":1557,"title":1558,"seriesNo":1559,"seriesLabel":1560},"\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule","システム開発を外注するときのAI利用ルール｜開発会社に求める5つの約束と秘密情報の扱い",5.2,"第5回（後編）",{"_path":1562,"title":1563,"seriesNo":1564,"seriesLabel":1565},"\u002Farticles\u002Fcopilot-pilot-kouka-sokutei","Microsoft 365 Copilotのパイロット導入と効果測定｜導入効果を経営に説明する指標とGo\u002FNo-Go判断",6,"第6回",{"_path":1567,"title":1568,"seriesNo":1569,"seriesLabel":14},"\u002Farticles\u002Fcopilot-kaitou-troubleshoot","Microsoft 365 Copilotが使えない・期待した回答を返さない原因と対処｜切り分けフローチャート",6.5,{"_path":1571,"title":1572,"seriesNo":1573,"seriesLabel":1574},"\u002Farticles\u002Fcopilot-zensha-tenkai-teichaku","Microsoft 365 Copilotの定着化｜全社展開で「使われない」を防ぐチャンピオン制度と事例共有",7,"第7回（前編）",{"_path":1576,"title":1577,"seriesNo":1578,"seriesLabel":1579},"\u002Farticles\u002Fcopilot-shanai-kenshu-susumekata","Microsoft 365 Copilotの社内研修の進め方｜リテラシーの差を越える段階別研修と復習の仕組み",7.2,"第7回（後編）",{"_path":4,"title":8,"seriesNo":13,"seriesLabel":14},1793545948921]